CLDM - CICS load module map
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.
Syntax
The CICS load module map can be generated in different formats using the options shown in following syntax diagram.
Options
- PATH=pathname
- pathname is 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 path name, that is, it must start with a forward slash (/).
- SYSOUT=sysoutclass
- sysoutclass is 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. - TSQ
- If you issue CLDM TSQ, CLDM generates a CICS load module map in a TSQ(DFHPTFS). You can subsequently browse it by issuing a CEBR DFHPTFS transaction.