Chapter 14. Some useful Debug Tool commands 317
14.2 Descriptions of some interesting commands
This section covers some more commands you may find useful.
SET AUTOMONITOR (COBOL and PL/I)
Automonitor support displays the variables referenced in the current statement. To do this,
you must enable automonitoring with the following command:
SET AUTOMONITOR ON ;
Please refer to Debug Tool for z/OS Reference and Messages, SC18-9010 for more
information on specific supporting compilers and required PTFs.
GOTO
The GOTO command instructs Debug Tool to start or resume running your program at the
specified statement, or you can position the cursor at a specific statement and use a PF key
defined as GOTO.
RUNTO
The RUNTO command instructs Debug Tool to run your program to the statement you define
in the command, without setting a breakpoint, or you can position the cursor at a specific
statement and use a PF key defined as RUNTO.
GO BYPASS
The GO BYPASS command instructs Debug Tool to resume running your program after a
condition occurred, hereby ignoring the condition.
PLAYBACK (COBOL)
Playback support allows you to replay and review the application paths and data values
starting at the point where you begin recording. You can simulate the backward execution of
the application and review application data values using appropriate Debug Tool commands.
To do this you must enable playback, using the following Debug Tool command:
PLAYBACK ENABLE ;
This command starts playback recording. To replay the statements starting at the current
statement enter PLAYBACK START ; To move backward one statement, enter STEP ; (or
PF2) To change the replay direction, enter PLAYBACK FORWARD; PLAYBACK BACKWARD ;
STEP will move in the direction last set.
To return to the point where you started playback (using PLAYBACK START) enter PLAYBACK
STOP ; to stop recording enter PLAYBACK DISABLE ;
14.3 Finishing a Debug Tool session
There are several ways to finish the Debug Tool, but this command needs to be discussed
because of the behavior related to databases.
As of today, there is no command to stop the Debug Tool, while your program continues to
run in non-debug mode.
318 Using IBM Application Development Tools for z/OS and OS/390
QUIT
Soft termination of your program occurs at the current statement, with a prompt message.
QQUIT
Soft termination of your program occurs at the current statement, with no prompt message.
QUIT ABEND
Your program will be abended (ABENDU4038) at the current statement, with a prompt
message.
You can associate QUIT ABEND with the PF3 key using following command:
SET PF3 ‘ABEND’ = QUIT ABEND;
QUIT DEBUG
The debugger will be terminated, but your program will continue to run to completion.
Note: By using QUIT ABEND, any non-committed database updates will be rolled back.
We suggest you use this as the default for your PF3.
Note: This PF key setting will be saved to your INSPSAFE, if one was allocated. CICS
does not support INSPSAFE, therefore you should put this command in your INSPPREF
when running under CICS.

Get Using IBM Application Development Tools for z/OS and OS/390 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.