HP OpenVMS Systems


HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here
DIGITAL SNA access server migration guide

[Top] [Prev] [Next] [Index] [Contents] DIGITAL SNA Access Server Migration Guide

How Microsoft SNA Server Creates LU Names and LU Pools

The SNA Server does not recognize DECnet old-style LU names. This section describes how to set up LU names in SNA Server, so that you can continue to use old-style LU names in the access routines of your network users.

If you are not already familiar with how SNA Server Manager creates and uses LU names, see Microsoft SNA Server Administration Guide for a complete discussion of how to configure individual LU names and LU pools, before you continue with this section. Also see Microsoft SNA Server Planning Guide for a discussion of creating and using LU pools.

An individual LU name in SNA Server may be up to eight alphanumeric characters plus the special characters $ # and @. You can also generate a range of LU names in SNA server, which consist of a base LU name and a two-digit or three-digit extension.

To easily map old-style LU names into SNA Server LU names, it is recommended that you set up your LU names on the SNA Server as a base plus extension. Here are some examples of valid LU name ranges that you could set up in SNA Server, to match the LU LIST for the access name SNATE in Figure 3-5, above:

SNA0001, SNA0002, ..., SNA0014 (base is SNA0, extension is decimal)

SNA0001, SNA0002, ..., SNA000D (base is SNA0, extension is hex)

IBMN1001,IBMN1002, ...,IBMN1014 (base is IBMN1, extension is decimal)

IBMN1001,IBMN1002, ...,IBMN100D (base is IBMN1, extension is hex)

These examples show that you may, but do not have to, match the base name of the LU range to the DECnet SNA Gateway PU name. The base LU name may be arbitrary, although it might be helpful to use base names that reflect the existing DECnet SNA Gateway configuration.

You can set the extension in SNA Server Manager to be either decimal or hexadecimal, depending on your own particular naming scheme.

You may also want to configure the LU names into LU pools that reflect the LU lists in SET ACCESS NAME in the DECnet SNA Gateway configuration. For example, SNA0001 through SNA0014 in the example above could be assigned to the LU pool SNA0POOL. By doing this, you most nearly replicate the DECnet LU LIST functionality, allowing the SNA Server to allocate the next not-in-use LU from the pool.

[Top] [Prev] [Next] [Index] [Contents] DIGITAL SNA Access Server Migration Guide