Consider the following scenario:
In this scenario, the SNA Server service does not try to make the LU 6.2 sessions active again by sending additional BIND RUs. When this problem occurs, the number of LU 6.2 sessions that are automatically made active is less than the total configured sessions that are to be made active as specified in the Host Integration Server configuration.
- An instance of Microsoft Host Integration Server is configured to communicate with an IBM mainframe Advanced Program-to-Program Communications (APPC) application by using Logical Unit type 6.2 (LU 6.2).
- An APPC Mode definition on the instance of Host Integration Server includes Partner definitions to automatically make LU 6.2 sessions active.
- The SNA Server service receives BIND -RSP response units (RUs) from the IBM mainframe when it tries to make the LU 6.2 sessions active.
- The BIND -RSP RUs include one of the following IBM sense codes. These codes indicate the reason that the session requests failed.
- 8001
- 8002
- 8003
- 8013
In this scenario, the SNA Server service does not try to make the LU 6.2 sessions active again by sending additional BIND RUs. When this problem occurs, the number of LU 6.2 sessions that are automatically made active is less than the total configured sessions that are to be made active as specified in the Host Integration Server configuration.