The information in this article applies to:
SUMMARYMicrosoft SNA Server 3.0 Service Pack 3 and later versions include support for LU6.2 "persistent verification" as described in the following Knowledge Base article: Q180866 Persistent Verification Support for APPC SessionsIn order for an application to make use of SNA Server persistent verification support, the application must do the following:
MORE INFORMATION
Persistent verification (PV) eliminates the need to provide a user ID and
password on each Attach during multiple conversations between a user and
its partner at a remote LU. The user is verified once during a sign-on
process during its initial conversation over an LU6.2 session between an
LU/LU pair, and remains verified until the user is signed off by the remote
LU, or if all sessions between the LUs are ended.
Byte 23, Bit 7 persistent verification capability must be set to 1 (ON): (Persistent Verification indicator is supported on incoming FMH-5s)Note that SNA Server does not set this bit, because SNA Server only supports the sending of FMH-5 Attach requests with persistent verification. SNA Server does not support incoming FMH-5 Attaches which have persistent verification set. If SNA Server detects that the remote system supports persistent verification (as indicated in the host BIND message), then the APPC or CPIC application can take advantage of persistent verification by setting security = SAME, and by providing a user ID AND password on every allocate request. SNA Server then implements PV by maintaining a PV sign-on user list associated with each Remote APPC LU as follows:
REFERENCESIBM documents the format of the SNA BIND command and FMH-5 Attach requests in the following IBM reference: Title: Systems Network Architecture FormatsFor more information about persistent verification, please see the following IBM reference: Title: SNA LU 6.2 Peer Protocols Additional query words:
Keywords : |
Last Reviewed: November 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |