NET/MASTER Management Services (MS) System Management Guide

Example 1: IBM Host Controlling Two Tandem Nodes
Supporting Remote Operations
105744 Tandem Computers Incorporated 9–21
Example 1: IBM Host
Controlling Two
Tandem Nodes
Having looked, generally, at how you use the LINK DEFINE, SESSION DEFINE, and
UNIT DEFINE commands to configure an INMC link, consider these steps in greater
detail using the network topology shown in Figure 9-2, earlier in this section.
The following example provides an excerpt of an SCF command file for the Tandem
production node known as \NODEA. The commands configure a line and subdevices
for INMC use. The commands produce the result depicted in Figure 9-3.
COMMENT*********************************************
COMMENT Configures SNAX/XF line and subdevices
COMMENT connecting \NODEA to IBM host
COMMENT*********************************************
ASSUME line $bita1
ALTER recsize 1044
ADD pu #pu1, type (13,2), address 193,recsize 1042,maxlus 6,&
maxpts 4
ADD lu
#
ibma1, address 2,recsize 1034,TYPE (14,2),&
puname #pu1,protocol snalu0,characterset ascii
COMMENT*********************************************
COMMENT Defines X.25 lines and subdevices connecting
COMMENT \NODEA to \NODEB
COMMENT*********************************************
ASSUME line $X25A
ALTER, calls TWOWAY
ALTER, framemode dte
ALTER, svc (1,10)
ADD su #vc1,protocol ptp,devtype (9,0),recsize 1024, port 1, ACCEPTCHG ON
ADD su #vc2,protocol ptp,devtype (9,0),recsize 1024, port 2, ACCEPTCHG ON
ADD su #vc3,protocol ptp,devtype (9,0),recsize 1024, port 3, ACCEPTCHG ON
ADD su #vc4,protocol ptp,devtype (9,0),recsize 1024, port 4, ACCEPTCHG ON
ASSUME line $X25B
ALTER, calls TWOWAY
ALTER, framemode dte
ALTER, svc (1,10)
ADD su #vc1,protocol ptp,devtype (9,0),recsize 1024, port 1, ACCEPTCHG ON
ADD su #vc2,protocol ptp,devtype (9,0),recsize 1024, port 2, ACCEPTCHG ON
ADD su #vc3,protocol ptp,devtype (9,0),recsize 1024, port 3, ACCEPTCHG ON
ADD su #vc4,protocol ptp,devtype (9,0),recsize 1024, port 4, ACCEPTCHG ON
This example (and the following \NODEB configuration example) is based on the
assumption that the communications lines are already in place and have therefore
been defined to both the SYSGEN program and the communications subsystems
(SNAX/XF and X25AM). The line to the IBM host has already been defined as a
secondary line, because SNAX lines are always secondary when connected to an IBM
host.