[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



Mapping DECnet SNA Gateway Old-Style LU Names to SNA Server LU Names

Once you've set up LU names and LU pools in SNA Server Manager, you can configure Access Server Manager to search for and activate an available LU name, depending on the access routine parameters that are used in any particular situation.

In the previous section, we saw how a variety of different access routine commands may specify parts of the information required to uniquely identify an LU name. The Access Server uses a hierarchy of parameters to build a unique old-style LU name. Table 3-5 shows how the Access Server interprets different DECnet SNA Gateway access routine parameters, including a way of interpreting an old-style LU name into a defined SNA Server LU name. This information can help you determine how to map your current DECnet SNA Gateway access routine parameters to the Access Server Gateway.

Table 3-5: How Access Server Interprets DECnet SNA Gateway Access Routine Parameters
Condition Examples Access Server Action Result
No PU or session address is specified
AND
an access name is specified
$set host/sna
/access_name=snate atog
Choose an available LU from the LU list specified for the Access Name in Access Names IBMLU01A
No PU is specified
AND
a session address is specified
$set host/sna
/access_name=snate
/sess=14 atog
Construct an LU name: choose from the Base Name list specified for the Access Name and add the session address as a decimal or hexadecimal extension, as specified IBML100E
A PU is specified
AND
no session address is specified
$set host/sna/pu=sna-0 atog $set host/sna
/access_name=snate
/pu=sna-0 atog
Use the LU name or LU pool specified for that old-style name in Name Mapping IBMNPOOL
A PU is specified
AND
a session address is specified NOTE: this is an old-style LU name
$set host/sna/pu=sna-0
/sess=14 atog $set host/sna
/access_name=snate
/pu=sna-0/sess=14 atog
Map an old-style name: use the Base Name specified for that old-style name in Name Mapping and add the session address as a decimal or hexadecimal extension, as specified IBMN100E
A specific LU name or LU pool is specified $set host/sna
/pu=IBML100D atog
Use the specified Access Name IBML100D
An old-style LU name (PU plus session address) is specified
AND
an Access Name is specified
$set host/sna
/access_name=snate
/pu=sna-0/sess=14 atog
The Access Name is overridden by the old-style name and name mapping is used IBMN100E
NOTE: If a valid LU name or LU pool or Access Name is not specified, then an old-style LU name, either with or without a session address, must be specified in order to build a valid Access Server LU name.

Table 3-6 shows an example of how to configure Access Name parameters in the Access Server, based on the DECnet SNA Gateway configuration file in Figure 3-1 and the example Access Server Configuration Worksheet in Figure 3-4. It lists the parameters from the SET ACCESS NAME command and shows how they might be used to configure LU information in the SNA Server Manager and in the Access Server Manager.

Table 3-6: Example Access Name Parameters
DECnet SNA Gateway Configuration File Parameter Access Name Parameter in DIGITAL SNA Access Server
Parameter Example Value Parameter Mapped Values
SET ACCESS NAME SNATE ACCESS NAME SNATE
LU LIST 1-14 LU LIST SNA001, ..., SNA014
or
SNA0POOL ¥
APPLICATION TSO PARTNER LU TSO
LOGON MODE TE LOGON MODE TE
PU (CIRCUIT) SNA-0 BASE NAME* SNA0 ¥
NOTE: Most properties are set in the Access Server Manager. ¥Properties marked with a ¥ are set in Connection Services and are mapped in the Access Server Manager. *The Base Name Radix is set to decimal or hexadecimal, depending on how you set the base name extension in the SNA Server Manager.

Table 3-7 shows an example of how to configure the Name Mapping parameters in the Access Server, based on the DECnet SNA Gateway configuration file in Figure 3-1 and the example Access Server Configuration Worksheet in Figure 3-4. You specify the exact old-style LU name from the DECnet SNA Gateway and then map either or both of the LU Name and Base Name parameters that you set up in the SNA Server.

Table 3-7: Example Name Mapping Parameters
DECnet SNA Gateway Configuration File Parameter Name Mapping Parameter in DIGITAL SNA Access Server
Parameter Example Value Parameter Mapped Values
SET ACCESS NAME
LU LIST 1-14 LU NAME SNA0POOL ¥
PU (CIRCUIT) SNA-0 OLD-STYLE NAME SNA-0 ¥ ¥
PU (CIRCUIT) SNA-0 BASE NAME* SNA0 ¥
¥Properties marked with a ¥ are set in Connection Services and are mapped in the Access Server Manager. ¥ ¥Old-Style Name is set in the Access Server Manager. *The Base Name Radix is set to decimal or hexadecimal, depending on how you set the base name extension in the SNA Server Manager.

In both cases, note that you only need to specify those parameters that you require for your particular network access environment.


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