[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



Step 6: Determine Any Impact to the IBM System

It is recommended that you review the gateway plans with your IBM system administration staff to determine the impact that adding the Access Server Gateway may have on the IBM system. Possible effects may include but are not limited to the following considerations:

  • If the Access Server Gateway is to be used alongside the DECnet SNA Gateway, you will need to configure new names (including nodes and LUs).
  • If the gateway will be connected to the IBM mainframe via a communications link, channel connection, or LAN, you may need to add new communication line definitions, channel device definitions, or LAN addresses to accommodate the new connections needed for the gateway.
  • If terminals or application programs are added or changed, you may need to make changes to the Customer Information Control System (CICS) tables or other IBM system tables.

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