Use the following procedure to issue an operational command from a terminal. (Some operational commands can also be invoked from an application program. See the System Reference Guide.)
Operational Command Syntax
►►─ transaction-ID ─ command ─────────────────────────────────────────────────►◄
Transaction ID, defined in the CICS System Definition data set (CSD), for invoking CA Datacom CICS Services functions to monitor and control resources in a non-MRO environment. Default transaction IDs follow:
Precedes an operational command to perform an action or make an inquiry.
Precedes an operational command to make an inquiry.
Note: To substitute other transaction IDs for DBOC or DBIC, see the System Reference Guide information about coding the DBOC= parameter in the System Options Table (DBCVTPR) or overriding the specified DBOC= value from the DBOC GENOPTS display.
Operational commands take one of the following forms:
Keywords for operational commands to perform an action follow. For more information, see DBOC: Controlling Resources with Operational Commands.
|
AUTO= |
DISABLE= |
RESET= |
|
AUX= |
DUMP= |
RESTART= |
|
CLOSE= |
ENABLE= |
SHUTDOWN |
|
DEBUG= |
LOAD= |
STARTUP |
|
DEFER= |
LOG= |
TRACEOFF |
|
DELETE= |
OPEN= |
TRACEON |
|
DELIM= |
PREFIX= |
TRACE[,DELETE],keyword= |
Keywords for operational commands to invoke a formatted display follow. For details, see DBOC/DBIC: Monitoring Resources with Operational Commands.
|
TASK |
INQ= |
INQ=TRACE,TERMID= |
|
TRACE |
TASK= |
INQ=TRACE,TRANSID= |
Example
DBIC INQ=OPENED
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|