Displaying variables
in the Monitor window
- SET AUTOMONITOR ON
- Automatically displays the values of variables referenced by
the current statement in the Monitor window.
- SET AUTOMONITOR ON BOTH
- Automatically displays the values of variables referenced by
both the current statement and the previously run statement in the
Monitor window.
- MONITOR LIST ITEMNO
- Adds the ITEMNO variable and its value to the Monitor window.
- SET MONITOR DATATYPE ON
- Display the data types of variables.
- SET MON WRAP OFF
- Displays values on a single line. If the value is longer than
the visible area, Debug Tool displays a scale to indicate that there is
more to see.
- CLEAR MONITOR
- Clears all items from the Monitor window.
- C
- C is the abbreviation for the CLEAR MONITOR command.
Type in the letter C in the prefix area of the monitor window. When
you press Enter, Debug Tool removes the variable on the line where C is
in the prefix area.
Changing values of variables
- Type over value displayed in the Monitor window
- Move cursor to value displayed in Monitor window, type in new
value, then press Enter.
- MOVE 24 to ACCUM-X
- For COBOL programs, replace the value of ACCUM-X with 24.
- ACCUMX = 24
- For some languages, replaces the value of ACCUMX with 24.
|
Displaying variables
in Log window and controlling Log window options
- LIST CUST-ID or LIST TITLED CUST-ID
- Displays the value of a variable. Only some programming languages
require TITLED.
- PF4 or LIST
- Displays the value of a variable identified by the location
of the cursor.
- LIST TITLED WSS or LS or FS or LOS
- Display contents of specific SECTIONS for COBOL programs. WSS
means Working-Storage Section, LS means Linkage Section, FS
means File Section, and LOS means Local-Storage Section.
- LIST TITLED *
- Displays the values of all variables.
- SET ECHO OFF
- Debug Tool does not display STEP and GO commands
in the Log window. However, if a log file is open, Debug Tool writes them
to the log file.
- SET LOG ON FILE file_name OLD
- Opens a log file. When Debug Tool opens the log file, all items
it writes to the Log window are also written to the log file.
Refresh the Source window to display the current statement
- QUALIFY RESET
- Repositions source in the Source window so that Debug Tool displays
the current program and current statement.
Working with called programs
- STEP or STEP INTO
- When the current statement is a CALL, steps into the called
program.
- STEP OVER
- When the current statement is a CALL, Debug Tool runs the called
program but does not display it. Debug Tool stops at the statement after
the call.
- LOAD program_name
- Make program_name known to Debug Tool.
- QUALIFY program_name
- Displays the program program_name in the Source window.
When the program is displayed in the Source window, you can set a
breakpoint or work with variables in that program.
- QUALIFY RESET
- Reposition to the current program and the current line.
|
Controlling program
execution
- STEP or PF2
- Run one statement or line.
- GO or PF9
- Run the program until Debug Tool encounters a breakpoint, the program
finishes, or an abend occurs.
- RUNTO 27
- Runs the program and then stops before it runs line 27.
- R
- R is the abbreviation of RUNTO. Type in the command in the prefix
area of the Source window. When you press Enter, Debug Tool runs the program
until it reaches the line with the R in the prefix area.
- GO BYPASS
- Resume running a program after encountering an abend. Enter
this command immediately after an abend occurs. Debug Tool skips the statement
that caused the abend and continues running the program from the next
logical statement.
Skipping (do not run) over program statements
- JUMPTO 27
- Moves the point at which the program resumes execution to line
27, does not run any statements between the current point and line
27, and then pauses at line 27. When you enter a GO or STEP command,
the program resumes running at line 27.
- GOTO 27
- Moves the point at which the program resumes execution to line
27, does not run any statements between the current point and line
27, and then resumes running the program at line 27.
|