GO command

The GO command causes z/OS® Debugger to start or resume running your program.

Read syntax diagramSkip visual syntax diagramGOBYPASS;
BYPASS
Bypasses the user or system action for the condition that caused the breakpoint. It is valid only when z/OS Debugger is entered for an:
  • AT CALL Breakpoint
  • HLL or Language Environment® condition
  • Condition that is raised by an MVS or CICS® ABEND when running without the Language Environment run time

Usage notes

  • For CICS only: The ABEND is reported whether BYPASS is or is not specified. When there is a HANDLE ABEND, control is passed to the abend handler, and the GO BYPASS command is ignored.
  • If GO is specified in a command list (for example, as the subject of an IF command or WHEN clause), all subsequent commands in the list are ignored.
  • If GO is specified within the body of a loop, it causes the execution of the loop to end.
  • To suppress the logging of GO commands, use the SET ECHO command.
  • GO with no operand specified does not actually resume the program if there are additional AT-conditions that have not yet been processed.
  • The GO command cannot be used while you replay recorded statements by using the PLAYBACK commands by using the PLAYBACK command.
  • You can use the GO command in remote debug mode by entering it in the Debug Console or the Action field, which is in the Optional Parameters section of the Add a Breakpoint task.
  • When a COBOL IGZ condition of severity 2 or higher occurs, GO BYPASS will bypass the condition. When the IGZ condition is raised by a COBOL program (for example the subscript out of range message IGZ0006S), GO BYPASS will bypass the condition and resume control back into the COBOL program. However, be aware that control might not return to the next statement of the program that raised the condition, since the compiler might have rearranged the statements.

Examples

  • Resume execution. 
    GO;
  • Resume execution and bypass user and system actions for the condition that caused the breakpoint. 
    GO BYPASS;
  • Your application has abended with a protection exception, so an OCCURRENCE breakpoint has been triggered. Correct the results of the instruction that caused the exception and issue GO BYPASS; to continue processing as if the abend had not occurred.

Refer to the following topics for more information related to the material discussed in this topic.