OptiConnect error messages

OptiConnect provides messages that are kept in the QCPFMSG message file in QSYS library. You can display and print these messages by using the Work with Message File (WRKMSGF) command as follows:

WRKMSGF MSGF(QCPFMSG)

Or, you can use:

WRKMSGD CPDADA1

Detailed information can be displayed by selecting option 5 (Display details). You can also print from this display by using option 6 (Print).

When you are using OptiConnect, you may also see system messages that can be displayed as described above. These messages are also in the QCPFMSG message file in the QSYS library.

The list below describes the major/minor codes for message CPDADA0. There are two pieces of information in the MSGCPDADA0 secondary text. The first is the 'yyxx'X data. This information includes an error code followed by a function code. The second, which the message identifies as a major/minor return code, is a code point that identifies (to the OptiConnect developer) where the operation failed.

The MSGCPDADA0 msg 'yyxx'X data in the second level text can be interpreted as follows:

• yy = Error Code (what failure was detected)
• xx = Function Code (what function was being run)

Error Codes:

• 01xx - Coupling Environment not open (for example, QSOC SBS and SOCMGR not up).
• 02xx - System name not found (results in CPF9162 - cannot establish DDM connection with remote system).
• 03xx - Source/Agent connection id invalid (for example, source or target job ended the OptiConnect conversation without a clean disconnect).
• 0403 - Source/target conversation startup error. This is typically due to timeout, but can happen due to other errors during startup.
• 05xx - Bad conversation state. Received the wrong message type when waiting for a request, response, or control message (for example, waiting for a request and received a control message or any other combination of request/response/control). Typically this happens when a "Close-Path" (conversation) is received due to unexpected error on the other job (look at target joblog if 05xx on source and vice versa).
• 06xx - Communication error - error from IPCF/transport layer. In a dual bus setup this typically means the operation could not be done on either adapter. Most operations will be automatically retried on the alternate connection if available. Errors returned from HMC I/O typically cause this error.
• 07xx - Transaction ended, this error is almost always 070B: Terminate waiting for response. Indicates an inflight request was ended without any response. This typically means the associated target (or source) job failed and ended OptiConnect conversation without sending a response. However, this can also occur if communication between source and target systems was lost while a request was outstanding. The 06xx error occurs only if the communication is lost during request/response transport, while 07xx results because of failure during wait for response.
• 90xx - Internal Error. An unexpected or unhandled condition was detected by the OptiConnect device driver. A VLIC log with major or minor of 0700/0DDD is logged when this occurs. This may indicate a code problem or incorrect data (900B has been due to bad data in messages that are sent over the bus).
  Note:
  There are also some known cases in the device driver where this error is due to loss of communication during certain states. That is, errors which should probably be 06xx sometimes show up as 90xx. A 90xx error, which happens at the same time as a SOCnnnnnn OptiConnect connection closed message, is probably one which should have been 06xx.

Function Codes which may appear in MSGCPDADA0:

• yy01 - Open-stream (connects job with OptiConnect device driver, should only fail if Coupling Environment not open = 0101)
• yy03 - Open-conversation (namely, Open-path; connects source and agent job through SOCMGR on the target system)
• yy05 - Close-conversation (namely, Close-path; disconnects source and agent job)
• yy07 - Send-request (send a request message; requests may be originated by either source or agent job)
• yy08 - Receive-request (receive a request message)
• yy0A - Send-response (send a response message; associated with a previous request message)
• yy0B - Receive-response