Previous Topic: Device SupportNext Topic: Issuing a Single Operational Command


Overview of Operational Commands

All operational commands can be issued with a single transaction ID (the default is DBOC). Operational commands that are used for monitoring system resources can be issued with a secondary transaction ID (the default is DBIC). The secondary ID is used to extend the availability of the monitoring function to users who would typically not be authorized for control functions.

Each operational command is logged to the Message Log file with the time of day it was invoked. Included in the log is the request, comments, and response. If the command is issued from a terminal, the terminal ID and Operator ID are logged too. Transactions that are invoked internally or from the PLT (at startup or termination) are identified in the log. The default Message Log destination is DBOCPRT, the CICS message log, where CA Datacom CICS Services log entries are intermingled with CICS messages. In DBCVTPR, you can specify an alternate destination for CA Datacom CICS Services log entries. For details, see the System Reference Guide.