SNAX Connection Manager (SNAX/CM) Manual

SNAX/CM Configuration Examples
Configuring SNAX/CM
097842 Tandem Computers Incorporated 2–7
== Configure floating PUs and LUs.
assume pu $sscp.#pu2
add,address %HF2,maxlus 1,type (13,2),recsize 265, &
calladdr 333333333333302
alter,puidblk %H017
alter,puidnum %H01141
start
assume lu $sscp.#lu2
add,puname #pu2,address 2,protocol snalu,type (14,0), &
recsize 256,devtype "3278-2",characterset ascii
start
assume line $SOXP1
start, sub all
assume line $SOXP2
start
== Define the APPLobject to be used by SNAX/CM.
add appl $sscp.#sxc1,appltype cmappl
add appl $sscp.#sxc2,appltype cmappl
Using SNAX/CM in a Token-
Ring Environment
This subsection describes how SNAX/CM manages connections to a Token-Ring
network. See the SNAX/XF Configuration and Control Manual for an overview of the
Token-Ring architecture, definition of terms, and more detailed information about
Tandem’s implementation using SNAX/XF.
Using SNAX/CM, multiple PUs can be configured in a single SNAX/XF line handler,
where each PU represents an independent switched component. When adding a
remote PU, certain Token-Ring aspects do not have to be preconfigured; they can be
left undefined and subsequently supplied dynamically using the SNAX/CM ENABLE
and CONNECT commands (described in Section 3).
Switched lines managed by SNAX/CM allow a user to supply the remote MAC
address, remote SAP value, and local SAP value when starting the session. (These
terms and how these components work together are described in detail in the
SNAX/XF Configuration and Control Manual ). In addition, SNAX/CM supports XID
validations made by user processes.
Configuration Considerations
Two SCF attributes handled differently when using SNAX/CM than when using
SNAX/XF are ASSOCIATESUBDEV and LANRMTADDR.
Because the SYSGEN attribute ASSOCIATESUBDEV is specified for lines, it must not
be used during system generation for a Token-Ring line. However, the SCF attribute
ASSOCIATESUBDEV can be specified for a PU using SCF when a line is added or
altered. When using SNAX/CM to manage lines, the ASSOCIATESUBDEV name can
be optionally specified using the SNAX/CM PORT parameter. The use of
ASSOCIATESUBDEV is similar to that of SNAX/XF in X.25 operations in that it must
identify the name of an existing TLAM device and must also specify a subdevice
name. The ASSOCIATESUBDEV parameter is required if PUs are configured on a
Token-Ring line that is not managed by SNAX/CM.