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

Configure SNA Server LU Information

Using the PU and LU information from the SNA Server Preparation Forms for Configuring LUs, configure all Microsoft SNA Server LUs and LU pools that you want to have available for the Access Server Gateway. Establish all LUs, LU pools, local LUs, remote LUs, and logon modes. If you're migrating an existing DECnet SNA Gateway, recall that this information was collected from the SET ACCESS NAME and SET PU commands in the DECnet SNA Gateway configuration file. You can review the access name information that comes from the DECnet SNA Gateway configuration file in Figure 3-5 in Chapter 3.

DIGITAL SNA Access Server is designed to work only with LUA type LUs (application LUs). When you build your LU and LU pool definitions in the SNA Server, make sure that they are all defined as LUAs (application LUs).

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