SALIPL

Read syntax diagramSkip visual syntax diagram SALIPL vdev (MOduleCPLOADOFfset0ORIGIN10001(Options2
Options
Read syntax diagramSkip visual syntax diagramExtentnMinivolNOVERIFYvolid*MOduleCPLOADMOdulefilenameOFfset0OFfsetnnnnnnnnORIGIN10001ORIGINhexlocVolidNOVERIFYvolid*WWPNwwpnLUNlunDevicerdevCommentstext?Iplparmstext?
Notes:
  • 1 CP will relocate itself to 2000. The default ORIGIN in a z/Architecture®-only environment is 2000; otherwise, the default is 1000.
  • 2 You can enter Options in any order.

Purpose

Use the SALIPL utility to install a copy of the Stand-Alone Program Loader (SAPL) in cylinder zero or, in the case of FBA DASD, in blocks 5 to 207 of a disk.

The SALIPL utility can run under CMS or it can be loaded by SAPL to run stand-alone. There is also a version of SALIPL that can be IPLed stand-alone from tape or card readers. For information on Running the Stand-Alone Program Loader Creation Utility (SALIPL) refer to z/VM: System Operation.

When SALIPL writes SAPL to the IPL volume, defaults for the following attributes that SAPL uses are established:
  • The location of the CMS minidisk where modules can be found
  • The name of the module that is to be loaded by SAPL
  • The location in storage at which the module will be loaded, if it is relocatable
  • The IPL parameters that are passed to the program being loaded
  • Operator instructions that are displayed on the SAPL screen.

Operands

vdev
specifies the virtual device number (vdev) representing the dedicated volume, full-pack minidisk, or regular minidisk on which SAPL is to be installed. The virtual device may be located on an emulated device.

If SAPL is installed on a regular minidisk, it cannot be IPLed in stand-alone mode. This type of SAPL installation is typically used for initializing second level systems and utilities that need to run stand-alone in a virtual machine.

The vdev operand may specify an FCP device. If this is done, the WWPN and LUN options must be specified.

Options

Extent n
specifies which minidisk extent on a CP-formatted volume contains the module to be loaded. n is a single decimal number from 1 to 9. 1 refers to the first extent formatted as ‘PARM’, while 9 refers to the ninth such extent.
Note: If you specify EXTENT, you cannot specify OFFSET.
Minivol
specifies whether SALIPL should check the label of the CMS formatted minidisk from which SAPL will load the module. If MINIVOL is not specified, SALIPL skips the check but displays the minidisk label when installing SAPL.
NOVERIFY
specifies that SALIPL is not to check for a matching minidisk label and the label of the minidisk should not be displayed in response to the SALIPL invocation.
volid
is a 1- to 6- character minidisk label. If the minidisk identified by OFFSET does not have a matching label, SALIPL issues an error message and no new loader is installed on the target vdev. If the minidisk does have a matching label or if volid is specified as an asterisk (*), no minidisk label is displayed in response to the SALIPL invocation.
MOdule
specifies the file name of the module that SAPL is to load.
CPLOAD
is the default module name.
filename
is the file name of the module that SAPL is to load. The file type of the module must be MODULE.
OFfset nnnnnnnn
specifies the offset from the beginning of the disk (identified by vdev) at which the CMS-formatted minidisk containing the module resides. You can specify up to 10 digits for OFFSET. For CKD and ECKD DASD, the offset is specified as the number of cylinders from the beginning of the disk. For FBA DASD, the offset is specified as the number of blocks from the beginning of the disk.

If you do not specify OFFSET or EXTENT, the default is OFFSET 0.

Note: If you specify OFFSET, you cannot specify EXTENT.
ORIGIN
specifies the address at which SAPL should load the module.

This option is ignored by SAPL if the module that is being loaded has not been generated with the RLDSAVE option. In this case, the module is loaded into storage at the location at which the module was generated.

The entire module, including its required CP data structures, must fit below the 2G line.

When loading CP, the ORIGIN option is accepted, but CP will relocate itself to location X'2000'.

X'1000'
is the default address except when SAPL runs in a z/Architecture-only environment, and then the default is 2000.
hexloc
is the address at which to load the module.
WWPN wwpn
specifies the world wide port name for a specific path to a SCSI device. The wwpn must be a 16-digit hexadecimal number between X'00000000 00000000' and X'FFFFFFFF FFFFFFFF'. WWPN is only valid if the vdev operand refers to an FCP device.
LUN lun
specifies the logical unit number for a specific path to a SCSI device. The lun must be a 16-digit hexadecimal number between X'00000000 00000000' and X'FFFFFFFF FFFFFFFF'. LUN is only valid if the vdev operand refers to an FCP device. Note that the number of digits recognized by the SCSI device may vary by manufacturer, type and model. You must be careful to specify all 16 digits, using trailing zeros, as explained in the note below.
Attention:
  1. lun and wwpn must be specified as 16 hexadecimal digits. This can be accomplished by specifying two 8-digit tokens, or by specifying one 16-digit token. CMS command invocation may truncate any token to 8 characters, with no warning. For safest operation, specify these arguments as two 8-digit tokens. However, if you know that the CMS command invocation technique uses extended plist (which is done for commands entered at the console or in a REXX EXEC), you can safely specify the value as a single 16-digit token.
  2. Because SALIPL cannot know how many digits your device recognizes, you must enter all 16 digits. If your SCSI device is identified by fewer than 16 digits, you should use trailing zeros to fill out the 16-digit lun. Note that if you enter non-zero digits following the digits identifying the SCSI device, those extra digits may be ignored by your device. (For example, if your device recognizes a four-digit lun, 5A51888811221122 and 5A51999933443344 would both represent the same device.) This could lead to unintended device sharing and hence might introduce data-integrity exposures.
    Note: Always identify your SCSI device by its actual lun unit number as defined in your storage-area network, padded on the right with zeros.
Volid
specifies whether SALIPL should check the volume serial identifier of the CP or CMS-formatted volume on which SAPL is being installed. If VOLID is not specified, SALIPL skips the check but displays the volume serial identifier when installing SAPL.
NOVERIFY
specifies that SALIPL is to perform no check for a matching volume serial identifier and the volume serial identifier of the vdev should not be displayed in response to the SALIPL invocation.
volid
is a 1- to 6-character volume serial identifier. If the volume identified by vdev does not have a matching volid, SALIPL issues an error message and no new loader is installed on the vdev. If the volume does have a matching volid or if volid is specified as an asterisk (*), no volume serial identifier is displayed in response to the SALIPL invocation.
Device rdev
specifies the address of the device where the minidisk containing the module to be loaded resides. This can be a 5-digit device address, in which case the leading digit specifies the subchannel set number where the device is located. This subchannel set will be used by z/VM to determine which devices belong in the active configuration. If the multiple subchannel set facility is not installed, the leading digit is truncated and subchannel set zero is used. If this operand is not specified, the minidisk is assumed to be located on the IPL device.
Comments
specifies up to 320 characters of text information that is to be displayed to the operator if SAPL is given a console address in the load parm when it is IPLed.
text
is the text to be displayed to the operator.
?
causes SALIPL to prompt the operator for exactly 4 lines of data to be read from the console. Each line is either truncated to 80 characters or padded with blanks out to 80 characters.
Note: When you enter text on the command line, COMMENTS must be the last option you specify.
Iplparms
specifies information that is to be passed to the loaded program by SAPL.
text
specifies up to 240 characters of text information that is to be passed on to the loaded program by SAPL.
Note: When you enter text on the command line, IPLPARMS must be the last option you specify.
The format of the IPL parameters depends entirely on the options supported by the loaded program. For a list of IPL parameters supported by CP, see Passing IPL Parameters in z/VM: System Operation.
?
causes SALIPL to prompt the operator for exactly 3 lines of data to be read from the console. Each line is either truncated to 80 characters or padded with blanks out to 80 characters.

Usage Notes

  1. No special privilege classes are required to run the SALIPL utility. The command issuer must, however, have write access to the volume on which SAPL is to be installed.
  2. If you are running SALIPL from an exec, it is suggested that you provide SALIPL with both the label of the volume on which SAPL is to be installed and the label of the CMS-formatted minidisk from which the module is to be loaded. This information is used by SALIPL to ensure that SAL is being installed on the correct volume and is pointing to the correct minidisk on that volume.
  3. If both IPLPARMS and COMMENTS are specified with a single ‘?’ as parameters, the user is prompted to enter the text for the options in the same order as they were specified on the command line.
  4. If you are IPLing CP from an FCP device (SCSI disk), PDVOL=raddr must be specified as an IPL parameter. Any device address that is not in the I/O configuration of the system to be IPLed can be specified for raddr. CP requires this parameter in order to build the EDEVICE control block for the SYSRES / PARM disk device during CP initialization.
  5. Attention: The number of blocks on FBA DASD (SCSI or not) that SALIPL uses for SAPL has increased. SALIPL writes to blocks 5-207 on CP-formatted DASD. In previous releases, SALIPL wrote to blocks 5-31. You must ensure that no other functions, such as CP directory, warmstart, checkpoint, paging, spooling, or minidisks, are using the area to which SALIPL writes.

    On a CMS minidisk with a RECOMP area, SALIPL writes SAPL to blocks 5-207 of the RECOMP area. In previous releases, blocks 5-31 of the RECOMP area were used. In order to accommodate the larger size of SAPL, you may need to increase the size of the RECOMP area on the CMS minidisk.

    The following data is in the blocks that SALIPL writes out:

    Blocks 5-196               SAPL program
    
    Blocks 197-199             Reserved for IBM Use
    
    Blocks 200-207             SCSI boot records

Responses

If you want to install SAPL on device 0400, a full-pack minidisk to which you have R/W access, and you want SAPL to use the CMS-formatted minidisk that is 210 cylinders into the full-pack minidisk as the disk from which it will read a module, you enter this command, and see the responses:
salipl 0400 (offset 210 module cpnew iplparms fn=sysnew
VOLUME ID IS ESARES
MINIDISK VOLID AT OFFSET 210 IS PARMD1
Ready;

Messages

  • HCP003E INVALID OPTION - {option|COMMAND CONTAINS EXTRA OPTION(S) STARTING WITH option}
  • HCP004E INVALID HEXLOC - hexloc
  • HCP006E INVALID DEVICE TYPE - vdev
  • HCP013E CONFLICTING OPTION - option
  • HCP021E A REAL DEVICE NUMBER WAS NOT SPECIFIED OR IT WAS INVALID.
  • HCP022E A VIRTUAL DEVICE NUMBER WAS NOT SPECIFIED OR IT WAS INVALID.
  • HCP023E VOLID MISSING OR INVALID
  • HCP040E DEVICE vdev DOES NOT EXIST.
  • HCP352E FATAL DASD I/O ERROR
  • HCP393E I/O ERROR ON DISK vdev; INCORRECT RECORD LENGTH
  • HCP394E I/O ERROR; DISK rdev IS BUSY OR HAS INTERRUPT PENDING
  • HCP395E PERMANENT I/O ERROR ON DISK rdev; SENSE=xxxxxxxx
  • HCP396E I/O ERROR. THIN STACK FUNCTION=function RC=rc
  • HCP422E THE SAME OPTION WAS SPECIFIED TWICE
  • HCP1001E AN OPERAND IS MISSING FOR option
  • HCP2218E DISK vdev IS READ-ONLY
  • HCP6207E I/O ERROR; DISK rdev HAS UNSOLICITED STATUS PENDING
  • HCP6741E DISK rdev IS NOT CP OR CMS FORMATTED
  • HCP6742E MINIDISK VOLID AT OFFSET nnnnn IS volid1 NOT volid2
  • HCP6743E MINIDISK AT OFFSET nnnnn IS NOT CMS FORMATTED
  • HCP6744E VOLUME ID IS volid1 NOT volid2
  • HCP6745E BLOCK SIZE IS LESS THAN 4096
  • HCP6746E THE PARAMETER FOR THE {IPLPARMS|COMMENTS} OPTION IS TOO LONG.
  • HCP6747E WWPN and LUN must be specified for an FCP subchannel
  • HCP6794E NO RECOMP AREA DEFINED ON CMS FORMATTED DISK
  • HCP6795E RECOMP AREA IS TOO SMALL ON CMS FORMATTED DISK
  • HCP6796E IPL PROGRAM AREA NOT ALLOCATED PERM
  • HCP6797I MINIDISK VOLID AT OFFSET nnnnn IS volid
  • HCP6798I VOLUME ID IS volid
  • HCP6799E INVALID EXTENT nnnnn
  • HCP6800E INVALID OFFSET nnnnn
  • HCP6801E EXTENT IS NOT VALID WITH A CMS FORMATTED DISK
  • HCP6802E EXTENT NOT FOUND IN ALLOCATION MAP
  • HCP6803I ENTER UP TO n LINES OF {IPLPARMS|COMMENTS}