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.

Messages<br />

For more information on the PDOFF parameter or any of the other IPL parameters,<br />

see the z/<strong>VM</strong>: <strong>CP</strong> Planning <strong>and</strong> Administration book.<br />

To display the current IPL parameters, use the <strong>CP</strong> QUERY IPLPARMS comm<strong>and</strong>.<br />

Be aware that the <strong>CP</strong> SET IPLPARMS comm<strong>and</strong> may have changed them since<br />

<strong>CP</strong> was started. For more information on these comm<strong>and</strong>s, see “QUERY<br />

IPLPARMS” on page 829 <strong>and</strong> “SET IPLPARMS” on page 1263.<br />

The third line of the response tells you that <strong>CP</strong> was started by the system operator<br />

at the system console. One of the following variations will appear as the third line of<br />

the response.<br />

v The response below tells you that <strong>CP</strong> was started by the system operator at the<br />

system console.<br />

Last start was a system IPL.<br />

v The response below tells you that the operator restarted <strong>CP</strong> using the <strong>CP</strong><br />

SHUTDOWN comm<strong>and</strong> with the REIPL oper<strong>and</strong>.<br />

Last start was a system restart from SHUTDOWN REIPL.<br />

v The response below tells you that <strong>CP</strong> restarted itself after abend XXXnnn<br />

occurred. Use <strong>CP</strong> QUERY <strong>CP</strong>LEVEL to find out when the restart occurred.<br />

Last start was a system restart after system failure XXXnnn<br />

Response 2:<br />

Module <strong>CP</strong>LOAD was loaded from minidisk on volume ESARES at cylinder 20<br />

Parm disk number 2 on volume ESARES, cylinders 90 through 94<br />

Last start was a system IPL<br />

In this example, the second line of the response indicates that the person who<br />

performed the IPL either:<br />

v Did not override the system’s assumption <strong>and</strong> the allocation map had a parm<br />

disk defined for the minidisk containing the <strong>CP</strong> module.<br />

v Or, used the PDNUM parameter during the IPL to specify a specific parm disk<br />

number, as defined in the allocation map<br />

v Or, used the PDOFF parameter during the IPL to specify a cylinder or block<br />

offset <strong>and</strong> the allocation map had a parm disk defined in that location<br />

For more information on the PDNUM or PDOFF parameter or any of the other IPL<br />

parameters, see the z/<strong>VM</strong>: <strong>CP</strong> Planning <strong>and</strong> Administration book.<br />

Response 3:<br />

Module NEW<strong>CP</strong> loaded from minidisk on volume ESARES at cylinder 2400<br />

Parm disk number 3 on volume OLDRES, cylinders 586 through 590<br />

Last start was a system IPL.<br />

In this example, the volume IDs on the first <strong>and</strong> second lines are different. The<br />

person who performed the IPL loaded <strong>CP</strong> from a module on one volume <strong>and</strong> used<br />

a parm disk on another volume.<br />

H<strong>CP</strong>003E Invalid option - comm<strong>and</strong> contains<br />

extra option(s) starting with oper<strong>and</strong><br />

QUERY <strong>CP</strong>LOAD<br />

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

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

Saved successfully!

Ooh no, something went wrong!