Debugging a Language Environment COBOL program that calls non-Language Environment subprograms
SVC screening is required when the first program is Language Environment enabled and non-Language Environment subprograms are called. SVC screening is used only for assembler subprograms in non-CICS environments.
- In ISPF Edit or Browse, enter EQAJCL G2 to invoke IBM z/OS Debugger JCL
Wizard, and request a debug session with the
remote debugger. Alternatively, you can enter EQAJCL and then select
G2.In this use case, the Language Environment COBOL program ASAMDRV will call the non-Language Environment assembler program ASAM1.
- In the parameters panel, type YES in the LE Program field.
To select an optional parameter, specify a forward slash (/) in the field.
The assembler subprogram requires debug libraries, LDD programs and AT ENTRY breakpoints. Because the subprogram is a non-Language Environment one invoked from a Language Environment program, SVC screening is also required. Specify a forward slash (/) in the corresponding fields.
- Since you chose Debugger Libs, the z/OS Debugger Debug
Libraries panel is displayed. In this panel, enter the library where the debugger source
information is found.
- Since you chose to set AT ENTRY breakpoints for subprograms, the Request AT ENTRY
Sub-Program Breakpoints panel is displayed. In this panel, enter the name of the
subprogram that you want to debug.
- In the Program/Procedure Selection List panel, select the step to
debug.
- Since you chose LDD Programs, the z/OS Debugger LDD Generation
for Non-LE Program Name panel is displayed. This panel is pre-populated with the initial
program and the programs specified in the Request AT ENTRY Sub-Program
Breakpoints panel. Load Data Descriptor (LDD) commands are generated from this panel.
- JCL statements are generated to invoke z/OS Debugger.