SDINST

Purpose

Use the SDINST utility to build a configuration file used for a stand-alone dump containing device addresses for dump IPL DASD as well as additional dump output devices.

Usage Notes

The user must have a R/W minidisk at device number 191 and accessed as file mode A. The configuration file is written there.
The SDINST utility creates a file called SDINST DUMPCONF on the user's A-disk. If the file is found at runtime, the user can choose to continue to install stand-alone dump using the existing file, or continue normal configuration and create a new file.
SDINST also creates a dump status file called SDINST CMSUT1 on the user's A-disk. The file contains information for SDINST's DASD formatting routine. This file is recreated each time SDINST is run and can be erased by the user if desired.
ECKD or SCSI DASD can be used as dump devices, however devices must be all ECKD or all SCSI.
There is a maximum of 30 DASD, including the IPL DASD.
The SDINST utility expects a virtual reader device at virtual device number 00C and a virtual punch device at virtual device number 00D.
The SDINST utility requires at least 512 MB of virtual storage in order to load its DASD formatting program.
The SDINST utility requires that your virtual machine does not have any existing class N reader files.
The SDINST utility requires the following files, all of which have a filetype of IMAGE: SADUnn, SSPInn, SSPKnn, and SSPPnn. The nn is a version number that SDINST supplies and with which it is compatible. In a standard z/VM installation, the MAINT 400 disk contains these files and should be accessed before running SDINST. The SDINST utility also looks for these files on the 191 disk before the 400 disk, so that service can be tested before it is installed. Files with matching names on other accessed disks are ignored.
The first dump device is formatted to contain the stand-alone dump program and is made IPLable. It is required to be large enough to hold the program plus some minimal space for a dump. For dumping a first-level system (LPAR), each dump device is an entire 3390 or SCSI LUN. Currently, a 3390 used by stand-alone dump is limited 65520 cylinders when allocated on an IBM® TotalStorage DASD subsystem. That is approximately 45 GB of data. The maximum SCSI device support is limited to about 1 TB because VM's EDEVICE support is used when loading the dump.
When using the stand-alone dump program to dump a second-level system, minidisks may be used. The minidisk used for the IPL device must be at least 75 cylinders. Minidisks for additional dump devices could be as small as 1 cylinder but that is not a reasonable size for dump devices. The minimum SCSI LUN sizes are equivalent: 53 MB for the IPL device and 0.7 MB for additional dump devices.
For additional instructions on creating a stand-alone dump utility on ECKD and SCSI devices, taking a stand-alone dump, and processing a stand-alone dump, see Chapter 12, "The Stand-Alone Dump Utility", in z/VM: CP Planning and Administration.

Examples

Typical use of the SDINST utility with no pre-existing configuration file using one 3390 DASD:

  >>> SDINST
  HCPSDI8682I STAND-ALONE DUMP INSTALLER Vv.r
  ENTER 'QUIT' AT ANY PROMPT TO TERMINATE EXECUTION.
  HCPSDI8654A PLEASE ENTER THE VIRTUAL DEVICE ADDRESS OF THE IPL DASD
  555
  HCPSDI8655A PLEASE ENTER THE REAL DEVICE ADDRESS FOR THIS DASD
  OR ENTER Y TO USE 0555
  y
  HCPSDI8674A DASD HAS EXISTING VOLID DSD555.
  DO YOU WISH TO CONTINUE? (Y/N)
  y
  HCPSDI8658A ARE THERE ANY ADDITIONAL DUMP DASD TO SPECIFY? (Y/N)
  n
  SSPK73  IMAGE  F1 F   80     113581     1738 yyyy-mm-dd hh:mm:ss
  SSPP73  IMAGE  F1 F   80          1        1 yyyy-mm-dd hh:mm:ss
  SSPJ73  IMAGE  F1 F   80      76478     1494 yyyy-mm-dd hh:mm:ss
  SADU73  IMAGE  F1 F   80      15655      306 yyyy-mm-dd hh:mm:ss

  CP SPOOL PUNCH CL N TO * NOHOLD NOEOF NOKEEP
  RDR FILE 1146 SENT FROM MYUSERID PUN WAS 1146 RECS 114K CPY 001 N ...
  RDR FILE 1147 SENT FROM MYUSERID PUN WAS 1147 RECS 0001 CPY 001 N ...
  RDR FILE 1148 SENT FROM MYUSERID PUN WAS 1148 RECS 076K CPY 001 N ...

  CP SPOOL RDR   CL N NOHOLD EOF
  SPOOL RDR OPTIONS HAVE BEEN CHANGED TO CLASS N, NOHOLD AND EOF.
  IF FOLLOWING IPL IS SUCCESSFUL, YOU WILL NEED TO RESTORE SPOOL
  RDR OPTIONS MANUALLY BECAUSE CONTROL DOES NOT RETURN TO THIS EXEC.

  EVERYTHING IS READY. ANSWER Y TO CONTINUE AND IPL THE DASD FORMATTING
  PROGRAM. ANY OTHER RESPONSE EXITS WITHOUT DOING THE IPL.
  y
  CP IPL 00C CLEAR PARM loglevel=0 sspmod=SADU73:191
  HCPSDI8660I SETTING DEVICE 0191 ONLINE.
  HCPSDI8662I FORMATTING 3339 CYLINDERS ON DEVICE 0555.
  HCPSDI8664I WRITING PARTITION TABLE TO DEVICE 0555.
  HCPSDI8666I CREATING FILE SYSTEM FOR IPL PARTITION ON DEVICE 0555.
  HCPSDI8668I INSTALLING STAND-ALONE DUMP TO IPL PARTITION ON
  DEVICE 0555.
  HCPSDI8670I STAND-ALONE DUMP INSTALLATION IS COMPLETE.
  YOU MAY RE-IPL CMS.

