FIX: The SNA Server service may return an incorrect remote APPC LU alias to an invokable TP if multiple remote APPC LUs exist with different aliases but with the same fully qualified LU name in Host Integration Server 2000 (892636)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1
  • Microsoft Host Integration Server 2000 SP2

SYMPTOMS

The SNA Server service, Snaservr.exe, may return an incorrect remote Advanced Program-to-Program Communications (APPC) logical unit (LU) alias to an invokable Transaction Program (TP). This problem occurs if multiple remote APPC LUs exist with different aliases but with the same fully qualified LU name. This problem occurs in Microsoft Host Integration Server 2000. The RECEIVE_ALLOCATE verb that is issued by the invokable TP may complete with an incorrect remote APPC LU alias or with an incorrect partner APPC LU alias.

The actual symptoms that are experienced by the invokable TP vary. How the actual symptoms vary depends on how the application is designed. An invokable TP that is designed to look in the remote APPC LU alias instead of the fully qualified LU name is likely to experience errors when this problem occurs. An invokable TP that does not explicitly look in the remote APPC LU alias may not experience errors when this problem occurs.

The SNA LU 6.2 Resync TP service cannot complete an Exchange Log Names (XLN) sequence when this problem occurs. The following event is logged by the SNA LU 6.2 Resync TP when this problem occurs:

Event ID: 118
Source: SNA LU6.2 Resync TP
Description: (118) A Remote Environment rejected the log name exchange (XLN) initiated by the SNA LU 6.2 Resynchronization Service
EXPLANATION Host LU Remote APPC LU Name rejected the attempt by local LU Local APPC LU Name to synchronize logs. Local log state was Log State. Host log state was Log State.

Note The SNA LU 6.2 Resync TP may log Event ID 118 under conditions other than the condition that is described here.

CAUSE

If multiple remote APPC LUs with different aliases but with the same fully qualified LU name exist, the SNA Server service may match the wrong remote APPC LU with the local APPC and with APPC Mode. This problem occurs when the SNA Server service creates a dynamic internal record for the APPC session that a host application is trying to establish. The result is that the wrong remote APPC LU alias is returned to the RECEIVE_ALLOCATE verb when a host application tries to invoke the invokable TP.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
  Date         Time   Version       Size     File name
  -----------------------------------------------------
  17-Jan-2005  18:44  5.0.0.1021  471,312    Snaservr.exe     
  17-Jan-2005  18:44  5.0.0.1021  1,065,232  Trcservr.exe
Note Because of file dependencies, the most recent fix that contains the previous files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The following is an example of a configuration that may cause this problem to occur:
Remote APPC LU aliasFully qualified remote APPC LU nameHost connection
Remote1 APPN.REMOTEConnection1
Remote2APPN.REMOTEConnection2
If a mainframe application sends an FMH-5 ATTACH message for the invokable TP over host connection Connection1 for APPN.REMOTE, the RECEIVE_ALLOCATE verb that is posted by the invokable TP may complete with the following information:

Remote APPC LU Alias: Remote2
Fully-qualified Remote APPC LU Name: APPN.REMOTE

In this example, the correct remote APPC LU alias for the APPC session over host connection Connection1 is Remote1.
Modification Type:MinorLast Reviewed:6/5/2006
Keywords:kbHotfixServer kbQFE kbfix kbbug KB892636 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.