NET/MASTER Management Services (MS) System Management Guide
SNA Connection Guidelines
Supporting Remote Operations
105744 Tandem Computers Incorporated 9–13
SNA Connection
Guidelines
This subsection provides guidelines for configuring INMC links over SNAX lines. The
subsection includes guidelines for configuring SNAX/XF and SNAX/CDF to support
efficient data block flow. It also includes guidelines for adding session and unit
definitions that enable NonStop NET/MASTER MS to send and read INMC data
blocks over SNA lines. See “Example 1: IBM Host Controlling Two Tandem Nodes,”
later in this section, for an example of how the commands and operands are used.
SNAX/XF Configuration
Guidelines
Table 9-1 provides guidelines for the configuration of SNAX/XF lines, physical units
(PUs), and LUs that support INMC links. The guidelines state required settings for
protocol and subdevice types. The guidelines also recommend settings for data
transfer attributes. The recommended settings allow for the most efficient
transmission of INMC data blocks over SNAX lines. Refer to the SCF Reference Manual
for SNAX/XF for additional information about the attributes.
Table 9-1. SNAX/XF SCF and SYSGEN Configuration Guidelines
Line Configuration Attributes
SCF Attribute SYSGEN Attribute Setting Guidelines
STATION PRIMARY
SECONDARY
PRIMARY if the line is the primary side.
SECONDARY if the line is the secondary side (must be set
to SECONDARY if the line is connected to an IBM host).
RSIZE FRAMESIZE Minimum of 1044 (at least two greater than the RECSIZE
setting of the PUs used by NonStop NET/MASTER MS).
PU Configuration Attributes
SCF Attribute SYSGEN Attribute Setting Guidelines
RECSIZE None For SNAX/XF, 1042 (18 greater than the RECSIZE specified
for the RU of the PIU; the 18 additional bytes allow for the
9-byte SNAX header and the 9-byte path header).
For SNAXLINK, the value is automatically calculated.
TYPE None (13,2)
LU Configuration Attributes
SCF Attribute SYSGEN Attribute Setting Guidelines
PROTOCOL None SNALU
RECSIZE None For a PLU, 1024.
For a SLU, the value is ignored, because byte 11 of the
BIND, which always takes precedence, is used.
TYPE None (14,0)