Use transaction CLDM to generate a CICS® load module map. The load module map can be used by the z/OS® hardware instrumentation service or during problem determination to help identify a program that has been loaded by the CICS loader domain.
The CICS load module map can be generated in different formats using the options shown in following syntax diagram.
PATH=pathname
The name of an existing USS file system path that CLDM uses to store a z/OS hardware instrumentation services CICS load module map. The path name must be an absolute pathname; that is, it must start with a forward slash (/).
The existing USS file system path is typically in lower case or
mixed case. By default, CLDM converts all the characters to lower
case in the value that you enter for the PATH option. To specify a
USS file system path that is in mixed case, ensure that the UCTRAN
attribute of the TYPETERM definition for the terminal is set to TRAN
or NO, and enclose the value that you enter for the PATH option in
single quotes. (If UCTRAN is set to YES, and you enclose the value
in single quotes, the value is converted to upper case.)
The file name written to the specified USS file system path is
generated by CLDM and has the format SYSHISTyyyymmdd.hhmmss.asidx.jobname.CICSMAP,
where:
yyyymmdd is the year, month, and day that CLDM
ran.
hhmmssis the hour, minute, and second that
CLDM ran.
asidx is the 4-byte hexadecimal address space ID of the CICS region.
jobname is the CICS job name.
The format of records written to the USS file system is described in the z/OS System Commands manual, in the table 'Interpreting the information in a .MAP file from hardware data collection'. However the following conditions apply:
CLDM generates data records only with record types of M (Module)
and C (CSECT).
For module (record type M) records, if the module is in an LPA
region (that is MLPA, PLPA, or FLPA), the memory area is always set
to M.
The long name (VOLSER and DSN) field is always blank for module
records.
Note: It is the CICS region user ID and not the user ID associated with the CLDM transaction that is checked for authority to create the file in the USS file system.
SYSOUT=sysoutclass
The sysout class that CLDM must use to produce a loader program map report. CICS must have the CICS spool interface active (SPOOL= YES in the SIT) for the SYSOUT operand to be effective. No other spool-related attributes must be specified. You can invoke CLDM in the following ways:
Run the transaction from a 3270 terminal. Input is received from
the terminal and messages are sent to the terminal.
CLDM can be started from a CICS API START command.
Input is retrieved from the START command and messages
are sent to the console.
Link to DFHLDMAP. The input is obtained from the current channel
in a container DFHLDM.INPUT and messages are written to the container
DFHLDM.OUTPUT.
Note: This support is intended to map executable code. Literal
pools cannot be included in the CSECT mappings for this release.
