27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Responses<br />

Please Note<br />

The following sample responses show information for multiple load IDs listed<br />

in ascending order. On your screen, multiple load ID responses may be<br />

arranged in ascending, descending, or r<strong>and</strong>om order. Options shown in the<br />

responses are the options specified on the <strong>CP</strong>XLOAD comm<strong>and</strong> <strong>and</strong> not the<br />

options set as a result of the OPTIONS loader directive.<br />

Response 1 (Display by Load ID):<br />

QUERY <strong>CP</strong>XLOAD<br />

To display information about the customer-written <strong>CP</strong> routines loaded as identifier 1,<br />

enter the following:<br />

query cpxload id 1<br />

▌1▐ Loaded as identifier 1<br />

▌2▐ File: ZXXKL STUFF Z<br />

▌3▐ Loaded by: SYSTEM on 10/12/95 at 11:27:59<br />

▌4▐ <strong>CP</strong>XLOAD options: MP NOCONTROL DELAY NOLET PERMANENT<br />

▌5▐<br />

Associated entry points <strong>and</strong> external symbols:<br />

PLOQWERTY is at 078DF3A6<br />

ZXXKLM is at 078DF58E<br />

ZXXKLMFF is at 078DF772<br />

ZXXKLMPQ is at 078DF99C<br />

ZXXKLMQU is at 078DF000 module size is 000EF8<br />

Ready;<br />

In this example,<br />

▌1▐ is the load ID assigned to all the routines that were loaded by the file in line<br />

▌2▐ .<br />

▌2▐ is the file identifier of the file:<br />

v Containing the routines that were loaded,<br />

v Which imbedded or included the routines that were loaded, or<br />

v Some combination thereof.<br />

v The filemode indicates the file mode of the <strong>CP</strong> accessed disk at the time<br />

of the <strong>CP</strong>XLOAD.<br />

▌3▐ tells you the virtual machine responsible for loading the routines <strong>and</strong> the<br />

date <strong>and</strong> time they were loaded. If the virtual machine is SYSTEM (as in this<br />

example), then the routines were loaded by <strong>CP</strong>XLOAD statements in your<br />

system configuration file.<br />

▌4▐ are the options from the <strong>CP</strong>XLOAD comm<strong>and</strong> or <strong>CP</strong>XLOAD configuration<br />

file statement. It does not include any information from OPTIONS loader<br />

directives imbedded in the loaded files. Note that the specified <strong>CP</strong>XLOAD<br />

options are listed as well as the defaults that were taken because an option<br />

was not specified.<br />

▌5▐ lists all of the entry points <strong>and</strong> external symbols associated with the routine<br />

that was loaded. For each entry point or external symbol, <strong>CP</strong> displays the<br />

starting address in <strong>CP</strong>’s system execution space where you can find the<br />

entry point or external symbol, <strong>and</strong> for modules, <strong>CP</strong> also displays the<br />

module’s size.<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 753

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!