RSCS Generation Procedure Generating and Installing RSCS General Information The data and control files required to generate and install RSCS are contained in the starter system maintenance areas of the VM/310 system. RSCS data, consists of the following. On MAINT 194:
File DMTixx TEXT DMTAXS TEXT DliTLAX TEXT DMTNPT TEXT DMTSML TEXT DMTLOAD EXEC Contents
The--pre-assembled nucleus modules
routines required to generate RSCS are: DMTASY, DMTCMX, DMTCOM, DMTCRE, DMTDSP, DMTINI, DMTIOM, DMTMAP, DMTMGX, DMTMSG, DMTREX, DMTSIG, DMTSTO, DMTSVC, DMTVEC, and supervisor
DMTAK E, DMTASK, DMTEXT, DMTGIV, DMTPST, DMTQRQ,
and DMTWAT. The spool file access method supervisor task.
The communication line allocation supervisor task.
The Nonprogrammable Terminal (NPT) line driver module.
The Spool MULTI-LEAVING (SML) line driver module.
The loadlist EXEC file. This file is required to
generate an RSCS nucleus on the RSCS system disk. DMTSYS ASSEMBLE The RSCS configuration table module. This file must be DMT MAC M ACLIB DMTRno 1 CNTRL DMTMAC EXEC
assembled with the COpy files you create to define your RSCS configuration (the AXSLINKS, LAXLINES, and TAGQUEUE COpy files).
The file containing all the macros needed to assemble
the RSCS source files.
The control file that is needed to assemble the
configuration table via the VMFASM EXEC procedure.
An EXEC file used to generate the DMTMAC MACLIB. On the VM/370 SOURCE tape: DMTxxx ASSEMBLE All the source files for RSCS. There is an ASSEMBLE file for each TEXT file previously listed.
Also, t he SOURCE tape contains all the macro and copy files included in
the DMT PI AC macro library. -----.--- -- ------
Rn 0 may be DMTR 10, DMTR20, DMTR30 and so forth, depending on the releas e level. Part 3. Generating Vl1/310 (CP, CMS, RSCS, and IPCS) 279

RSCS Generation Procedure The AXSLINKS COpy file is a list of 1 to 64 GENLINK macro statements.
The GENLINK macro defines the attributes of a link. The first GENLINK
macro in the AXSLINKS file must contain the ID of the local RSCS station. You must also code the TYPE=driverid operand with a valid
filename on this first GENLINK macro. You should code additional
GENLINK macros, with no operands, for links you may want to define
temporarily during an operating session.
The format of the GENLINK macro is:
r------------------------------ I I r , , GENLINK I I ID=linkid, TYPE=dri verid[ ,CLASS=c] I I , [ , KEEP=holdslot] 1 I I [ , LI NE=vaddr ] I I , [ ,TASK=taskname] I , I L J L
ID=linkid is a 1-to 8-character alphameric location ID of the remote
location to be served by the link. If this operand is not
specified, the ID defaults to "undefined." TYPE=driverid CLASS=c is a eMS filename of a file which is the TEXT file for the
line driver to be used to process files the link.
The appropriate line dr iver program to be specified depends on
the type of remote telecommunications facilities to be used.
The TYPE operand must specified if is coded. If
the TYPE operand is omitted, TYPE defaults to "undefined".
is the spooling class (es) of the files which can be processed
by the active link. ,-You can specify up to four spooling
classes (single alphameric characters from A to Z and 0 to 9)
with no intervening blanks, or *, which means all spool file
classes may be If the CLASS operand is not
specified, the default is "*". KEEP=holdslot
LINE=vaddr
is a decimal number from 0 to 16 which designates the number
of virtual storage file tag slots to be reserved for exclusive
use by the link. If the KEEP operand is omitted, a default
"holdslot" value of 2 is assumed.
designates the virtual device address of a permanent
telecommunications line port, to bensed for processing files
on the' link. If the LINE operand is omifteo., the defaul t 'is "undefined". TASK=taskname is a 1-to 4-character alphameric identifier. It specifies
the task name to be used by the line driver associated with
the link. If the TASK operand is omitted, the default is "undefined". Part 3. Generating VM/370 (CP, eMS, RSCS, and IPCS) 281