IPL

Authorization

Privilege Class: G

Purpose

Use the IPL command to simulate an initial program load (IPL) function for your virtual machine.

Operands

system_name

The system_name operand specifies the 1- to 8-character alphanumeric name of a named saved system. The system was saved by using the SAVESYS command.

vdev

The vdev operand specifies the virtual device number of a device to IPL. The value must be a hexadecimal number in the range X'0000' - X'FFFF'. A guest IPL from the specified device is initiated.

Note: DASD that is defined as being unsupported cannot be IPLed by CP. Unsupported DASD can be used only by a virtual machine that is IPLed from a supported device or from a named saved system. See Direct access storage devices (DASD) in z/VM: General Information.

fcp_vdev

The fcp_vdev operand initiates a list-directed IPL operation from an FCP-attached (SCSI) device. The fcp_vdev operand specifies the virtual device number of the attached FCP device.

If the IPL command's DUMP operand is specified, some storage is saved for the dump. The system dumper program is then loaded and stores data to the device that it is configured to use.

The fcp_vdev operand indicates a list-directed IPL, in which some required IPL information is specified by LOADDEV or DUMPDEV parameters. For more information, see usage notes 25 and 26.

If the LOADDEV or DUMPDEV parameters specify a virtual device number, you can omit the IPL command's fcp_vdev operand and instead use the IPL command's LOADDEV or DUMPDEV operand. If both the IPL command's fcp_vdev operand and the LOADDEV or DUMPDEV parameters specify a virtual device number, then the fcp_vdev operand must specify the same virtual device number as the LOADDEV or DUMPDEV parameters specify.

The fcp_vdev operand is not allowed if the LOADDEV or DUMPDEV parameters specify the SECURE parameter.

If the fcp_vdev and NSSDATA operands are specified, the DUMP operand must also be specified.

LOADDEV

DUMPDEV

The LOADDEV and DUMPDEV operands initiate a list-directed IPL operation from an FCP-attached (SCSI) device or an ECKD device. All information that is required for IPL, including the device number, must be set in the LOADDEV or DUMPDEV parameters.

The LOADDEV operand indicates a list-directed IPL that uses preset LOADDEV parameters to load an operating system program without dump.

The DUMPDEV operand indicates a list-directed IPL that uses preset DUMPDEV parameters to load a system dumper program. The device that is IPLed is also used to store the dump data.

A secure IPL is possible only when the SECURE parameter is set and the IPL command specifies the LOADDEV or DUMPDEV operand.

For more information, see usage notes 25 and 26.

cylno

blkno

The cylno and blkno operands specify the location of the IPL data when the vdev operand specifies a DASD device. For CKD and ECKD DASD devices, the cylno operand specifies the cylinder number that contains the IPL data. For FBA DASD devices, the blkno operand specifies the starting block number where the IPL data is located. If not specified and the vdev operand identifies a DASD device, virtual cylinder 0 or block number 0 are defaulted. This operand is only for virtual direct access storage devices.

NOCLear

The NOCLEAR operand allows the contents of your virtual machine's storage to remain unchanged before program load. NOCLEAR is the default.

CLear

The CLEAR operand sets the contents of your virtual machine's storage to binary zeros before the operating system is loaded.

DUMP

The DUMP operand initiates a guest IPL from SCSI disk with dump. The following requirements apply when the DUMP operand is specified:

• The fcp_vdev operand specifies an attached FCP device.
• DUMPDEV parameters were set by using the SET DUMPDEV command. If the DUMPDEV parameters include a device number, then the fcp_vdev operand matches that device number.

A list-directed IPL with dump is similar to a list-directed IPL without dump but has three differences:

1. Before the machine loader is loaded into storage, a model-dependent amount of guest storage is saved in simulated HSA. The anchor and size of the storage area is saved in the base VMDBK of the guest that requests the dump.
2. A system image is not loaded from the SCSI device that is identified by using a SET LOADDEV command. A system dumper is loaded from the SCSI device that is identified by the SET DUMPDEV command. The same device is also used to store the dump data. The operands that are valid for the SET LOADDEV command are the same operands that are valid for the SET DUMPDEV command.
3. The system dumper calls DIAG X'308' with subcode 2 to release the data that is saved in simulated HSA.

