NETID


>>-NETID--=--network_id----------------------------------------><


>>-+---------------------------+-------------------------------><
   +-NETID--=--(network_id)----+   
   |                       (1) |   
   '-NETID--=--(,NOXNETLS)-----'

Notes:

NOXNETLS applies only to the PU definition statement.

statements:

BUILD

statements:

PCCU, GROUP,
HOST, NETWORK
PU

dependency:

VTAM® and NCP

dependency:

VTAM and NCP; SNI only; COPIES

Specifies 1–8 character network identifier.

Note: The use of the national character, #, is discouraged, because this character might not be present on keyboards of terminals produced in other countries. Because # might not be available on all terminals, SNA architecture specifically excludes # from the list of valid characters that can be used for defining network identifiers. Although VTAM allows you to use #, other products might enforce this restriction.

NETID=(network_id)

On PCCU: (network_id) specifies the 1–8 character name of the network of the host represented by this PCCU definition statement. VTAM uses this name along with the SUBAREA operand to determine which PCCU definition statement it should process in the NCP major node.

On BUILD: (network_id) specifies the network name of the host coded on the NETID start option. This operand is required for NCP V4R3 and later releases.

On HOST: (network_id) specifies a 1–8 character name that identifies the network containing the corresponding host node. It is used along with the SUBAREA operand to determine which HOST definition statement the VTAM host should process. This operand is optional.

On NETWORK: (network_id) specifies the 1–8 character network identifier of the nonnative network in which the gateway SSCP resides. If the value for NETID matches the value of VTAM’s NETID start option, VTAM uses the MAXSUBA value on this statement as the maximum subarea value, and the SUBAREA value is the actual subarea for the gateway NCP representation in the VTAM network.

On PU: (network_id) specifies a 1–8 character network identifier. For type 4 and 5 physical units, network_id identifies the network of the subarea serviced by the line. NETID is used only in gateway NCPs, and is required for a connection to another network.

NETID=(,NOXNETLS)

PU only:(,NOXNETLS) specifies that VTAM does not allow nonnative network attachment for LU-LU sessions for this PU. When NETID=(,NOXNETLS), VTAM indicates to the NCP that this PU uses VTAM’s native network ID.

LU-LU sessions might fail if the NETID sent in the BIND from the LU is different than the NETID specified in VTAM (even though PU-PU connections can be established). If no NETID is included in the BIND, or if the NETID is identical to that specified by VTAM, the LU-LU session should activate.

Note: For switched subarea connections, all lines within the same group must be defined with the same network_id.

For type 2 physical units, NETID is used in conjunction with the XNETALS start option in support of nonnative network connection. See XNETALS start option for information about XNETALS.

If you specify NETID on the PU definition statement, VTAM ensures that when the physical unit is active, the connecting resource is within the network specified by NETID. If you omit NETID, VTAM dynamically processes the network ID when a connection is established. If you code NETID, and nonnative network connection is not supported, the definition is rejected unless the operand specifies VTAM’s network ID.

If dynamic dial-out connections are required (that is, a session request drives the dial), NETID must be predefined. Otherwise, VTAM might not be able to determine the connecting network ID and the resultant sessions might fail. If leased connections are not established, and if NETID is not predefined, directory requests could fail because of VTAM’s inability to determine the resource’s actual network.