Debugging PL/I when only a few parts are compiled with TEST

Suppose you want to set a breakpoint at entry to subroutine PUSH. PUSH has been compiled with TEST, but the other files have not. z/OS® Debugger comes up with an empty Source window. To display the compile units, enter the command:

LIST NAMES CUS

The LIST NAMES CUS command displays a list of all the compile units that are known to z/OS Debugger. If PUSH is fetched later on by the application, this compile unit might not be known to z/OS Debugger. If it is displayed, enter:

SET QUALIFY CU PUSH
AT ENTRY PUSH;
GO ;

If it is not displayed, set an appearance breakpoint as follows:

AT APPEARANCE PUSH ;
GO ;

You can also combine the breakpoints as follows:

AT APPEARANCE PUSH AT ENTRY PUSH; GO;

The only purpose for this appearance breakpoint is to gain control the first time a function in the PUSH compile unit is run. When that happens, you can set a breakpoint at entry to PUSH like this:

AT ENTRY PUSH;