NSSDATA

The NSSDATA operand preserves a private copy of the contents of the existing embedded NSS (named saved system) in memory after the IPL command completes.

If the NSSDATA operand is specified when an FCP device is IPLed, then the DUMP operand must also be specified.

Because the NSSDATA operand is not permitted when the LOADDEV or DUMPDEV operand is specified, the NSSDATA operand cannot be used with a secure IPL. The NSSDATA operand is deprecated and might be removed in the future.

The following requirements apply when the DUMP operand is specified:

• The NSS is fully contained within the first extent of guest memory.
• The NSS does not contain SW, SN or SC pages.
• The NSS is not a VMGROUP NSS.

If any of these requirements are not satisfied, the command fails and the system remains unchanged.

STOP

The STOP operand halts the virtual machine during the IPL procedure just after the initial PSW is loaded. After the halt, you can simulate an IPL procedure for your virtual machine in instruction step mode. When your virtual machine stops, you can enter CP commands. To restart the virtual machine, enter the BEGIN command.

ATTN

The ATTN operand sends an attention interrupt to the virtual machine during the IPL procedure.

LOADParm load_parm

The LOADPARM operand specifies a load parameter of 1-8 characters. The parameter value can be retrieved by the guest operating system during its IPL sequence. Its use is determined by the guest operating system, such as indicating the nucleus to be loaded during the IPL sequence. If the LOADPARM operand is not specified, a load parameter of eight EBCDIC blanks is formed.

Use single quotation marks to preserve leading and embedded blanks. If fewer than eight characters are specified, the parameter value is left-justified and padded with blanks.

The parameter value is converted to uppercase and can include only the uppercase alphabetic characters (A-Z), digits 0-9, the period, and the blank.

PARM parm_string

The PARM operand specifies a parameter string up to 64 bytes long to pass to the virtual machine in general purpose registers at completion of IPL. The parameter string begins with the first nonblank character that follows the PARM keyword. It consists of all remaining characters that follow on the command line, including trailing blanks. If you specify other optional parameters on the IPL command, you must enter the PARM operand last.

If you are IPLing a device, the parameter string is inserted into the virtual machine registers, four bytes per register, starting with register 0. If the string is less than 64 bytes, a single byte of binary zeros is inserted following the string. If you omit PARM, the virtual machine registers are unchanged. If you IPL an NSS that was defined with the PARMREGS=m-n option on the DEFSYS command, the parameter string is inserted into the virtual machine registers m through n. Before insertion, the virtual machine registers m through n, initialized to binary zeros. For more information, refer to the DEFSYS command. If you enter a string that is too large to fit in the designated registers, an error message is issued, and the command is not processed. If you specify PARM followed by all blanks or if you omit PARM, the virtual machine registers specified by the PARMREGS option on the DEFSYS command contains all zeros.

If you IPL an NSS that was defined with the PARMREGS=NONE option on the DEFSYS command, the PARM option yields an error message. The command is not processed.

If you are IPLing an NSS that was defined without the PARMREGS=m-n option on the DEFSYS command, the parameter string is inserted into the virtual machine registers 0 - 15. The registers are not first initialized to binary zeros. If you specify PARM followed by all blanks or if you omit PARM, the virtual machine registers are unchanged.

Usage Notes

1. The IPL command can be entered from the virtual machine console as the first or only command on a CP command line. A CP command line is when TERMINAL MODE is CP or CP READ is displayed or the command line begins with #CP. In that case, VM attempts to break out of certain wait states that might exist. Thus the IPL command can be entered to cause breakout of certain virtual machine wait states.

   The breakout attempt occurs when the IPL command is entered, not when the command is processed. Command errors do not prevent the breakout attempt. In some cases, a breakout resets the virtual machine.

