.-XNETALS--=--NO------.
>>-+---------------------+-------------------------------------><
'-XNETALS--=--+-NO--+-'
'-YES-'
dependencies: |
NETID on PU statement |
Determines whether the network ID of an attaching node
or VTAM's network ID is used for an adjacent nonnative node. Used
to control how a nonnative node can attach to VTAM®.
Note: The XNETALS option has changed in the way VTAM treats PUs that send in nonnative
NETIDs in their XID. VTAM used
to let the PU connect and treated it as if it sent in the same NETID
that VTAM started with but
that is no longer true.
Note: Coding XNETALS=NO and GWCAP=NO will prevent subarea
searches of the node in which the options are coded when the DLU NETID
is not the NETID of the host. If YES is coded for either option, subarea
searches will be performed for the host in which the options were
coded.
The following matrix shows the resulting XNETALS values
when XNETALS and CONNTYPE are coded for various levels:
Table 1. XNETALS matrixStart list values |
Specified on GROUP, LINE,
or PU (lowest level wins) |
CONNTYPE |
XNETALS and result for
the PU |
YES |
YES |
APPN |
YES |
YES |
YES |
LEN |
YES |
YES |
YES |
|
YES |
YES |
NO |
APPN |
NO |
YES |
NO |
LEN |
NO |
YES |
NO |
|
NO |
YES |
|
APPN |
YES |
YES |
|
LEN |
YES |
YES |
|
|
YES |
|
|
|
|
NO |
YES |
APPN |
YES |
NO |
YES |
LEN |
YES |
NO |
YES |
|
YES |
NO |
NO |
APPN |
NO |
NO |
NO |
LEN |
NO |
NO |
NO |
|
NO |
NO |
|
APPN |
NO |
NO |
|
LEN |
NO |
NO |
|
|
NO |
|
|
|
|
not specified |
YES |
APPN |
YES |
not specified |
YES |
LEN |
YES |
not specified |
YES |
|
YES |
not specified |
NO |
APPN |
NO |
not specified |
NO |
LEN |
NO |
not specified |
NO |
|
NO |
not specified |
|
APPN |
YES |
not specified |
|
LEN |
NO |
not specified |
|
|
NO (Default) |
|
|
|
|
- XNETALS=NO
- Indicates that VTAM's network ID will be used to represent the
connecting node's network ID.
During connection:
- If the NETID operand is specified on the PU statement then, it
must specify VTAM's network ID.
- If the NETID operand is not coded on the PU statement then, VTAM's
network ID is assumed and the adjacent node's network ID is ignored.
During LU-LU session establishment:
- If the network ID for the originating LU is specified (during
connection time) and is not identical to VTAM's network ID, the session
will not be established.
- If the originating LU is not using a network qualified name, VTAM's
network ID is assumed and the session will be established.
Note: If the PU is a dependent LU server or requester,
nonnative network connection is not allowed if XNETALS=NO is specified
and the NETID operand is not coded.
- XNETALS=YES
- Indicates that the network ID of the adjacent PU will be used
for connection and session establishment.
During connection:
- If the NETID operand on the PU statement is coded, it will be
used as the PU's network ID. In this case, the network ID specified
on the PU statement must match the network ID specified by the attaching
node during connection processing.
- If the NETID operand is not specified on the PU statement, then
the network ID specified by the attaching node during connection processing
will be assumed.
During LU-LU session establishment:
- If the network ID for the originating LU is specified and does
not match the PU's network ID, the session will not be established.
- If the originating LU name is not a network qualified name, the
session will be established. VTAM will
qualify the LU's name with the attaching node's network ID.