Previous Topic: Display Example: DBOC CLOSE=??Next Topic: Display Example: DBOC DEBUG=LIST

DBOC: Controlling Local Resources with Operational Commands › DEBUG= Controlling the DBUG Environment

DEBUG= Controlling the DBUG Environment

The DEBUG= transaction allows you to have more control over the DBUG environment.

You can use the following transactions to list or release any or all terminals currently under DBUG control.

►►─ DBOC ─ DEBUG= ─┬─ LIST ─────────────┬─────────────────────────────────────►◄
                   └─ KILL ─┬─────────┬─┘
                            └─ =xxxx ─┘
DBOC

(Required) Specify the transaction ID used with Operational commands to control system resources. Leave a space between the transaction ID and the command.

DEBUG=

(Required) Specifies the DEBUG function invoked.

LIST

Provides a list showing all terminals currently under DBUG control. The list is in the form:

DEBUG ON TERMINAL "xxxx" DISPLAY ON "yyyy"

The xxxx identifies a terminal under DBUG control (the intercepted terminal) and yyyy identifies the terminal that initiated that control (the initiating terminal).

Note: You must be a master operator to use KILL (described following). One or more master operators can be defined through the MSTOPR= parameter in the DBCVTPR macro. If no master operators are specified, all users are eligible to invoke master operator-type functions. Specifications for master operators can be altered for the current CICS session through the screen displayed when you issue the DBOC GENOPTS command. For more information, see the System Reference Guide.

KILL

Removes DBUG from the system, meaning that it releases DBUG control from all terminals currently in intercept mode.

=xxxx

(Optional) KILL=xxxx removes DBUG control from a specific intercepted terminal (not an initiating terminal). You can invoke DBOC DEBUG=LIST first to determine the terminal IDs. To cancel monitor mode, specify KILL=****.

For monitor mode or remote mode DBUG: If the terminal that initiated the DBUG is in "lost session" status and DBUG is active at an intercepted terminal, perform the following steps to free the intercepted terminal:

  1. Use DBOC DEBUG=KILL=xxxx to terminate the DBUG session on the intercepted terminal, where xxxx is the intercepted terminal ID.
  2. You can use CEMT to purge the task which is active at the intercepted terminal.