NETID


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

statements:

dependencies:

XNETALS start option

Specifies a 1–8 character network identifier.

Note: The use of the national character, #, is discouraged, because it might not be on keyboards of terminals produced in some 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

For type 4 and 5 physical units: NETID identifies the network in which this physical unit resides. It is required for a connection to another network.

If you do not specify a value, the network specified as NETID in the VTAM start options is used.

For type 2 physical units: This operand is used in conjunction with the XNETALS start option in support of nonnative network connection. See "VTAM start options" 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 connections are established. If you code NETID, and nonnative network connection is not supported, the definition is rejected unless the operand specifies VTAM’s network id.

NETID=(,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.

If a dynamic nonnative dial-out connection is required (that is, a session request drives the dial), and it is not an APPN connection, then NETID must be predefined. This ensures that subsequent session requests do not fail because of VTAM's inability to locate dependent logical units by using the dynamic nonnative NETID of the physical unit. This is also true when establishing a DLUS pipe, which is an APPN connection.

For dependent LU server PUs, VTAM will not dynamically process the network ID when CPSVRMGR sessions are established. To correctly define the NETID of a dependent LU server, if the NETID coded on the DLURNAME operand on the PATH statement is different from VTAM's network ID, the NETID parameter on the PU statement must be coded with the NETID coded on the DLURNAME otherwise the VTAM's network ID will be used for the PU.