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-60
SNANETID (PU Objects) - for SNAX/APN Only
LOCALSNANAME TC17105, DEVTYPE “3278-2”, &
SNANETID USPALO03
SNANETID (PU Objects) - for SNAX/APN Only
When applied to a PU, SNANETID specifies the SNA network identifier of the adjacent
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. Together, the SNA network identifier name and
the control point name specified in the CPNAME attribute uniquely define the link
station of the adjacent node.
If not specified, the SNANETID attribute of the PU is set equal to the value of the SNA
network identifier of the local node. (This value is specified in the SNANETID attribute
of the ALTER SUBSYS command.)
The NonStop node always attempts to validate an incoming Exchange Identification,
Format 3 (XID3) frame by comparing the received control point name and SNA
network identifier with the names stored in the CPNAME and SNANETID attributes. If
there is a match, the connection is established; if not, the connection is rejected. When
link stations negotiate their roles, Exchange Identification (XID) validation takes place
before negotiation occurs.
When not explicitly defined by the user, the CPNAME attribute defaults to 8 blank
characters. In such cases, the NonStop node will attempt validation using only the
value of SNANETID. If this value matches the SNA network identifier in the incoming
XID3 frame, the connection is established; if not, the connection is rejected. This is true
only for remote PU’s configured as NNSERVER NONE or without the NNSERVER
attribute.
For a remote PU configured as NNSERVER, MAIN, BKUP, or OTHER, the CPNAME is
an optional attribute. If not explicitly defined by the user, the CPNAME defaults to 8
blank characters. In such cases, the HP NonStop node extracts the CPNAME from the
incoming Exchange Identification (XID) from the adjacent node.
If the adjacent node does not send a control point name and SNA network identifier in
the incoming XID3 frame, the NonStop node attempts to validate using the
PUIDBLK/PUIDNUM attributes of the remote PU object.
When specified, SNANETID should match the parameter in which the adjacent node
defines its own SNA network identifier. The name and location of this parameter varies
by IBM system type. Therefore, the following matches must be made:

AS/400 systems: The SCF SNANETID attribute of the remote PU object must
match the LCLNETID parameter in the Network Attributes description.
Default: SNANETID value for the SUBSYS object
Value: String of 1 through 8 characters in the SNA type 1134 character set
Objects: PU