Dependent LU6.2 Session Fails With Event ID 14: INITSELFLast reviewed: April 17, 1997Article ID: Q148599 |
The information in this article applies to:
SYMPTOMSWhen an SNA Server starts a dependent LU6.2 session to a host system, the SNA Server sends an INITSELF command to solicit a BIND command from the host. If there is a configuration mismatch between the SNA Server and the host (VTAM and subsystem, such as CICS) or if the host application is temporarily unavailable, then the host sends a negative response to the INITSELF command and the SNA Server logs a sense code in the Windows NT application event log:
Event ID: 14 Description: APPC session activation failure: INITSELF negative response received. Sense data = <sense code> Connection = <connection name> LU alias = <Local LU alias> PLU alias = <Remote LU alias> Mode name = <mode name> LU address = <Locaddr of Local LU>NOTE: This event may start occurring after applying SNA Server 2.11 Service Pack 1 due to a change in the BIND verification for dependent APPC LU sessions. See below for more information.
CAUSEAn APPC session fails to start because the host has rejected the SNA INITSELF request sent to initiate the session. The data contains more information about the reason for the rejection. A common sense code which may be returned if a configuration mismatch exists is "1003xxxx", where 1003 indicates "Function Not Supported" and xxxx subcode indicates the sense code specific information. Under SNA Server versions 2.0, 2.1 and 2.11, SNA Server does not check the local dependent APPC LU name received in a host BIND command. Under these versions, SNA Server simply checks if the host BIND contains the same User Request Correlation (URC) field that SNA Server specified in the preceding INIT-SELF command. However, to correct an SNA Server Admin problem which this caused (see KB article Q140835), the SNA Server 2.11 Service Pack 1 version will now reject a host BIND request on a dependent APPC LU session if the Local APPC LU name does not match the SLU name received in the BIND. This change in behavior will only be seen if the local APPC LU name is misconfigured (i.e. if it does not match the VTAM LU macro name for the dependent APPC LU).
RESOLUTIONTo correct this problem, do the following (assuming that CICS is being used):
MORE INFORMATIONAll the Sense Codes are listed in Chapter 9 of the IBM SNA Formats Guide (IBM document GA27-3136). For more information in configuring independent and dependent LU6.2 and APPC for different IBM platforms (including CICS, AS/400, APPC/MVS, and APPC/VM), see the Multi-Platform APPC Configuration Guide (IBM document SV40-0089). This document is available on the APPC Forum (GO APPC) in CompuServe as MPCONT.ZIP.
|
Additional query words: prodsna
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |