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

QUERY CPLOAD
QUERY CPLOAD
►►
Query
Authorization
Purpose
CPLOAD
Responses
Privilege Class: A, B, E
Use QUERY CPLOAD to display information regarding the last CP IPL. The
information displayed includes the location of the CP module that was last used, the
location of the parm disk, and how CP was started.
You can load CP only from a module on a CMS-formatted minidisk. When you load
CP, you must specify device, system, and logo definition information. You specify
this information in files on a parm disk. CP can ‘sense’ most device definition
information, so you do not have to define it. System definition information goes in
the system configuration file, and logo definition information goes in the logo
configuration file.
Note: When you use FBA devices, the responses are shown in blocks.
Response 1:
For CKD/ECKD devices:
Module CPLOAD2 was loaded from minidisk on volume ESARES at cylinder 2400
Parm disk on volume ESARES, cylinders 2400 through 2420
Last start was system IPL.
For FBA devices:
742 z/VM: CP Commands and Utilities Reference
Module CPLOAD2 was loaded from minidisk on volume FBARES at block 24000
Parm disk on volume FBARES, blocks 24000 through 43992
Last start was a system IPL.
The first line of the response tells you CP was loaded from a module, the name of
the module, and the location of the minidisk from which CP loaded the module. The
second line of the response tells you CP used a parm disk during the IPL and the
location of the parm disk.
CP assumes the parm disk is the same minidisk that contains the module, unless
you override that assumption. In the example above, the second line of the
response indicates that the person who performed the IPL either:
v Did not override the system’s assumption. The Stand Alone Loader used a
cylinder or block offset to find the location of the parm disk. The allocation map
did not have a parm disk defined at that location.
v Used the PDOFF IPL parameter during the IPL to specify a cylinder or block
offset of the location of the parm disk. The value specified for the PDOFF IPL
parameter coincides with the location of the minidisk from which CP loaded the
module. The allocation map did not have a parm disk defined at that location.
►◄