MAP Command

Read syntax diagramSkip visual syntax diagram MAP PROmptNOPromptinfile1infile2outfile(type)

Purpose

Use the MAP command to convert a load map into a format that the Dump Viewing Facility can process. The converted load map, which is called the module map, serves as input to the ADDMAP command. ADDMAP appends the converted load map to the dump file. The Dump Viewing Facility requires primary and secondary load maps to create certain types of module maps.

When you invoke MAP, you may request or suppress prompting. You may specify the files or accept the default files for processing.

Operands

PROmpt
requests prompting. PROMPT is the default. Prompting occurs in the following sequence:
  1. The Dump Viewing Facility asks first for one of the following:
    type
    specifies the type of module map to create. See Table 1 for a list of types.
    null line
    accepts the default type: CMS.
    SUBSET
    invokes CMS subset mode.
    HX
    terminates the MAP command.
  2. You may then supply output and input files:
Read syntax diagramSkip visual syntax diagram fn ftfm
 
specifies each file to process. You are prompted for the output file ID, the primary input file ID, and the secondary input file ID (if necessary). If you do not specify the file type or file mode, the file type defaults to MAP, and the file mode defaults to *.
null line
accepts a predefined file ID. See Table 1 for default input and output map file IDs.
SUBSET
invokes CMS subset mode.
HX
terminates the MAP command.
NOPrompt
suppresses prompting altogether. The Dump Viewing Facility uses the default input and output file IDs for the module map type that you specify. Table 5 shows the file IDs associated with each type.
Note: SFS includes coordinated resource recovery facility.
infile1
indicates the file name, file type, and file mode of the input CMS file containing the primary load map.
infile2
indicates the file name, file type, and file mode of the input CMS file containing the secondary load map required to create certain types of module maps. To create a module map for a supported type that requires a secondary load map, MAP processes the CMS nucleus load map (infile1) and then the secondary load map (infile2).
outfile
is the file name, file type, and file mode of the resulting CMS file containing the module map, which is used as input to the ADDMAP command.

Options

type
specifies a type of module map for the MAP command to create. You may specify one of the module map types listed below. If you do not specify a module map type, type defaults to CMS.

The following table lists the module maps which may be created using the Dump Viewing Facility. If you wish to create another type of module map see, Using Attachment Interfaces.

Table 1. Maps Processed by the MAP Command
Module Map Type Module Map Component Load Map Type Nucleus Default Input Map File Default Output Map File
CMS Primary CMS Yes CMSNUC MAP * CMSDVF MAP A
DFSMS Primary CMS Yes CMSNUC MAP * DFSMSDVF MAP A
Secondary DFSMS No FSMDFSMS MAP *
GCS Primary GCS Yes GCSNUC MAP * GCSDVF MAP A
PVM Primary CMS Yes CMSNUC MAP * PVMDVF MAP A
Secondary PVM No PVM MAP *
SECP Primary GCS Yes GCSNUC MAP * SECPDVF MAP A
Secondary SECP No SECP MAP *
TSAF Primary CMS Yes CMSNUC MAP * TSAFDVF MAP A
Secondary TSAF No TSAF MAP *

Usage Notes

  1. MAP requires primary and secondary load maps for certain module map types (see Table 1). If you specify a file ID for one of these types on the command line, you must specify infile2. If you do not specify infile2, you receive an error message and command processing terminates.

    Other map types do not require secondary maps. If you specify infile2 for one of these types, you receive an error message and command processing terminates.

  2. MAP does not issue prompting messages when you specify file IDs or enter NOPROMPT on the command line. If an error occurs or you do not specify a required file ID, you receive an error message and command processing terminates.
  3. AVS, RSCS, and SFS do not have separate maps. AVS and RSCS require that the GCS NUCLEUS map be added to their dumps. SFS requires a CMSNUC map be added to the dump.

Messages and Return Codes

Return Code
Explanation
0
Successful completion
20
Invalid file ID
24
Command line error
28
Missing files or file already exists
32
Invalid data in file
36
Disk not accessed
41
Insufficient storage
50
CP dumps are not supported. Use VM Dump Tool
100
FSREAD/PRINTL failure
104
Internal processing error