DBOC: Controlling Local Resources with Operational Commands › LOG= Resetting the Log Option for Operational Commands

LOG= Resetting the Log Option for Operational Commands

CA Datacom CICS Services provides the capability to write the responses to Operational commands to the Message Log.

The Message Log destination is defined with the MSGLOG= parameter of the DBCVTPR or through the DBOC GENOPTS transaction. For more information, see the System Reference Guide. The default Message Log destination is DBOCPRT, the separate log for DBOC/DBIC messages. If MSGLOG=CSMT is specified, the CA Datacom CICS Services log entries are intermingled with CICS messages.

Logging of Operational commands can be specified for your system in the DBCVTPR macro (see the System Reference Guide). To change this specification for the current CICS session, issue the following transaction.

►►─ DBOC ─ LOG= ─┬─ YES ─┬────────────────────────────────────────────────────►◄
                 └─ NO ──┘

DBOC

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

LOG=

(Required) Specifies to set the logging of Operational commands.

YES

Specifies that responses to Operational commands are written to the Message Log.

NO

Specifies that responses to Operational commands are not written to the Message Log.

Note: If LOG=YES is typed correctly, YES would be in effect. If the LOG=NO or anything other than YES is typed, then LOG=NO is in effect.