Canceling, stopping, and starting EXEC execution


You might decide to manually control the progress of an EXEC after it has been scheduled.

By using the BBI control command .DISPLAY, you can see the progress in the BBI Log display. If you decide to intervene in the EXEC, you can use the following BBI control commands:


BBI control command

Action taken

.CANCEL

Terminates the execution of an EXEC while it is running or if it is waiting for a thread to become available

Error
Warning

The CANCEL command causes an abnormal termination of the TSO/E EXEC command and any other command or program currently running within the EXEC. The abnormal termination might result in resources, such as storage, not being cleaned up. Particularly, if the command or program does not explicitly freemain subpool 0 storage and relies upon task termination to clean up this storage, the storage will not be freemained and an eventual private storage problem might be experienced, such as ABEND878 RC10.

.STOP

Disables an EXEC that is running

This command prevents the EXEC from being scheduled again until it is STARTed by the BBI START command. Does not cancel the current EXEC.

.START

Enables an EXEC that has been stopped with the STOP command and makes it available to be scheduled

This command does not schedule an EXEC.

For more information about the syntax for the BBI control commands, see BBI control commands

You can also control the execution of an EXEC with the EXEC Management application. See Managing-EXECs-by-using-the-EXEC-Management-application

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.4