Using LDD for assembler or LangX COBOL compile units

When you use the LDD command for assembler or LangX COBOL compile units, the LDD command indicates that the compile unit (CU) is an assembler or LangX COBOL CU and z/OS® Debugger loads debug data from the default data set name, userid.EQALANGX(cu_name). If the debug data is stored in a different data set, specify that data set name by using the SET SOURCE command, SET DEFAULT LISTINGS command, or the EQADEBUG DD statement. In remote debug mode, specify the data set name by using the SET DEFAULT LISTINGS command, the EQADEBUG DD statement, or providing the data set name when the remote debugger prompts you for it.

Generate the required debug information by using the EQALANGX program or, if you are debugging an assembler program, by assembling your program through IBM® z/OS Debugger Utilities, as described in IBM z/OS Debugger User's Guide.

Read syntax diagramSkip visual syntax diagramLOADDEBUGDATALDDload_module_name::>cu_name%CU%PROGRAM(,load_module_name::>cu_name%CU%PROGRAM);
load_module_name
The name of the load module containing the specified compile unit (cu_name). If the corresponding load module is known to z/OS Debugger, the specified compile unit must be a disassembly compile unit within the specified load module. If the load module is not known to z/OS Debugger, z/OS Debugger defers the LOADDEBUGDATA command until a load module by the specified name and containing the specified compile unit is loaded. load_module_name is folded to upper case, unless it is enclosed in double-quotation marks or the current environment is UNIX System Services.

If you do not specify load_module_name, z/OS Debugger applies the LOADDEBUGDATA command to all compile units by the specified name found in any load module.

cu_name
The name of the assembler or LangX COBOL compile unit for which the debug data is to be loaded. If the compile unit is not currently known to z/OS Debugger, z/OS Debugger defers the LOADDEBUGDATA command until a compile unit by the specified name becomes known to z/OS Debugger.

Usage notes (assembler and LangX COBOL form of LDD)

  • When you use the SET SAVE command to save breakpoints or monitor specifications or you use the RESTORE command to restore breakpoints or monitor specifications, all LDD settings including the data set name of the data set from which the debug data was loaded is saved and restored.
  • For CICS® only: When a DTCN profile is active for a full screen mode debugging session, z/OS Debugger preserves all LDD settings, including the data set name of the data set from which the debug data was loaded, until the DTCN profile is deleted or the terminal session is terminated.
  • You can use this command for assembler compile units in remote debug mode.
  • After z/OS Debugger successfully processes a LOADDEBUGDATA command for a CU, if the CU is deleted and then appears later, an implicit LDD command is run for the CU using the same EQALANGX data set that was used initially.
  • You cannot enter the LDD command for the same compile unit more than once.
  • A deferred LDD creates an implicit NAMES INCLUDE for the target of the deferred LDD.

Refer to the following topics for more information related to the material discussed in this topic.