DUMPLD2

Read syntax diagramSkip visual syntax diagram DUMPLD2 SPOOLFILEDASDAUTomaticSMAllMEDiumLARgeOUTfilePRBxxxxxOUTfilefnTOATO*fmlistvdevlist

Purpose

Use the DUMPLD2 utility as an alternative to DUMPLOAD, to segment a dump into multiple files in order to load or transmit it. The utility will handle all dump types currently supported by DUMPLOAD, except for multiple address space dumps. Hard Abend, Soft Abend, SNAPDUMP, and VMDUMP will be handled. Stand-alone dumps will also be handled.

Operands

SPOOL
indicates dump to be processed is in spool. This is the default.
FILE
indicates the dump to be processed is a single CMS file on disk. If you specify FILE, you must enter the file name of the dump and file mode where it can be found. The file type is assumed to be ‘DUMP0001’.
DASD
indicates the dump to be processed is on DASD and was written by stand-alone dump. You will be prompted to enter the virtual device number of the first device containing the dump. DUMPLD2 will read data from that device and display information about which devices contain the dump. All of those devices need to be defined, attached, or linked, as appropriate, before DUMPLD2 will process the dump.

The DUMPLD2 utility requires all of the real devices that are part of the stand-alone dump configuration to be attached at the same virtual device numbers that were used when SDINST formatted them. If this is not the case, error messages are displayed and the dump is not loaded. To help you set up the devices correctly, the DUMPLD2 utility displays a device table which has a DUMPLD2 VDEV column that shows the virtual device at which the real device must be attached. You can use the CP DEFINE command to change the virtual device number if the device is attached at the wrong number.

If the dump was written to SCSI DASD, you must respond with the virtual device number of the first emulated device (EDEV). Additional dump DASD must be defined at sequential virtual device numbers starting after the first number specified by the user.

AUTomatic
indicates that the record count of each output file will be determined by the sizes of the disks specified by the user. The record count will be calculated based on the disk space available on the specified file modes and virtual device addresses. File modes and virtual device addresses that have less than 65,536 (the ‘small’ record count) available will be ignored. The smallest available space on any of the remaining file modes or virtual device addresses will be compared to the “small” “medium” or “large” values. The largest of these 3 sizes to fit in that space will be chosen as the record count for each of the CMS files created. This is the default if the record count parameter is omitted.
SMAll
indicates the record count of each file will be:
  • 65,536 records, which is approximately .25 G, or 365 cylinders on a 3390 disk.
MEDium
indicates the record count of each file will be:
  • 262,144 records, which is approximately 1 G, or 1460 cylinders on a 3390 disk.
LARge
indicates the record count of each file will be:
  • 1,048,576 records, which is approximately 4 G, or 5825 cylinders on a 3390 disk.
OUTfile fn
is a keyword for specifying the file name for the CMS files (of file type MDMPxxxx) to be created. If fn is omitted, the utility will produce an error message and exit.
Note: If ‘OUTFILE’ is omitted, the multiple dump files will have a file name of format “PRBxxxxx”, where “xxxxx” is an unused number from 00000 to 99999, chosen by the utility.
TO
is a keyword indicating the disks on which the CMS files should be created (of file type MDMPxxxx). The user may specify file modes or virtual device addresses, or a combination in any order. If the user does not specify any file modes or virtual device addresses after ‘TO’, the utility will display an error message and exit.
Note: If ‘TO’ is omitted, the MDMPxxxx files will be written to the A disk.
fmlist
indicates the set of file modes on which to create the CMS files (MDMPxxxx). Accepted inputs include:
  • a blank delimited list: “A D E F”
  • a range: “A-F”, indicating all R/W file modes in that range are to be used.

If a specified file mode is not accessed or is not R/W, it will be ignored and not used.

vdevlist
indicates the set of virtual devices on which to create the CMS files. Accepted inputs will include:
  • a blank delimited list of 3 or 4-digit hex values: “0122 125 0121”
  • a range: “0121-012E” (3 or 4 digit hex values are accepted)

If a specified virtual device is not attached as a CMS DASD, or is not R/W, it is ignored and not used.

Note: The user must have at least one free file mode available so that a virtual device may be accessed if it is not currently accessed.
*
indicates that the utility will search for available R/W file modes and use them in order of search sequence.

Usage Notes

  1. You can use the CMS files you create with DUMPLD2 as input for the VM Dump Tool.
  2. If you use DUMPLD2 to read a dump from a reader spool file, the system changes the file to User ‘HOLD’ status and does not purge it upon completion of the command processing.
  3. If DUMPLD2 runs out of file modes or virtual devices during the processing of a dump, DUMPLD2 stops but does not erase the CMS files it has created, including a possibly incomplete one. You can use the VM Dump Tool to view the files you do have, or you can obtain more space and reissue the DUMPLD2 command. It will start from the beginning and recreate all files as if it had never been run – the existing files will be overwritten. If you wish to keep the old files, specify another file name when re-invoking DUMPLD2.
  4. After the ‘TO’ operand, a combination of fmlist, vdevlist and ‘*’ may be intermixed in any order.
    • For example, “D 0120-012F A-C *” is valid.
  5. You can specify fmlist or vdevlist for as many file modes or VDEVs as you have – duplicate values will be ignored.
  6. Every CMS file that DUMPLD2 produces will have the file type of “MDMPxxxx”.
  7. If you are processing a Hard Abend dump, the frame table must not span over the first two different unaccessed virtual device addresses.
    • If the first disk specified is an unaccessed VDEV, the frame table must be contained within the multiple files on that VDEV.
    • If the first few disks specified are file modes, the frame table must be contained within the multiple files on these file modes and must not span to an unaccessed VDEV.
  8. If one of the file modes specified is an SFS directory, multiple dump files are loaded up to the space limits for that directory. The utility will not calculate in advance how many files will be written or if there will be sufficient space to load the entire dump.
  9. ‘VMLINK’ is used to temporarily access virtual device addresses. The file modes used to temporarily access virtual device addresses are chosen according to the default settings in ‘VMLINK’.
  10. The order in which file modes, virtual device addresses, or SFS directories are specified after the 'TO' operand is the order to which they are written.