2. If you want to use the AUTOCR, BATCH, NOSPROF, INSTSEG, or SAVESYS parameters of the IPL command, you must have PARMREGS=0-15 in the DEFSYS command for the CMS named saved system.
3. IPL simulates the LOAD operation on the real system console. The specified virtual device is accessed, and the required input/output operations are performed to retrieve the IPL data. This does not pertain to named saved systems.
4. Optionally, you can stop the IPL procedure after the virtual PSW is loaded. Also, you can pass parameters to the virtual machine's general registers. When the simulated load function is complete, CP initiates execution of the virtual machine by loading the IPL PSW, which was stored during the simulation process.
5. If you enter ipl system_name or ipl vdev clear, the IPL command performs a system-reset-clear function on your virtual machine as if the SYSTEM CLEAR command were processed.

   You can enter ipl vdev noclear or enter ipl vdev and take the NOCLEAR default. In this case, the IPL command performs a system-reset-normal function on your virtual machine as if the SYSTEM RESET command were processed.

   The effects of a system-reset-normal or system-reset-clear function are described in detail in the description for the SYSTEM RESET and SYSTEM CLEAR commands.
6. Any logical lines that follow the IPL command are ignored because execution of the IPL command transfers control from the CP environment to the virtual machine environment.
7. The IPL sequence for the program that you want to IPL must use only format 0 CCWs.
8. After you enter the IPL command, the pseudo page fault facility is deactivated. To activate (or reactivate) the pseudo page fault facility, you must enter the SET PAGEX command with the ON operand. For more information, see usage note 2 in the description of the SET PAGEX command.
9. Care must be used when parameters are passed to a named saved system (system_name). Named saved systems might expect certain registers to be initialized when they are given control. Indiscriminate use of the PARM operand might overlay a previously initialized register, causing unpredictable results.
10. The IPL command fails if issued when VMRELOCATE is in progress.
11. When system_name is equal to a hexadecimal device number, the device is IPLed if it exists; otherwise, the named saved segment (NSS) is IPLed.
12. The NSS name _0___1__ is reserved for IBM® use.
13. The LOADDEV and DUMPDEV keywords are not valid for use as NSS names.
14. Processing of an IPL command on an NSS might be delayed if DIAGNOSE code X'64' is concurrently performing the initial load of a large DCSS.
15. The contents of an NSS preserved by processing the NSSDATA parameter includes storage keys that are accurately preserved except for the reference bit, which is unreliable. The change bit is always off for SR and ER pages of an NSS and they cannot be changed by the user. Therefore, the change bit is never on for preserved SR or ER pages.
16. Immediately after an NSS is restored by the IPL command, the virtual machine's architecture mode is determined by its MACHINE setting. In some cases, the virtual machine's architecture mode is also determined by the architecture mode when the NSS was saved. The interaction of the MACHINE setting and the architecture mode when the NSS was saved has the following outcomes:

    MACHINE setting: ESA

    Architecture mode when NSS was saved: ESA/390 or ESA/XC

    If the MACHINE setting is ESA and the NSS was saved while in ESA/390 mode or ESA/XC mode, then the architecture mode is ESA/390.

    Architecture mode when NSS was saved: z/Architecture® or z/XC

    If the MACHINE setting is ESA and the NSS was saved while in z/Architecture mode or z/XC mode, then the architecture mode is z/Architecture.

    MACHINE setting: XC

    Architecture mode when NSS was saved: ESA/390 or ESA/XC

    If the MACHINE setting is XC and the NSS was saved while in ESA/390 mode or ESA/XC mode, then the architecture mode is ESA/XC.

    Architecture mode when NSS was saved: z/Architecture or z/XC

    If the MACHINE setting is XC and the NSS was saved while in z/Architecture mode or z/XC mode, then the architecture mode is z/XC. However, if the virtual machine's relocation domain excludes z/XC capability, then IPL sets the architecture mode to ESA/XC.

    MACHINE setting: Z

    If the MACHINE setting is Z, then the architecture mode is z/Architecture.

    If the architecture mode on completion of the IPL command differs from the mode at SAVESYS, the PSW is converted to the appropriate format (that is, from a 64-bit ESA/390 or ESA/XC PSW to a 128-bit z/Architecture or z/XC PSW, or vice versa).
