611 lines
27 KiB
HTML
611 lines
27 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-03" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 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>APPN session setup states</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="ssstup"></a>
|
||
|
|
<h4 id="ssstup">APPN session setup states</h4>
|
||
|
|
<p>The following table presents the possible session setup states for APPN
|
||
|
|
while it processes a session initiation request. One of these values always
|
||
|
|
resides in the current session setup state.</p><img src="delta.gif" alt="Start of change" />
|
||
|
|
<a name="sescode"></a>
|
||
|
|
<table id="sescode" width="100%" summary="" border="1" frame="hsides" rules="rows">
|
||
|
|
<caption>Table 4. APPN Session Setup States</caption>
|
||
|
|
<thead valign="bottom">
|
||
|
|
<tr>
|
||
|
|
<th id="wq104" width="11%" align="left" valign="bottom"><span class="bold">State</span></th>
|
||
|
|
<th id="wq105" width="88%" align="left" valign="bottom"><span class="bold">Reason</span></th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody valign="top">
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup complete. An existing session
|
||
|
|
will be used; therefore, APPN control point functions will not be called.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1015</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup request has failed. Refer to
|
||
|
|
sense code for details.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1020</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup rejected. The local location
|
||
|
|
name chosen is not defined in either the network attributes or as a local
|
||
|
|
location list entry.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1025</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup rejected. Mode name specified
|
||
|
|
is not defined on the system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup request has been sent by location
|
||
|
|
manager to resource manager to obtain a device.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1032</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup request cannot be satisfied
|
||
|
|
with a non-APPN device or with an existing APPN session. The APPN control
|
||
|
|
point has been called to establish a new session.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1035</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup has been pended because of
|
||
|
|
a previous request that is waiting for the request transmission group vectors
|
||
|
|
processing to complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup has been pended because of
|
||
|
|
a previous request that is still waiting for the route selection phase (request
|
||
|
|
single hop route - end node) to complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup has been pended because of
|
||
|
|
a previous request that is still waiting for the route selection phase (request
|
||
|
|
route - network node) to complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1060</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup has been pended because of
|
||
|
|
a previous request that is still waiting for the switched link activation
|
||
|
|
phase to complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1070</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup has been pended because of
|
||
|
|
a previous request that is still waiting for the location search phase to
|
||
|
|
complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1080</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request transmission group vectors request
|
||
|
|
is outstanding to topology routing services component.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1082</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request transmission group vectors request
|
||
|
|
is being processed by topology routing services component.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1084</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request transmission group vectors response
|
||
|
|
was returned by the topology routing services component.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1086</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request transmission group vectors request
|
||
|
|
has been received by session services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">1090</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase request is outstanding,
|
||
|
|
but has not yet been received by the local system's directory services function.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">End Node Location Search Phase (2000 - 2999) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The local system's directory services has
|
||
|
|
received the search request and has begun its processing.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2010</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">There is a one hop search request outstanding
|
||
|
|
to the local system's network node server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2020</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search processing has been completed
|
||
|
|
by the local system's directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2025</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session services has received the locate
|
||
|
|
message response from directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase has failed. The owning
|
||
|
|
control point for the remote location can not be determined during the search
|
||
|
|
phase. In this case, the search was forwarded to our network node server and
|
||
|
|
the location can not be found.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase has failed. The owning
|
||
|
|
control point for the remote location can not be determined during the search
|
||
|
|
phase. In this case, the search was not sent out of the local system because
|
||
|
|
of no network node server, and there was no network node that the local system
|
||
|
|
can forward the bind to.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase has failed. The network
|
||
|
|
node server has sent an SNA negative response indicating that the route selection
|
||
|
|
control vector (RSCV) required is larger than 255 bytes.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2060</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase has failed. The network
|
||
|
|
node server has sent an SNA negative response indicating that the class-of-service
|
||
|
|
is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">2070</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Location search phase has failed. The network
|
||
|
|
node server has sent an SNA negative response indicating a route-not-available
|
||
|
|
condition.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">Network Node Location Search Phase (3000 - 3999) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The local system's directory services has
|
||
|
|
received the search request and has begun its processing.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3010</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Query control-point name outstanding. A request
|
||
|
|
to determine if the remote location is the name of a network node control
|
||
|
|
point in the topology database is outstanding.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3012</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Query control-point name request is being
|
||
|
|
processed by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3014</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Query control-point name response has been
|
||
|
|
sent by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3016</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Query control-point name response has been
|
||
|
|
received by directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3020</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">One hop search request is outstanding to
|
||
|
|
an attached end node.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request for a route is outstanding to topology
|
||
|
|
routing services so that a directed search can be sent to another network
|
||
|
|
node.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3032</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route for directed search is being
|
||
|
|
processed by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3034</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for directed search
|
||
|
|
has been sent by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3036</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for directed search
|
||
|
|
received by directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A directed search request is outstanding
|
||
|
|
to another network node.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request for a route is outstanding to topology
|
||
|
|
routing services for a remote search.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3052</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route for a remote search is being
|
||
|
|
processed by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3054</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for a remote search
|
||
|
|
has been sent by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3056</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for a remote search
|
||
|
|
was received by directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3060</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A routed search request is outstanding to
|
||
|
|
a network node.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3070</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A domain broadcast is currently being run.
|
||
|
|
This involves querying attached end nodes or network nodes in another network
|
||
|
|
to determine if the location is known by that system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3080</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A broadcast search is outstanding to one
|
||
|
|
or more directly attached network nodes (this might involve attached network
|
||
|
|
nodes that have access to multiple networks).</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3090™</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request for a route is outstanding to topology
|
||
|
|
routing services to determine if a node that can access multiple networks
|
||
|
|
exists so that it can determine where the remote location exists.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3092</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route for a node that can access
|
||
|
|
multiple networks is being processed by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3094</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for a node that can
|
||
|
|
access multiple networks has been sent by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3096</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Request route response for a node that can
|
||
|
|
access multiple networks was received by directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3100</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A search request is outstanding to a node
|
||
|
|
that can access multiple networks.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3110</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request is outstanding to the session services
|
||
|
|
component in order to perform functions necessary to send searches into a
|
||
|
|
different APPN network.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3120</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The location search phase has completed and
|
||
|
|
a response has been returned by directory services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3125</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The location search phase has completed and
|
||
|
|
the response has been received by session services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">3130</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The location search phase has failed.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">Route Selection Phase (4000 - 4999) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request for a single hop route is outstanding
|
||
|
|
to the topology routing services component.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4002</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a single hop route is being
|
||
|
|
processed by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4004</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request single hop route response has
|
||
|
|
been returned by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4006</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request single hop route response has
|
||
|
|
been received by session services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4010</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request single hop route failure has occurred.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request for a route is outstanding to the
|
||
|
|
topology routing services component.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4032</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route is being processed
|
||
|
|
by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4034</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request route response has been returned
|
||
|
|
by topology routing services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4036</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request route response has been received
|
||
|
|
by session services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. The
|
||
|
|
class-of-service name being used is not defined on the local system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. The route
|
||
|
|
selection control vector required to satisfy the end-to-end route is larger
|
||
|
|
than the architected limit (255 bytes).</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4060</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. Route-not-available
|
||
|
|
condition has been detected. No destination network nodes or virtual nodes
|
||
|
|
are available for intermediate routing.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4062</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. Route-not-available
|
||
|
|
condition has been detected. A route that satisfies the user class-of-service
|
||
|
|
but which uses inactive transmission groups does exist.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4064</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. Route-not-available
|
||
|
|
condition has been detected. A route that has active transmission groups but
|
||
|
|
which does not meet the class-of-service requirements does exist.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4066</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. Route-not-available
|
||
|
|
condition has been detected. A route that has active transmission groups but
|
||
|
|
which does not meet the class-of-service requirements does exist. A route
|
||
|
|
that satisfies the user class-of-service but which uses inactive transmission
|
||
|
|
groups also exists.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4068</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request for a route has failed. Route-not-available
|
||
|
|
condition has been detected. Destination intermediate routing nodes exist,
|
||
|
|
but no route of any type can be calculated.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">4080</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session setup failure. The controller description
|
||
|
|
that represents the first hop of the route is unknown by the local system.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">Switched Link Activation Phase (5000 - 5199) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
is currently outstanding from session services.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5005</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Configuration services has begun processing
|
||
|
|
the activate route request but has not yet completed its processing.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5010</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The activate route has completed, but some
|
||
|
|
failure has occurred. Details are based on sense code.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5020</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. A controller description is being created or varied on for
|
||
|
|
establishing a link using the connection network.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. The controller is not allowed to make a connection in this
|
||
|
|
state. The probable cause is a message outstanding for this controller description.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. Configuration services is waiting for the operating system
|
||
|
|
to issue the command to activate the switched connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. The attempt to select an eligible line description for this
|
||
|
|
request has failed. The probable cause is a message that is outstanding requiring
|
||
|
|
operator intervention.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5070</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. The system is currently in the process of establishing an
|
||
|
|
outgoing connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5080</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. The outgoing connection has been made, but the exchange identification
|
||
|
|
phase is in progress.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5090</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to activate the switched link
|
||
|
|
has been pended. The outgoing connection or exchange identification phase
|
||
|
|
has failed. The system is waiting for the operator to respond to a message.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5100</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The switched link activation has completed
|
||
|
|
successfully.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5110</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The session services component has received
|
||
|
|
its response to its switched link activation request.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">Non-Switched Link Activation Phase (5200 - 5299) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5200</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Session services is waiting for configuration
|
||
|
|
services to complete the non-switched link activation.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5210</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The non-switched link activation phase has
|
||
|
|
completed successfully.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">HPR Route Setup Phase (5300 - 5399) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5300</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request to determine whether a session
|
||
|
|
should be carried over an RTP connection is outstanding.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5310</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to determine if an RTP connection
|
||
|
|
should be used for the session has detected an error.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5315</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">An HPR Route Setup request is outstanding.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5320</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The HPR Route Setup request was returned
|
||
|
|
with a good completion.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5325</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The HPR Route Setup request has failed.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5330</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The HPR Route Setup phase has completed successfully.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">APPN Virtual Controller Selection Phase (5400 - 5499) States</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5400</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request is outstanding to the virtual
|
||
|
|
controller manager component to find the APPN virtual controller description.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5490</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to find the APPN virtual controller
|
||
|
|
description has failed.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">5495</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The request to find the APPN virtual controller
|
||
|
|
description has completed successfully.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td colspan="2" align="center" valign="top" headers="wq104 wq105"><span class="bold">Device Selection Phase (6000 - 6999)</span></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6000</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">A request is outstanding to the T2 station
|
||
|
|
input/output manager (IOM) task to select a device.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6005</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The T2 station input/output manager (IOM)
|
||
|
|
task has begun processing the get device request.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6010</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Device selection pended. The device was found,
|
||
|
|
but it is in the process of being automatically varied on.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6020</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Device selection pended. No device was found;
|
||
|
|
therefore, a new device is in the process of being created and varied on.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6025</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">Device selection request pended. A dynamic
|
||
|
|
device creation or vary on is already in progress for a previous get device
|
||
|
|
request or for a received bind request.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6030</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The device selection has failed. Refer to
|
||
|
|
the sense data returned for an explanation of this failure.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6040</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The device selection phase was completed
|
||
|
|
successfully by the T2 station input/output manager (IOM) task.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6045</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The device selection response was received
|
||
|
|
by session manager.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6050</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">APPN session manager processing is complete.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" headers="wq104">6060</td>
|
||
|
|
<td align="left" valign="top" headers="wq105">The session setup has completed successfully.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|