Messages

HCP002E Invalid operand - operand.
HCP1004E operand is not a DASD volume or is an invalid DASD type.
HCP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU nn.
HCP6741E Disk operand is not CP or CMS formatted.
HCP8219E VDEV must be a hex value - operand
HCP8225E Device operand does not exist
HCP8227E Device operand is not R/W
HCP8625E Image file mismatch.
HCP8639E This version of the SDINST utility requires hardware features not available on this processor.
HCP8640E Device vdev is not a devtype
HCP8641E Insufficient virtual storage to run the program that formats the stand-alone dump DASD. You need at least 512 MB to proceed.
HCP8642E This process can not proceed if you already have Class N RDR files.
HCP8643E STATE error rc for required file file.
HCP8644E PUNCH error rc for file file.
HCP8645E Error rc for command command.
HCP8647E Device vdev must have a label.
HCP8648E THE SDINST UTILITY DOES NOT RUN IN A VIRTUAL MACHINE THAT IS IN ESA/XC OR Z/XC MODE.
HCP8649E Error rc when obtaining device size.
HCP8650E SDINST requires a 191 minidisk accessed R/W as file mode A.
HCP8651E vdev is a {3390|SCSI} DASD, but IPL DASD is {3390|SCSI}. All DASD must be the same type.
HCP8652E DASD at virtual address vdev is not large enough to install stand-alone dump.
HCP8653E Volume ID of vdev is volid instead of expected volid.
HCP8654A Please enter the virtual device address of the {IPL|additional dump} DASD.
HCP8655A Please enter the real device address for this DASD or enter Y to use rdev.
HCP8656A Please enter the 16 hexadecimal digit WWPN for this DASD.
HCP8657A Please enter the 16 hexadecimal digit LUN for this DASD.
HCP8658A Are there any additional dump DASD to specify? (Y/N)
HCP8659E Attempted to define more than 30 dump devices.
HCP8660I Setting device devno online.
HCP8661E Could not bring device devno online.
HCP8662I Formatting xxxxxxx cylinders on device devno.
HCP8663E There was a problem formatting device devno.
HCP8664I Writing partition table to device devno.
HCP8665I There was a problem writing partition table to device devno.
HCP8666I Creating file system for IPL partition on device devno.
HCP8667E There was a problem creating the file system for the IPL partition on device devno.
HCP8668I Installing stand-alone dump to the IPL partition on device devno.
HCP8669E There was a problem installing stand-alone dump to the IPL partition on device devno.
HCP8670I Stand-alone dump installation is complete. You may re-IPL CMS.
HCP8671A Existing File SDINST DUMPCONF A found. Enter O to overwrite, C to continue using the existing file or anything else to quit.
HCP8672I Stand-alone dump installation aborted.
HCP8673E Device type for vdev vdev is not as expected.
HCP8674A DASD has existing volid volid. Do you wish to continue? (Y/N)
HCP8675E SDINST failed because no file modes are available.
HCP8676E Existing file file is not a valid stand-alone dump configuration file.
HCP8677E Existing file file was created with an older version of the SDINST utility and is no longer compatible.
HCP8678E Existing file file was created with a newer version of the sdinst utility. Please use the newest version of SDINST.
HCP8679E There was a problem with the DASD specified starting on line line.
HCP8680E Parsing failed on line line. Check previous error message.
HCP8681E There can be only one IPLDASD statement in a stand-alone dump configuration file.
HCP8682I Stand-alone Dump Installer Vversion enter 'QUIT' at any prompt to terminate execution.
HCP8683E VDEV must be 1 to 4 digits - vdev.
HCP8684E Size of the SCSI device devno can not be larger than 2,147,483,640 512-byte blocks.
HCP8684E Size of the 3390 device devno can not be larger than 65520 cylinders.
HCP8685E operand value missing.
HCP8686E RDEV value not valid - operand. It must be a 1 to 4 digit hex number.
HCP8687E WWPN must be 16 digits - operand
HCP8688E WWPN must be a hex value - operand
HCP8689E LUN must be 16 digits - operand
HCP8690E LUN must be a hex value - operand
HCP8691E VDEV vdev cannot be accessed at file mode A.
HCP8692E operand was already specified.
HCP8693E IPLDASD statement must be the first configuration statement in file file.
HCP8694E The stand-alone dump DASD formatting module is incompatible with this version of the SDINST utility.
HCP8695E Could not read configuration data from 191 disk.
HCP8696E An unexpected error has occurred and stand-alone dump installation has been aborted. You may re-IPL CMS.
HCP8697E The stand-alone dump DASD formatting module encountered invalid configuration data.
HCP8698E keyword keyword on line line is not valid when device type is devtype.
HCP8699E Found second occurrence of keyword keyword on line curr for statement starting on line line.