The information in this article applies to:
SYMPTOMS
A twinaxial connection goes to an Active state in SNA Server Manager after
the connection is started, but users are unable to get active APPC sessions
on an AS/400 through the twinaxial connection.
NOTE: The System Operator Log on the AS/400 can be accessed by entering the following command on an AS/400 command prompt: DSPMSG QSYSOPRThe following event may also be logged in the Windows NT Application Event Log on the SNA Server computer: This problem does not occur when you upgrade SNA Server 2.11 to SNA Server 3.0. CAUSEThe problem is caused by the way SNA Server 3.0 saves the twinaxial connection properties in the SNA Server configuration. The twinaxial connection is saved as a Peer connection, as are all other connections to AS/400s. The problem is that twinaxial connections are not saved with all of the connection properties that other Peer connections include, such as Peer DLC Role and XID Type. WORKAROUNDTo work around this problem:
STATUSMicrosoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C KAfter you apply the updated binary file, do the following so the twinaxial connection will successfully connect to the AS/400:
MORE INFORMATIONThe problem is that twinaxial connections are not saved with all of the connection properties that other Peer connections include, such as Peer DLC Role and XID Type. This results in an incorrect sequence when activating a twinaxial connection, as shown below:
In this sequence, the XID negotiation, shown as SXID and RQOS messages, is
done after the Station Contacted (DLCST STCD) message.
The correct sequence when activating a Peer connection is shown below:
In the correct sequence, the XID negotiation occurs before the Open Station
(Open Stat) and Station Contacted messages.
SNA Server has been updated to correctly save the twinaxial connection with all of the Peer connection properties and to do the XID negotiation before it does the Open Station sequence. In addition, the Twinaxial connection properties page will be updated to include a System Identification page. This page will include configuration options for the Local Node Name, Remote Node Name, XID Type, and Peer DLC Role. Additional query words:
Keywords : kbnetwork snatwinax kbfix3.00.sp2 |
Last Reviewed: November 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |