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.
| State | Reason |
|---|---|
| 1000 | Session setup complete. An existing session will be used; therefore, APPN control point functions will not be called. |
| 1015 | Session setup request has failed. Refer to sense code for details. |
| 1020 | Session setup rejected. The local location name chosen is not defined in either the network attributes or as a local location list entry. |
| 1025 | Session setup rejected. Mode name specified is not defined on the system. |
| 1030 | Session setup request has been sent by location manager to resource manager to obtain a device. |
| 1032 | 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. |
| 1035 | Session setup has been pended because of a previous request that is waiting for the request transmission group vectors processing to complete. |
| 1040 | 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. |
| 1050 | 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. |
| 1060 | Session setup has been pended because of a previous request that is still waiting for the switched link activation phase to complete. |
| 1070 | Session setup has been pended because of a previous request that is still waiting for the location search phase to complete. |
| 1080 | A request transmission group vectors request is outstanding to topology routing services component. |
| 1082 | A request transmission group vectors request is being processed by topology routing services component. |
| 1084 | The request transmission group vectors response was returned by the topology routing services component. |
| 1086 | The request transmission group vectors request has been received by session services. |
| 1090 | Location search phase request is outstanding, but has not yet been received by the local system's directory services function. |
| End Node Location Search Phase (2000 - 2999) States | |
| 2000 | The local system's directory services has received the search request and has begun its processing. |
| 2010 | There is a one hop search request outstanding to the local system's network node server. |
| 2020 | Location search processing has been completed by the local system's directory services. |
| 2025 | Session services has received the locate message response from directory services. |
| 2030 | 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. |
| 2040 | 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. |
| 2050 | 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. |
| 2060 | Location search phase has failed. The network node server has sent an SNA negative response indicating that the class-of-service is not valid. |
| 2070 | Location search phase has failed. The network node server has sent an SNA negative response indicating a route-not-available condition. |
| Network Node Location Search Phase (3000 - 3999) States | |
| 3000 | The local system's directory services has received the search request and has begun its processing. |
| 3010 | 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. |
| 3012 | Query control-point name request is being processed by topology routing services. |
| 3014 | Query control-point name response has been sent by topology routing services. |
| 3016 | Query control-point name response has been received by directory services. |
| 3020 | One hop search request is outstanding to an attached end node. |
| 3030 | A request for a route is outstanding to topology routing services so that a directed search can be sent to another network node. |
| 3032 | Request route for directed search is being processed by topology routing services. |
| 3034 | Request route response for directed search has been sent by topology routing services. |
| 3036 | Request route response for directed search received by directory services. |
| 3040 | A directed search request is outstanding to another network node. |
| 3050 | A request for a route is outstanding to topology routing services for a remote search. |
| 3052 | Request route for a remote search is being processed by topology routing services. |
| 3054 | Request route response for a remote search has been sent by topology routing services. |
| 3056 | Request route response for a remote search was received by directory services. |
| 3060 | A routed search request is outstanding to a network node. |
| 3070 | 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. |
| 3080 | 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). |
| 3090™ | 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. |
| 3092 | Request route for a node that can access multiple networks is being processed by topology routing services. |
| 3094 | Request route response for a node that can access multiple networks has been sent by topology routing services. |
| 3096 | Request route response for a node that can access multiple networks was received by directory services. |
| 3100 | A search request is outstanding to a node that can access multiple networks. |
| 3110 | A request is outstanding to the session services component in order to perform functions necessary to send searches into a different APPN network. |
| 3120 | The location search phase has completed and a response has been returned by directory services. |
| 3125 | The location search phase has completed and the response has been received by session services. |
| 3130 | The location search phase has failed. |
| Route Selection Phase (4000 - 4999) States | |
| 4000 | A request for a single hop route is outstanding to the topology routing services component. |
| 4002 | The request for a single hop route is being processed by topology routing services. |
| 4004 | The request single hop route response has been returned by topology routing services. |
| 4006 | The request single hop route response has been received by session services. |
| 4010 | A request single hop route failure has occurred. |
| 4030 | A request for a route is outstanding to the topology routing services component. |
| 4032 | The request for a route is being processed by topology routing services. |
| 4034 | The request route response has been returned by topology routing services. |
| 4036 | The request route response has been received by session services. |
| 4040 | The request for a route has failed. The class-of-service name being used is not defined on the local system. |
| 4050 | 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). |
| 4060 | 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. |
| 4062 | 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. |
| 4064 | 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. |
| 4066 | 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. |
| 4068 | 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. |
| 4080 | Session setup failure. The controller description that represents the first hop of the route is unknown by the local system. |
| Switched Link Activation Phase (5000 - 5199) States | |
| 5000 | The request to activate the switched link is currently outstanding from session services. |
| 5005 | Configuration services has begun processing the activate route request but has not yet completed its processing. |
| 5010 | The activate route has completed, but some failure has occurred. Details are based on sense code. |
| 5020 | 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. |
| 5030 | 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. |
| 5040 | 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. |
| 5050 | 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. |
| 5070 | The request to activate the switched link has been pended. The system is currently in the process of establishing an outgoing connection. |
| 5080 | The request to activate the switched link has been pended. The outgoing connection has been made, but the exchange identification phase is in progress. |
| 5090 | 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. |
| 5100 | The switched link activation has completed successfully. |
| 5110 | The session services component has received its response to its switched link activation request. |
| Non-Switched Link Activation Phase (5200 - 5299) States | |
| 5200 | Session services is waiting for configuration services to complete the non-switched link activation. |
| 5210 | The non-switched link activation phase has completed successfully. |
| HPR Route Setup Phase (5300 - 5399) States | |
| 5300 | A request to determine whether a session should be carried over an RTP connection is outstanding. |
| 5310 | The request to determine if an RTP connection should be used for the session has detected an error. |
| 5315 | An HPR Route Setup request is outstanding. |
| 5320 | The HPR Route Setup request was returned with a good completion. |
| 5325 | The HPR Route Setup request has failed. |
| 5330 | The HPR Route Setup phase has completed successfully. |
| APPN Virtual Controller Selection Phase (5400 - 5499) States | |
| 5400 | The request is outstanding to the virtual controller manager component to find the APPN virtual controller description. |
| 5490 | The request to find the APPN virtual controller description has failed. |
| 5495 | The request to find the APPN virtual controller description has completed successfully. |
| Device Selection Phase (6000 - 6999) | |
| 6000 | A request is outstanding to the T2 station input/output manager (IOM) task to select a device. |
| 6005 | The T2 station input/output manager (IOM) task has begun processing the get device request. |
| 6010 | Device selection pended. The device was found, but it is in the process of being automatically varied on. |
| 6020 | Device selection pended. No device was found; therefore, a new device is in the process of being created and varied on. |
| 6025 | 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. |
| 6030 | The device selection has failed. Refer to the sense data returned for an explanation of this failure. |
| 6040 | The device selection phase was completed successfully by the T2 station input/output manager (IOM) task. |
| 6045 | The device selection response was received by session manager. |
| 6050 | APPN session manager processing is complete. |
| 6060 | The session setup has completed successfully. |
