SNAX/XF and SNAX/APN Configuration and Management Manual

Attributes for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
14-61
SNANETID (SUBSYS Object) - for SNAX/APN Only

PS/2 systems running OS/2: The SCF SNANETID attribute of the remote PU
object must match the Network ID in the Local Node Characteristics definition.

Systems using NCP and VTAM: The SCF SNANETID attribute of the remote PU
must match the NETID parameter in the VTAM Start-Up List.
SNANETID cannot be altered if LUs are defined under the PU object.
SNANETID (SUBSYS Object) - for SNAX/APN Only
When applied to the SUBSYS object, SNANETID specifies the SNA network identifier
for the NonStop node. This identifier can contain from 1 through 8 characters and must
use the SNA type 1134 character set. For a description of this character set, see the
IBM Systems Network Architecture: Formats manual.
For the rules governing valid network identifiers, see the description of the LCLNETID
parameter in the IBM document, AS/400™ Communications: Advanced Peer-to-Peer
Network Guide.
SNANETID is a required attribute for the SUBSYS object.
The SNA network identifier specified in SNANETID is sent in an Exchange
Identification, Format 3 (XID3) frame to the adjacent node. This SNA network identifier,
together with the control point name, is used in extended BIND requests. Under certain
circumstances, SNANETID must match parameters specified on the IBM system:

AS/400 systems: If the NonStop node is defined on the AS/400 system, the SCF
SNANETID attribute of the SUBSYS object must match the specification for the
RMTNETID parameter in the AS/400 Controller Description.

PS/2 systems running OS/2: The SCF SNANETID attribute of the SUBSYS object
must match the Partner Network ID in the Configure Connection definition.

Systems using NCP and VTAM: For the parameters that match SNANETID and the
circumstances under which they must match SNANETID, consult the IBM
documentation for the version and release of VTAM and NCP on your system.
Default: None
Value: String of 1 through 8 characters in the SNA type 1134 character set
Objects: SUBSYS
Note. With SNAX/APN, you can configure multiple service managers to exist concurrently in a
single NonStop node; each service manager process controls its own network configuration
(that is, the lines, PUs, and LUs). Because this situation allows many variations of a
configuration, you must take care when defining CPNAME and SNANETID attributes for
different service managers.