Messages ALO200 through ALO2xx

This group includes messages for the Control-O CMEM product.

ALO290I {CONTROL-O | CTMCMEM} AUTOMATION LOG STARTED

Explanation: This information message indicates that the Automation Log subtask began.

Corrective Action: No action is required.

ALO291E AUTOMATION LOG ERROR WHILE PROCESSING REQUESTS

Explanation: The Automation Log subtask detected an error while processing requests.

The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.

Corrective Action: Contact your INCONTROL administrator.

ALO292S {CONTROL-O | CTMCMEM} AUTOMATION LOG TERMINATION ERROR

Explanation: The Automation Log subtask terminated after an error was detected.

The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.

Corrective Action: Contact your INCONTROL administrator.

ALO293I CONTROL-O AUTOMATION LOG ENDED

Explanation: This information message indicates that the Automation Log subtask terminated successfully.

The subtask and the monitor shut down.

Corrective Action: No action is required.

ALO294E OPEN OF AUTOMATION LOG FAILED. LOG SWAPPED

Explanation: The Automation Log subtask attempted to open the Automation Log file but failed.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Do the following:

• Check the CTOPARM member in the Control-O installation library.
• Check to see if the Automation Log file exists for this CPU.

ALO295S OPEN OF DAACTLOG FAILED

Explanation: The Automation Log subtask failed to open the file referenced by the DAACTLOG DD statement.

The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.

Corrective Action: Check the JCL of your Control-O or CMEM starting procedure to verify that the DD statement DAACTLOG exists. If the problem is not resolved, contact your INCONTROL administrator.

ALO296E ERROR DETECTED DURING ADDF. LOG SWAPPED

Explanation: The Automation Log subtask was unable to write to the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

ALO297I AUTOMATION LOG STATUS CHANGE COMPLETED

Explanation: This information message indicates that the Automation Log subtask completed the change of Automation Log status.

This message is displayed in response to the operator command F CONTROLO,AUTOLOG=YES/NO.

The Automation Log subtask writes to the new destination.

Corrective Action: No action is required.

ALO298E ERROR DETECTED DURING ENQ. LOG SWAPPED

Explanation: The Automation Log subtask detected an error while trying to ENQUEUE the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

ALO299E ERROR DETECTED DURING DEQ. LOG SWAPPED

Explanation: The Automation Log subtask detected an error while trying to dequeue the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.