SNAX/XF and SNAX/APN Configuration and Management Manual

Configuring for Token-Ring Support
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
9-28
Notes
Step Two: Add the Device and Start It
ADD DEVICE #TRS1, PROF TSPROF, CPU 2, ALTCPU 3,&
IOPOBJECT $SYSTEM.[sysnn].SNATSOBJ, TYPE (58,4), RECSIZE 128
START DEVICE $ZZWAN.#TRS1
Step Three: Add the LINE, PU and LU
ALTER SUBSYS $SSCP1, SNANETID USPALO01
ASSUME LINE $TR1
ADD LINE, STATION NEGOTIABLE, CHARACTERSET ASCII, &
RECSIZE 6600, MAXPUS 64, MAXLUS 1024, &
MAXLOCALLUS 256, DUPLEX HALF, &
SAPINFO (SAP %H04, MAXLS 2; SAP %H08, MAXLS 2)
ADD LU #LLU1, TYPE (14,21),SNANAME TLU1
ADD LU #LLU2, TYPE (14,21),SNANAME TLU2
ADD LU #LLU3, TYPE (14,21),SNANAME TLU3
ADD LU #LLU4, TYPE (14,21),SNANAME TLU4
ADD PU #RPU1, ADDRESS1, MAXLUS 64, TYPE (13,21), &
RECSIZE 2048, TRSSAP %H08, &
TRRMTADDR 08040011770161 &
ASSOCIATESUBDEV $PAM1.#TR1RPU1
ADD LU #RLU1, TYPE (14,21), PUNAME RPU1, SNANAME LU1
ADD LU #RLU2, TYPE (14,21), PUNAME RPU1, SNANAME LU2
ADD LU #RLU3, TYPE (14,21), PUNAME RPU1, SNANAME LU3
ADD LU #RLU4, TYPE (14,21), PUNAME RPU1, SNANAME LU4
START TR1, SUB ALL
Notes
1. In Step Two, type 58,4 refers to the Token-Ring adapter.
2. The PAM LINE object and the SNAX LINE object are not the same entity. You may
have more than one SNAX LINE per PAM LINE. The usual requirement of a
unique MAC-SAP address applies.
3. Externally there are no changes required to an existing SNAX configuration, but
you must match the ASSOCIATESUBDEV attribute to the PAM LINE and
PROCESS objects.
4. This example does not take you all the way from the base SNAX product to your
eventual application program. It is quite possible that you will continue by using the
higher-level product SNAX/APC for LU6.2 conversations.
5. To take advantage of the dynamic features of SNAX/APN and SNAX/APC — for
example, to configure a server application you may need the SNAX Creator,
Pathway, or other HP software products for NonStop systems.