Messages OPL300 through OPL3xx

This group includes messages for the Control-O product.

OPL341S OPERLOG NOT AVAILABLE UNDER MVS/ESA 5.2

Explanation: The user tried to access the MVS OPERLOG with a system level lower than MVS/ESA 5.2.

The system rejects the request and continues.

Corrective Action: Update the system to MVS/ESA 5.2 or higher.

OPL342S ERROR OPENING OPERLOG FILE

Explanation: The user tried to access the OPERLOG in a SYSPLEX environment. However, the OPERLOG could not be opened.

The system rejects the request and continues.

Corrective Action: Record the message and contact your system programmer.

OPL346S ABEND abCode INTERCEPTED WHILE PROCESSING THE OPERLOG

Explanation: The user tried to access the OPERLOG in a SYSPLEX environment but an abend was generated.

For information about abCode, see the IBM Abend Codes manual.

The system terminates the requested action.

Corrective Action: Take appropriate corrective action.

OPL347S ERROR RETURN CODE FROM A SYSTEM LOGGER REQUEST rc

Explanation: The user issued the OPER command in the OL screen to access the OPERLOG in a SYSPLEX environment. However, the request failed and the rc SYSTEM LOGGER return code was issued.

The system rejects the request.

Corrective Action: For information about the error, note the value of rc and refer to IBM LOGGER services (IXGxxx macros) in the Sysplex service manual.

OPL348S OPERLOG IS EMPTY

Explanation: The user issued the command OPER in the OL screen to access the OPERLOG in a SYSPLEX environment. In response, the system logger informed Control-O that the OPERLOG was empty.

The system rejects the request.

Corrective Action: For more information about the error, note the message and contact your system programmer.

OPL349S OPERLOG END OF FILE IS REACHED

Explanation: The user attempted to access the OPERLOG in a SYSPLEX environment and reached the end of the OPERLOG. However, no more data was available in the OPERLOG.

The system rejects the request.

Corrective Action: Reattempt access to the OPERLOG.