LU Has Blank Status after Connection Move to Another SNA Server

ID: Q241320

The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3

SYMPTOMS

A 3270 or LUA LU (Logical Unit) may show a "Blank" status in SNA Server Manager after the host connection it is associated with is moved to another SNA Server computer. Usually, the "Blank" LU status is only seen on instances of SNA Server Manager other than the one where the connection move was performed. On the computer where the connection move was performed, the connection and its LUs will have the same status as they had prior to the connection move, which may also be an incorrect status.

This can also occur when a connection and its associated LUs are moved from one SNA Server service to another SNA Server service on the same SNA Server computer. A computer running SNA Server 4.0 (or later) can support up to four SNA Server services.


CAUSE

The Manage components associated with a connection and its LUs are not moved when the connection is moved to another SNA Server computer. Also, moving a connection between SNA Server services on the same SNA Server 4.0 (or later) computer results in the Manage components being duplicated. This can cause LU status updates to be sent to the incorrect Manage objects, which results in incorrect an LU status in SNA Server Manager.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

File name Date Time
Snaadmin.dll 08/06/99 11:40AM
Mngsna.dll 08/06/99 01:24PM
Snaole.dll 08/06/99 11:41AM

NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files.


STATUS

Microsoft has confirmed this to be a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3.


MORE INFORMATION

The following example demonstrates how this problem occurs when you move connections between SNA Servers and SNA Server services on the same SNA Server system:

Configuration:

Primary SNA Server 4.0 SP2 system
Backup SNA Server 4.0 SP2 system
Connections moved using the drag-and-drop operation in SNA Server Manager:
TEST1 - Originally on the primary SNA Server service on the Primary SNA Server (PRIMARY)
TEST2 - Originally on the primary SNA Server service on the Backup SNA Server (BACKUP)
Each connection had one 3270 LU defined.

TEST1 is configured for On Demand startup.
TEST2 is configured for On Server Startup.
  1. Open SNA Server Manager on both SNA Server computers.


  2. The primary SNA Server service on both SNA Server computers is Active, as is the secondary SNA Server service on BACKUP.


  3. Use the drag-and-drop operation to move TEST1 from Primary SNA Server (PRIMARY) to primary SNA Server service on Backup SNA Server (BACKUP). Assign a link service (SNADEMO1) to the connection.


  4. Use the drag-and-drop operation to move TEST2 from primary SNA Server service on BACKUP to secondary SNA Server service on BACKUP. Assign a link service (SNADEMO2) to the connection.


  5. Save the configuration.


  6. SNA Server Manager, where the connection moves were performed, shows the following status:
    Connection LU

    TEST1(Active) Available
    TEST2 (Active) Available
    This is incorrect because a connection moved to a new SNA Server service cannot be active and the LU cannot be Available.


  7. Other instances of SNA Server Manager that are open show the following when the configuration is refreshed:
    Connection LU

    TEST1 (Offline) Blank
    TEST2 (Offline) Blank


  8. The SNA Server services on the backup SNA Server (BACKUP) are "Out of Date" as expected. Restarting the SNA Server services corrects the status problem in SNA Server Manager on the primary SNA server (PRIMARY) where the moves were performed.


Additional query words:

Keywords : sna3 sna3sp1 sna3sp2 sna3sp3 sna3sp4 sna4 sna4sp1 sna4sp2 sna4sp3
Version : WINDOWS:3.0,3.0 SP1,3.0 SP2,3.0 SP3,3.0 SP4,4.0,4.0 SP1,4.0 SP2,4.0 SP3
Platform : WINDOWS
Issue type : kbbug


Last Reviewed: September 23, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.