SNAX/XF and SNAX/APN Configuration and Management Manual

SCF Commands for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
13-9
ADD LINE Command

You can also specify any SNAX/XF attribute for the LINE object. However, note the
following:

SNAX/APN cannot share a switched line. Thus, no switched line attributes
apply to a shared line.

SNAX/APN does not support SNAXLink lines and, therefore, cannot share a
SNAXLink line. The following attributes have no operational effect when
specified on a SNAX/XF line that is also used by SNAX/APN: BURST,
IBMCUADDR, PROG9367, and PROG9370.

The following attributes have no operational effect on lines used by
SNAX/APN: CONNECTAPPL, SPXID, and SWSESSTIMEOUT.

The SNAX/XF attribute ESSTABLE, which supports SNAX LU Network
Services (LUNS), should be specified on shared lines only when the NonStop
node serves as a primary link station in a multipoint configuration.

SNAX/APN does not support switched floating PUs and LUs. SNAX/APN PUs and
LUs are always permanently subordinated.
SNAX/XF does not permit permanently subordinated PUs and LUs and switched
floating PUs and LUs to coexist on the same line. Consequently, lines shared by
SNAX/APN and SNAX/XF cannot use switched floating PUs and LUs.
Also, for this reason, the ZSX1-ASSOC-SUBDEV token for the LINE object, which
supports switched floating PUs and LUs, has no effect or meaning in a SNAX/APN
environment.

On shared lines, the SNAX/APN attributes MAXLOCALLUS, MAXRCVSIZE,
PUIDBLK, and PUIDNUM have no effect on SNAX/XF operation.
You should not specify the STATION attribute as NEGOTIABLE on lines that
SNAX/APN PUs share with SNAX/XF PUs. Such lines should always be
specified as either PRIMARY or SECONDARY.
Example for SNAX/APN
->ADD LINE $APN1, MAXPUS 1, MAXLUS 30, MAXLOCALLUS 10, &
->RECSIZE 524, STATION NEGOTIABLE
IOPAGES SNRMIFDM
MAXLUS SUPFCSERRMSG
MAXPUS TIMEOUT
POLLINT WINDOW
RECSIZE XMTTIMEOUT
RETRIES XPAGES