>>-+------------------------+---------------------------------->< +-NETID--=--(network_id)-+ '-NETID--=--(,NOXNETLS)--'
| statements: | PU |
| dependencies: | XNETALS start option |
Specifies a 1–8 character network identifier. This operand is used in conjunction with the XNETALS start option in support of nonnative network connection. See XNETALS start option for information about XNETALS.
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
- 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. The network ID specified by NETID is the CP NETID of the NETID where the PU resides. If you omit NETID, VTAM dynamically acknowledges the network ID during connection establishment and this network ID becomes the CP NETID. 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.