Defining a compilation unit as LangX COBOL and loading debug information

Before you can debug a LangX COBOL program, you must define the compilation unit (CU) as a LangX COBOL CU and load the debug data for the CU. This can only be done for a CU that is currently known to z/OS® Debugger as a disassembly CU or for a CU that is not currently known to z/OS Debugger.

You use the LOADDEBUGDATA command (abbreviated as LDD) to define a disassembly CU as a LangX COBOL CU and to cause the debug data for this CU to be loaded. When you invoke the LDD command, you can specify either a single CU name or a list of CU names enclosed in parenthesis. Each of the names specified must be either:

  • the name of a disassembly CU that is currently known to z/OS Debugger
  • a name that does not match the name of a CU currently known to z/OS Debugger

When the CU name is currently known to z/OS Debugger, the CU is immediately marked as a LangX COBOL CU and an attempt is made to load the debug as follows:

  • If your debug data is in a partitioned data set where the high-level qualifier is the current user ID, the low-level qualifier is EQALANGX, and the member name is the same as the name of the CU that you want to debug no other action is necessary
  • If your debug data is in a different partitioned data set than userid.EQALANGX but the member name is the same as the name of the CU that you want to debug, enter the following command before or after you enter the LDD command: SET DEFAULT LISTINGS
  • If your debug data is in a sequential data set or is a member of a partitioned data set but the member name is different from the CU name, enter the following command before or after the LDD command: SET SOURCE

When the CU name specified on the LDD command is not currently known to z/OS Debugger, a message is issued and the LDD command is deferred until a CU by that name becomes known (appears). At that time, the CU is automatically created as a LangX COBOL CU and an attempt is made to load the debug data using the default data set name or the current SET DEFAULT LISTINGS specification.

After you have entered an LDD command for a CU, you cannot view the CU as a disassembly CU.

If z/OS Debugger cannot find the associated debug data after you have entered an LDD command, the CU is a LangX COBOL CU rather than a disassembly CU. You cannot enter another LDD command for this CU. However, you can enter a SET DEFAULT LISTING command or a SET SOURCE command to cause the associated debug data to be loaded from a different data set.