[an error occurred while processing this directive]

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



Preserving Old-Style LU Names in the Access Server Gateway

When you migrate from a DECnet SNA Gateway to an Access Server Gateway, and you want to preserve the old-style LU names in the access routines of your users, you have to set up LU names and LU pools in SNA Server that reflect the old-style names that are already configured in the DECnet SNA Gateway access routines.

To optimize the ways in which an access routine can access a unique LU, you must set up a unique mapping to a single LU name on the SNA Server. The Access Server Manager enables you to set up a series of hierarchical procedures that uniquely select one LU name or LU pool.

The following sections discuss the general principles and strategies you should consider when setting up LU and LU pool names in SNA Server so that you can then easily map the DECnet old-style LU names to them using Access Server Manager.


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