17. If you IPL an NSS that was created with the VMGROUP option on the DEFSYS command, your virtual machine becomes a member of the virtual machine group that is known by the NSS name. Members of a virtual machine group are permitted to connect to the signal system service and to provide intragroup signaling. Signaling includes awareness messages (signal-in and signal-out) about members that join or leave the group.

    If your machine is a member of a virtual machine group, a user with an appropriate privilege class can authorize trace data recording into a system data file for the group. Issue a TRSAVE command and specify FOR sysname.

18. If you do not want leading blanks or embedded blanks in the LOADPARM operand, you can specify the parameter value as a single blank-delimited token. Single quotation marks preserve leading and embedded blanks.
19. The LOADPARM operand cannot contain a X'15' character.
20. You can specify both the LOADPARM and PARM options when IPLing by either vdev or system_name. Both options can be specified on the same command line. However, if you specify the PARM option, it must be the last option on the command.
21. If the tape drive specified is in a Given State, the issuer must be the user ID to whom the tape drive was given, or the command is not performed.
22. This command terminates all Concurrent Copy (CONCOPY) sessions for your virtual machine.
23. The IPL command can be invoked without operands if both of the following conditions are true:
    • A previous IPL command was successful.
    • The IPL command is entered without abbreviation (that is, is entered as IPL rather than I or IP).
    In such a case, the operands of the last successful IPL command are used.

    If the IPL command is invoked without operands and either of the conditions are false, then an error message is issued.

24. If an external security manager is installed on your system, you might not be authorized to enter this command. For additional information, contact your security administrator.
25. A list-directed IPL is an IPL that is initiated when an IPL command or IPL directory statement specifies one of the following operands:
    • fcp_vdev
    • LOADDEV
    • DUMPDEV (DUMPDEV is not a valid operand for IPL directory statements)

    In these cases, the IPL command or IPL directory statement operands do not provide all required information for the IPL. List-directed IPL parameters (LOADDEV and DUMPDEV parameters) provide the IPL information that the IPL command or IPL directory statement operands don't provide.

    Most list-directed IPL parameters specify information that cannot be entered as operands on the IPL command or IPL directory statement. (The one exception is the DEVICE parameter, which value can be specified by the fcp_vdev operand of the IPL command or IPL directory statement.)

    Table 1 lists parameters that are used in list-directed IPLs.

    Table 1. LOADDEV and DUMPDEV parameters

    Parameter	Description	Device type	Default value
    DEVICE	The number of the virtual device that is IPLed	SCSI and ECKD	There is no default value
    PORTNAME	The fibre channel port name of the device that is IPLed	SCSI only	01
    LUN	The logical unit number of the device that is IPLed	SCSI only	01
    BR_LBA	The logical-block address of the boot record	SCSI only	0
    BOOTPROG	The number of the boot program	SCSI and ECKD	0
    SECURE/NOSECURE	Specifies whether the IPL is a secure IPL	SCSI and ECKD	NOSECURE
    ALTERNATE	Specifies the device number and fibre-channel port name of an alternate path to the IPL device.	SCSI only	There is no default value
    SCPDATA	Information that is passed to the program that is loaded during IPL	SCSI and ECKD	There is no default value
    BOOTREC	The boot record location on the device that is IPLed	ECKD only	LABEL

    Note:

    1. The default value 0 is not a valid device port name and not a valid device LUN. An IPL attempt that uses the default value for the PORTNAME or LUN parameter will fail.

    Table 2 shows which LOADDEV and DUMPDEV parameters have default values that must be set (changed from the default) before each type of list-directed IPL can be started. Other parameters might need to be set if the default values are not appropriate for your environment.

    Table 2. LOADDEV and DUMPDEV parameters requirements by type of list-directed IPL

    IPL type	DEVICE parameter	PORTNAME parameter	LUN parameter	SECURE parameter
    IPL fcp_vdev	The DEVICE parameter is not set or matches fcp_vdev on the IPL command	Required	Required	Not allowed
    IPL fcp_vdev DUMP
    IPL LOADDEV from SCSI device	Required	Required	Required	Required if the SECUREIPLREQ option is specified in the OPTION directory statement
    IPL LOADDEV from ECKD device	Required	Not applicable	Not applicable
    IPL DUMPDEV from SCSI device	Required	Required	Required	Required if the previous IPL used the SECURE parameter or if the SECUREIPLREQ option is specified in the OPTION directory statement
    IPL DUMPDEV from ECKD device	Required	Not applicable	Not applicable

    There are two groups of parameters for list-directed IPLs:

    LOADDEV parameters

    LOADDEV parameters provide IPL specifications when the IPL does not include a dump.

    DUMPDEV parameters

    DUMPDEV parameters provide IPL specifications when the IPL does include a dump.

    In each group, a value can be set for each parameter that is listed in Table 1. The values of the LOADDEV and DUMPDEV parameters are independent of each other and do not affect each other. The settings for LOADDEV parameters are displayed by the QUERY LOADDEV command. The settings for DUMPDEV parameters are displayed by the QUERY DUMPDEV command.

    For more information, see QUERY LOADDEV and QUERY DUMPDEV in z/VM: CP Commands and Utilities Reference.