Messages

  • HCP002E Invalid operand operand
  • HCP0003E Invalid option - command contains extra option(s) starting with operand
  • HCP0026E Operand missing or invalid
  • HCP022E A virtual device number was not supplied or it was invalid.
  • HCP1008E Device userid vdev is not a DASD
  • HCP040E Device vdev does not exist
  • HCP8164E Dump file name fn is not a valid CMS file name
  • HCP8170E There are no default file names available
  • HCP8178E Dump file mode filemode invalid
  • HCP8210I numfiles fn MDMPxxxx file(s) will be created on disk filemodenumfiles fn MDMPxxxx file(s) will be created on VDEV vdev
  • HCP8211E Please reset SPOOL READER class to V, D or *
  • HCP8212E No unheld class V or class D files exist in SPOOL
  • HCP8213I Created fileid
  • HCP8214I Duplicate values will be ignored duplicates
  • HCP8215I DUMPLD2 cannot determine how many files will be written to the SFS directory specified
  • HCP8216I n files have been written to the SFS directory at file mode – mode
  • HCP8217E Error in erasing incomplete file – ERASE rc = rcError in copying incomplete file to next disk – ERASE rc = rc
  • HCP8218E Incorrect mode mode in range - range
  • HCP8219E VDEV must be a hex value - vdev
  • HCP8220E VDEV must be 3 or 4 digits - vdev
  • HCP8221E Incorrect range specified - range
  • HCP8223E File mode mode is not accessed
  • HCP8224E File mode mode is not R/W
  • HCP8225E Device vdev does not exist
  • HCP8226E Device vdev is not formatted as CMS DASD
  • HCP8227E Device vdev is not R/W
  • HCP8228E Insufficient space for any files – device
  • HCP8229E Error in writing to file fileid – EXECIO rc = rcError in closing file fileid – FINIS rc = rc Error in opening file fileid – EXECIO rc = rc
  • HCP8230E Insufficient disk space to continue.. Exiting
  • HCP8231E Error in accessing disk – VMLINK rc = rcError in releasing disk – VMLINK rc = rc
  • HCP8232E File name must be specified with the OUTFILE operand
  • HCP8234E Fn DUMP0001 mode not found
  • HCP8235E No usable devices/disks specified
  • HCP8236E Must specify file modes or VDEVs after the TO operand
  • HCP8237I TO operand not specified. MDMPxxxx files will be created on A disk
  • HCP8238I System dump not found. Searching for VMDUMP
  • HCP8239A Dump File Name?
  • HCP8240A Dump File Mode?
  • HCP8241I Automatic file size chosen – filesize records
  • HCP8242I Insufficient disk space to create the remaining n files
  • HCP8243I Dump is not complete: records records written of totalrecords expected
  • HCP8243I Dump not complete when it was created; it contains no CP storage. Only number records were copied from the SPOOL file and written to the CMS file.
  • HCP8243I Dump not complete when it was created; it contains some CP storage. RecsWritten of expected number records were dumped.
  • HCP8243I Dump not complete when it was created; it contains some CP storage. RecsWritten records written.
  • HCP8244E DUMPLD2 failed because no R/W File Modes are available
  • HCP8245E File mode incorrect – mode
  • HCP8246E DUMPLD2 cannot create more than 9999 files from one dump
  • HCP8247E HCPxxx MODULE was not found so it could not be used to determine whether the dump is complete.
  • HCP8248E QUERY READER spoolid and DIAGNOSE X'14' spoolid mismatch. Make sure the dump spool file is ORDERed to top of READER queue.
  • HCP8249I The dump is larger than what QUERY READER command shows. It really has nnnnnnnnnn records.
  • HCP8277E Pipe error rc processing the dump.
  • HCP8278E Enter virtual device number of first dump device.
  • HCP8281E Device vdev has unexpected format: format
  • HCP8282E Device vdev appears to be formatted as an additional stand-alone dump DASD and not as the IPL DASD
  • HCP8283E Error rc during function
  • HCP8284E Format of item on device vdev was not as expected.
  • HCP8285E Error validating dump data - data description Reason code rc
  • HCP8286E Device vdev does not contain a dump
  • HCP8287E Generated VDEV past maximum allowed VDEV
  • HCP8288E Pipe error, rc=rc, while putting records into the pipe
  • HCP8289E No output stream for pipe
  • HCP8290E Unexpected error. Location number