Debugging VS COBOL II programs

There are limitations to debugging VS COBOL II programs compiled with the TEST compiler option and linked with the Language Environment® library. Language Environment callable services, including CEETEST, are not available. However, you must use the Language Environment run time.

z/OS® Debugger does not get control of the program at breakpoints that you set by the following commands:

• AT PATH
• AT CALL
• AT ENTRY
• AT EXIT
• AT LABEL

However, if you set the breakpoint with an AT CALL command that calls a non-VS COBOL II program, z/OS Debugger does get control of the program. Use the AT ENTRY *, AT EXIT *, AT GLOBAL ENTRY, and AT GLOBAL EXIT commands to set breakpoints that z/OS Debugger can use to get control of the program.

Breakpoints that you set at entry points and exit statements have no statement associated with them. Therefore, they are triggered only at the compile unit level. When they are triggered, the current view of the listing moves to the top and no statement is highlighted. Breakpoints that you set at entry points and exit statements are ignored by the STEP command.

If you are debugging your VS COBOL II program in remote debug mode, use the same TEST run-time options as for any COBOL program.