26. Parameters for a list-directed IPL without dump (also called LOADDEV parameters) are set by using any of the following methods:
    • SET LOADDEV command.
    • LOADDEV user directory statement. The LOADDEV user directory statement can be modified by a directory management tool such as IBM Directory Maintenance (DirMaint). To set load parameters by using DirMaint, use the DIRM LOADDEV command. The LOADDEV user directory statement can be modified also by the Image_IPL_Characteristics_Define_DM API function.

    Parameters for a list-directed IPL with dump (also called DUMPDEV parameters) are set by using the CP SET DUMPDEV command.

    For more information, see SET LOADDEV and SET DUMPDEV, LOADDEV Directory Statement in z/VM: CP Planning and Administration, DIRM LOADDEV in z/VM: Directory Maintenance Facility Commands Reference, and Image_IPL_Characteristics_Define_DM API function in z/VM: Systems Management Application Programming.

27. A secure IPL is required in the following situations:
    • A user's OPTION directory statement includes the SECUREIPLREQUIRED option. For a secure IPL, the IPL command must use the LOADDEV operand (for IPL without dump) or the DUMPDEV operand (for IPL with dump).
    • A guest's previous IPL was a secure IPL and the current IPL includes a dump. For a secure IPL in this case, the IPL command must use the DUMPDEV operand.
28. To initiate a secure IPL by using the IPL command, the following conditions must be satisfied:
    • The IPL command uses the LOADDEV or the DUMPDEV operand.
    • The DEVICE parameter specifies the virtual device number.
    • The SECURE parameter is set.
    • Other list-directed IPL parameters are set to appropriate values for your environment.
    • The program that is loaded must be signed. The appropriate certificate must be loaded in the HMC and assigned to the LPAR on which the IPL occurs.
29. z/VM® does not support list-directed IPL of a z/VM system from ECKD or a secure IPL of a z/VM system from SCSI or ECKD. The z/VM stand-alone dump utility does not support list-directed IPL from ECKD, and does not support secure IPL from SCSI or ECKD. For more information, see SET LOADDEV and SET DUMPDEV.
30. Up to three alternate paths can be defined as part of a SCSI LOADDEV or DUMPDEV specification. For a SCSI list-directed IPL that is invoked with either the LOADDEV or DUMPDEV operand, if IPL is not successful for the primary device path, then the alternate device paths are automatically considered:
    • If a device is not available, then the next alternate path is considered.
    • Alternate device paths are considered in turn until IPL is successful or all device paths are considered and IPL is not successful.
    Alternate paths are not considered for list-directed IPLs that are invoked by specifying the virtual device number (IPL fcp_vdev). For more information, see SET LOADDEV and SET DUMPDEV.

