The DEBUG command initiates the debugging of a program. When the DEBUG command is issued, an Initialization breakpoint appears on the screen that lets you specify (or alter) Debug commands. When a breakpoint is encountered, application processing stops, any commands attached to the breakpoint are executed, and the Debug screen displays at the terminal. When the Debug screen is transmitted, a checkpoint is issued that commits records marked for update. The SET RUN UPDATE NO command stops the application from updating the database. For more information on breakpoints, see the Programming Reference Guide. For more information about using the symbolic debugger, see the Creating Programs Guide.
Online: If no member name is specified, member DEBUG is used. If member DEBUG already exists, the contents of the member are saved.
Batch: Follow the DEBUG command with debug commands for the session and end with a GO command. When the GO command is encountered, execution of the program begins. When a breakpoint is encountered, any attached commands execute and application processing resumes. Output is written to the Debug print file. If no member name is specified, a member unique to this run is used.
Both online and batch: If a member name is specified, it is created if it does not already exist. If this member already exists, the contents of the member are saved.
Issuing the DEBUG command alone invokes the DEBUG prompter. DEBUG * debugs the current program.
This command has the following format:
DEBUG { * }
{pgm‑name [VERSION version]}
{Y}
[UPDATE [DB] {N} ]
[PARAMETER 'string' ]
[ ]
[ {MAIL 'email‑id' }]
[ {LIB }]
[DESTINATION {{SYS name} }]
[ {{NET name} [COPIES num]}]
[ ]
[ {KEEP } ]
[DISPOSITION {RELEASE} ]
[ {HOLD } ]
[ ]
[MAXLINES n ]
[ ]
[DESCRIPTION 'string' ]
[ ]
[COMMANDS [{* }] ]
[ [{member [USER uuu]}] ]
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|