Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/171623

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 10:05, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Unable to Define a Low-Priority LUA LU in SNA Server Manager

Article ID: 171623

Article Last Modified on 6/24/2004



APPLIES TO

  • Microsoft SNA Server 3.0 Service Pack 4
  • Microsoft SNA Server 4.0



This article was previously published under Q171623


SYMPTOMS

When you define an LUA LU in SNA Server Manager, there is no way to indicate that the LUA LU is low priority. Instead, all LUA LUs created using SNA Server Manager are defined as high priority, so that all traffic flowing over the LUA LU is handled at the same priority as 3270 LUs.

You can set the priority in SNA Server version 2.x. The SNA Server 2.x Administrator program supports configuration of the LUA LU priority through the "High Priority LU" checkbox located in the LUA LU Properties dialog box.

CAUSE

RESOLUTION

To work around this problem, do one of the following:

  • Use the Snacfg.exe command line configuration program to add a low- priority LUA LU, using the following command:

    SNACFG LUA <luaname> /ADD /CONNECTION:<name> /LUNUMBER:<value> /HIGHPRIORITY:No

    -OR-
  • To change an existing LUA LU to low priority, use this command:

    SNACFG LUA <luaname> /HIGHPRIORITY:No

    -OR-
  • If the above command-line configuration method is not possible, see the fix to SNA Server Manager referenced below.


STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 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 K


Keywords: kbbug kbfix kbnetwork KB171623