Options

Optional CMS Initialization Parameters: The following CMS parameters are passed to the system profile EXEC (SYSPROF EXEC). Any unrecognized parameters are ignored by CMS initialization, but are still passed to the SYSPROF EXEC.

CMS users can use the PARM operand to specify any of the following CMS parameters:

AUTOCR

is the automatic carriage return parameter that simulates the pressing of the ENTER key as input to the virtual machine at the initial VM READ. Your PROFILE EXEC is automatically executed if it exists on your file mode A.

BATCH

indicates that the CMS IPL is being performed in a batch instead of an interactive virtual machine.

Use of this parameter does not affect execution of the SYSPROF EXEC. Execution of the SYSPROF EXEC is suppressed only if the NOSPROF parameter was specified.

At the beginning of each job, the batch facility work disk is accessed and immediately erased, preventing the current user job from accessing files that might remain from the previous job. Because of this, execution of the PROFILE EXEC is disabled for the CMS Batch Facility machine. However, if the BATPROF EXEC exists on an accessed system disk, it is invoked instead of the PROFILE EXEC.

FILEPOOL filepoolid

specifies the default file pool that is established as the user's file mode A. If FILEPOOL is not specified, 191 is established as the file mode A.

The following parameters are ignored by the SYSPROF EXEC, but processed by CMS initialization.

NOSPROF

indicates that the SYSPROF EXEC is bypassed. You must specify NOSPROF if you intend to enter the CMSBATCH command when the initial VM READ is issued. When the SYSPROF EXEC does not exist, you do not have to specify NOSPROF to enter the CMSBATCH command.

INSTSEG YES

links the default CMS installation saved segment for this CMS session. The CMS installation-saved segment is an optional shared segment that contains EXECS and editor macros that your installation provides.

INSTSEG NO

indicates that you do not want to use the CMS installation-saved segment during this CMS session.

INSTSEG name

links the named CMS installation saved segment for this CMS session. The segment can be a physical or a logical saved segment.

SAVESYS sysname

is used while creating named systems. The SAVESYS parameter is available only to Class E users. It saves a virtual machine storage space with registers and PSW as they currently exist. The operand sysname must be a predefined name that represents a definition of installation requirements of named system. The definition indicates the number of pages to be saved, the DASD volume on which the system is to be saved, and the shared segments, if any.

After the system is saved, initialization continues, all CMS parameters that are entered on the IPL command are ignored, and SYSPROF EXEC is processed. The parameters that are entered on the original IPL command are not passed to SYSPROF EXEC.

No other parameters can be specified with this parameter. If any other parameters are specified, all parameters are ignored, and a CONFLICT parameter is passed to SYSPROF EXEC, as well as the parameters entered on the IPL command.

MTSEG YES

links the default CMS multitasking segment for this CMS session. The CMS multitasking segment is an optional shared segment that contains the CMS multitasking enablement code.

Note: The CMS multitasking segment is no longer used because the multitasking enablement code is now included in the CMS nucleus. This parameter has no effect and is retained only for compatibility.

MTSEG NO

indicates that you do not want to use the CMS multitasking segment during this CMS session.

Note: The CMS multitasking segment is no longer used because the multitasking enablement code is now included in the CMS nucleus. This parameter has no effect and is retained only for compatibility.

MTSEG name

links the named CMS multitasking segment for this CMS session. The segment can be a physical or a logical multitasking segment.

Note: The CMS multitasking segment is no longer used because the multitasking enablement code is now included in the CMS nucleus. This parameter has no effect and is retained only for compatibility.

Optional CMS Initialization usage notes

