LUALIAS


>>-+---------------------+-------------------------------------><
   '-LUALIAS--=--lualias-'

statements:

GROUP, CDRSC

dependencies:

see description

Defines a 1–8 character name used by application programs in this domain to represent a cross-network or cross-domain resource that is defined under a NETWORK definition statement that precedes the CDRSC definition statement.

Note: LUALIAS is valid only for cross-domain and cross-network resources that are defined under a NETWORK definition statement, and is recommended only for cross-network CDRSCs which are defined using NQNMODE=NQNAME because same-network CDRSCs and NQNMODE=NAME CDRSCs are known by their unqualified resource names.

Session requests from this domain's application programs are routed to the CDRSC, when the destination resource has the same name as defined by LUALIAS. Session requests from any resource other than a VTAM® application in this domain are routed to the resource in this domain with the same name.

If you define two CDRSCs with the same LUALIAS name, only one can be active at a time. This means that a shadow resource with an LUALIAS name that duplicates a real resource with the same LUALIAS name, regardless of whether the resource names for the two resources are the same, cannot be activated until the real resource is deactivated. A shadow resource that attempts to become active and cannot because it has an LUALIAS name that duplicates an active resource is put into RESET state. After it is in RESET state, the major node of the shadow resource must be deactivated, the active resource with the LUALIAS name must be deactivated, and then the major node of the shadow resource must be activated before the shadow resource can be activated.

An LU in shadow (which does not have a duplicate LUALIAS name) also can be activated when it comes out of shadow if the LU's initial status (ISTATUS operand) was active while it was in shadow, and the CDRSC that held the LU in shadow was not deactivated.

Note: LUALIAS takes effect only in the following situations:

When the LUALIAS name has been defined for a resource that is defined on the CDRSC definition statement that is preceded by a NETWORK definition statement.
For session requests that cross the application programming interface.
For session requests whose origin or destination is the VTAM for which LUALIAS is coded. VTAMs along the session setup path are not involved with or affected by LUALIAS.
Note: LUALIAS can be used in DISPLAY commands issued in the VTAM where LUALIAS is defined. LUALIAS cannot be used in MODIFY or VARY commands, and cannot be specified for LOGAPPL.

LUALIAS is optional for cross-network or cross-domain resources predefined with the NETWORK definition statement. If it is not defined and there are duplicate names in the SNA network interconnection, application programs can use the network-qualified name [if PARMS=(NQNAMES=YES) is specified on the ACB macroinstruction] or any of the other types of alias name translation, such as:

Alias name translation with NetView®
Session management exit routine
USERVAR

Restriction: LUALIAS does not work with ALIAS name translation (regardless of whether translation is performed by NetView or the Session Management Exit). If an ALIAS name is received on a session setup request from a resource that is predefined as a CDRSC with an LUALIAS, then the received ALIAS name is presented to local applications, rather than the predefined LUALIAS name.

If you are predefining this resource just to specify an LUALIAS, consider coding LUAPFX on the APPL definition statement which does not support network-qualified names and allow the CDRSC to be created dynamically. VTAM will dynamically generate an LUALIAS for each dynamic cross-network CDRSC as needed. See LUAPFX for more information about dynamic LUALIAS.