105 lines
6.1 KiB
HTML
105 lines
6.1 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-10-17" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow"/>
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<title>OptiConnect error messages</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="msgs"></a>
|
||
|
|
<h2 id="msgs">OptiConnect error messages</h2>
|
||
|
|
<p>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: </p>
|
||
|
|
<pre class="xmp">WRKMSGF MSGF(QCPFMSG)</pre><p class="indatacontent"> Or, you can use:</p>
|
||
|
|
<pre class="xmp">WRKMSGD CPDADA1</pre>
|
||
|
|
<p>Detailed information can be displayed by selecting option 5 (Display details).
|
||
|
|
You can also print from this display by using option 6 (Print).</p>
|
||
|
|
<p>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.</p>
|
||
|
|
<p>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.</p>
|
||
|
|
<p>The MSGCPDADA0 msg 'yyxx'X data in the second level text can be interpreted
|
||
|
|
as follows:</p>
|
||
|
|
<ul>
|
||
|
|
<li>yy = Error Code (what failure was detected)</li>
|
||
|
|
<li>xx = Function Code (what function was being run)</li></ul>
|
||
|
|
<p>Error Codes:</p>
|
||
|
|
<ul>
|
||
|
|
<li>01xx - Coupling Environment not open (for example, QSOC SBS and SOCMGR
|
||
|
|
not up).</li>
|
||
|
|
<li>02xx - System name not found (results in CPF9162 - cannot establish DDM
|
||
|
|
connection with remote system).</li>
|
||
|
|
<li>03xx - Source/Agent connection id invalid (for example, source or target
|
||
|
|
job ended the OptiConnect conversation without a clean disconnect).</li>
|
||
|
|
<li>0403 - Source/target conversation startup error. This is typically due
|
||
|
|
to timeout, but can happen due to other errors during startup.</li>
|
||
|
|
<li>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).</li>
|
||
|
|
<li>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.</li>
|
||
|
|
<li>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.</li>
|
||
|
|
<li>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).
|
||
|
|
<a name="wq61"></a>
|
||
|
|
<div class="notetitle" id="wq61">Note:</div>
|
||
|
|
<div class="notebody">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 SOC<span class="italic">nnnnnn</span> OptiConnect
|
||
|
|
connection closed message, is probably one which should have been 06xx.</div></li></ul>
|
||
|
|
<p>Function Codes which may appear in MSGCPDADA0:</p>
|
||
|
|
<ul>
|
||
|
|
<li>yy01 - Open-stream (connects job with OptiConnect device driver, should
|
||
|
|
only fail if Coupling Environment not open = 0101)</li>
|
||
|
|
<li>yy03 - Open-conversation (namely, Open-path; connects source and agent
|
||
|
|
job through SOCMGR on the target system)</li>
|
||
|
|
<li>yy05 - Close-conversation (namely, Close-path; disconnects source and
|
||
|
|
agent job)</li>
|
||
|
|
<li>yy07 - Send-request (send a request message; requests may be originated
|
||
|
|
by either source or agent job)</li>
|
||
|
|
<li>yy08 - Receive-request (receive a request message)</li>
|
||
|
|
<li>yy0A - Send-response (send a response message; associated with a previous
|
||
|
|
request message)</li>
|
||
|
|
<li>yy0B - Receive-response</li></ul>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|