1. If you want to use the NOSPROF, INSTSEG, or SAVESYS parameters of the IPL command, you must have PARMREGS=0-15 specified on the DEFSYS command for the CMS named saved system.
2. You can indicate that the CMS initial program load is being performed in a batch rather than an interactive virtual machine. Specify either the BATCH parameter on the IPL command or the NOSPROF parameter, and then enter the CMSBATCH command at the VM READ. Then, a BATPROF EXEC is processed in the batch machine, rather than a PROFILE EXEC. This option causes the CMS nucleus to issue the CMSBATCH command to load the batch processor. Specifying the BATCH option eliminates the need for operator intervention between jobs. See The CMS Batch Facility in z/VM: CMS Planning and Administration for information.
3. AUTOCR should not be used for AUTOLOG users if SET AUTOREAD OFF is in the user's profile.
   Note: For a disconnected CMS service virtual machine, this mechanism can be useful. The name of a CMS restart routine can be specified in the CMS nucleus. In case of an abend, the specified restart routine receives control instead of the service virtual machine entering a disabled wait state. If this routine issues an IPL CMS PARM AUTOCR command, the PROFILE EXEC processes initial setup procedures that allow the service virtual machine to reestablish itself.
4. The SYSPROF EXEC contains some of the CMS initialization function. When you IPL CMS, it is executed by default before any file modes are accessed. The user PROFILE EXEC is invoked after the SYSPROF EXEC. You can bypass the SYSPROF EXEC by specifying the NOSPROF parameter on the IPL command.
5. If you defined disks with virtual device numbers 190 and 19E in the system directory, or if they are defined before you IPL CMS, these disks are accessed as the S- and Y-disks. After you IPL CMS, you must enter explicit ACCESS commands to access other disks. Ordinarily, you have access only to files with a file mode number of 2 on the system disk.

   If you defined disk address 191 and the FILEPOOL parameter is omitted, the 191 disk is accessed as file mode A. However, if the FILEPOOL parameter is specified, your top directory in the identified file pool is accessed as file mode A, even if you also have a 191 minidisk defined. If the access of the top directory fails (perhaps because the file pool is unavailable), the 191 minidisk is accessed. If there is no 191 minidisk, nothing is accessed as file mode A.

   When ACCESS is the first command that is issued after an IPL of the CMS system, file mode A is not automatically defined. Another ACCESS command must be issued to define file mode A.

   For more information, see CMS ACCESS command in z/VM: CMS Commands and Utilities Reference.

6. If you have a disk that is defined as virtual device number 192, the following special rules apply when CMS is IPLed:
   • If 192 is an unformatted temporary minidisk or virtual disk in storage, CMS formats it and accesses it as file mode D.
   • If 192 is a CP-formatted temporary minidisk or virtual disk in storage, CMS reformats it for CMS use and accesses it as file mode D.
   • If 192 is a CMS-formatted temporary minidisk, virtual disk in storage, or permanent minidisk that is accessed as a file mode other than D, CMS reaccesses it as file mode D.
   • If 192 is an unformatted or CP-formatted permanent minidisk, CMS does not automatically format, reformat, access, or reaccess it.

   When CMS accesses a 192 minidisk as file mode D, any minidisk or SFS directory that is already accessed as D is released.

Responses

Usually, after a successful IPL, any responses you receive are those from the operating system that was loaded and initialized.

Trace active at IPL

IPL stop at xxxxxxxx

xxxxxxxx

is the address where execution of the loaded program starts.

After this response is issued, your virtual console is placed into CP READ so that you can enter CP commands (for example, TRACE). After you enter all wanted CP commands, issue the BEGIN command to start the loaded program.

Messages

Messages:

