How To Stop SNA Server From Retrying BIND Attempts (250145)
The information in this article applies to:
- Microsoft Host Integration Server 2000
- Microsoft SNA Server 3.0 SP4
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
This article was previously published under Q250145 SUMMARY
In some cases, you may want to stop SNA Server from retrying BIND attempts when an APPC or CPI-C application is attempting to establish a conversation.
One instance where it might be useful to stop the BIND retries is if APPC or CPI-C sessions are configured on the SNA Server to connect to a CICS region on the mainframe, and the CICS region is down. By default, the SNA Server tries to reestablish the sessions until the region is available. This behavior can cause unwanted network traffic and can cause the Event Log on the server to fill up with Event 18 messages reporting failed BIND attempts.
NOTE: SNA Server 4.0 and later will not log multiple Event 18 messages for each failed BIND attempt on the same LU/LU/Mode triplet.
Modification Type: | Major | Last Reviewed: | 6/28/2004 |
---|
Keywords: | kbhowto KB250145 |
---|
|