• HCP003E Invalid option - {option|command contains extra option(s) starting with option}
• HCP006E Invalid device type - {rdev|vdev|ldev}
• HCP013E Conflicting option - option
• HCP014E Conflicting operands - operand1, operand2
• HCP022E A virtual device number was not supplied or it was invalid.
• HCP040E Device {rdev|vdev|ldev} does not exist
• HCP044E System {name|volume} does not exist
• HCP052E [XAUTOLOG failed for userid:] Error in CP directory
• HCP053E [XAUTOLOG failed for userid:] userid|value not in CP directory
• HCP059E {XAUTOLOG|AUTOLOG} failed for userid - {IPL missing|IPL failed|accounting errors|incorrect password}
• HCP170E System name exceeds storage size; {nnnnnnnnK|nnnnM} required
• HCP174E Paging I/O error; IPL failed
• HCP175E IPL is not allowed on a secondary CPU; IPL failed
• HCP177E Your PARM data exceeds the limit of nn characters. Correct your data string and reissue the IPL command.
• HCP232E IPL UNIT ERROR, {CSW=csw|IRB=irb}, SNS=sense
• HCP235E IPL with NSSDATA failed because the NSS {exceeds the end of the first extent of guest memory. | contains page range(s) of type SW, SC, or SN. | is defined with the VMGROUP attribute. | extends into unassigned increments.}
• HCP236E The NSSDATA operand is not allowed with the IPL of an NSS.
• HCP237E The NSSDATA operand must be specified after the DUMP keyword for the IPL of an FCP device.
• HCP260E IPL command processing cannot complete due to errors.
• HCP356E Access denied; User userid file spoolid not {changed|transferred|printed}
• HCP410E CP ENTERED; PAGING ERROR
• HCP447E System sysname cannot be IPLed due to an invalid processor configuration.
• HCP449E Your userid is not authorized to IPL system name.
• HCP475I Fatal I/O error trying to read directory from volid [for user userid]
• HCP799E IPL failed due to insufficient or faulty storage
• HCP819I Traceid traceid disabled; group group enabled by traceid
• HCP838E The request process cannot complete due to a processor controller failure.
• HCP1001E An operand is missing for option.
• HCP1013E An invalid operand was supplied for option - operand
• HCP1015E [XAUTOLOG failed for userid:] Insufficient storage is available to satisfy your request.
• HCP1122E command was not performed. Tape vdev has been given to user userid.
• HCP1352E System name cannot be processed.
• HCP1600E Specified cylinder number cylinder is not on the virtual DASD.
• HCP1601E The PARM option is not allowed for the system specified with the IPL command.
• HCP1612E Conflicting device numbers were specified on the IPL and SET LOADDEV or SET DUMPDEV commands.
• HCP1614E An IPL without the SECURE option cannot be performed because the system being dumped was IPLed with the SECURE option.
• HCP1614E An IPL without the SECURE option cannot be performed because the virtual machine has the SECUREIPLREQUIRED option set in its directory entry.
• HCP1615E IPL LOADDEV|DUMPDEV failed because not all necessary parameters have been set.
• HCP1616E IPL of a dump program failed because no dump save areas are available. Try again later.
• HCP1617E IPL by device number failed because secure IPL can be done only when using the LOADDEV or DUMPDEV form of the command.
• HCP2813E CP is running on a processor or in a mode that does not support IPL with DUMP to SCSI or ECKD devices.
• HCP2813E CP is running on a processor or in a mode that does not support IPL from SCSI or ECKD devices.
• HCP2815E The virtual storage size must be greater than nnnnM to perform a list-directed IPL.
• HCP2815E The virtual storage size of the CF Service Machine must be greater than nnnnM to load the message processor.
• HCP2815E The virtual storage size must be greater than nnnnM to perform a list-directed IPL with the DUMP option.
• HCP2816I Acquiring the machine loader from the processor controller.
• HCP2816I Attempting IPL via alternate path vdev hhhhhhhh hhhhhhhh.
• HCP2817I Load completed from the processor controller. Now starting the machine loader.
• HCP2818E The request to load the machine loader from the processor controller has been cancelled.
• HCP2824E No {LOADDEV|DUMPDEV} parameters are currently defined
• HCP6056I XAUTOLOG information for userid: The IPL command is verified by the IPL command processor.
• HCP6061I APPC wait canceled; virtual machine has been reset.
• HCP6086I Traceid traceid1 is no longer superseded by VMGROUP trace traceid2.
• HCP6094I User userid will not be traced by trace traceid.
• HCP6097I User userid has restricted tracing to traces defined as BLOCK.
• HCP6525E Authorization request failed.