RSCS Generation Procedure On the TYPE operand, DMTNPT refers to the Nonprogrammable Terminal (NPT) line driver program and DMTSML refers to the Spool MULTI-LEAVING (SML) line driver program.
edit laxlines copy NEW FILE: EDIT:
input INPUT: *copy lax lines
genline line=079
genline line=07a
genline line=07b
genline line=07c
genline line=07d genline line=07e
genline line=07f
EDIT:
file
R;
edit tagqueue copy NEW FILE:
EDIT:
input INPUT: *copy tagqueue
gentagq num=32
EDIT:
file
R; STEP 5. CREATE THE DMTLOC MACRO LIBRARY Using the COpy files created in Step 4, generate a CMS macro library
called DMTLOC MACLIB, as follows:
maclib gen dmtloc axslinks laxlines tagqueue
If you must change your RSCS configuration at a later time, you have
to change the COpy file and then generate a new DMTLOC macro library. STEP 6. ASSEMBLE THE CONFIGURATION TABLE (DMTSYS) Before you assemble the configuration table module, access the staging
area disk (194) as an extension of the RSCS system disk.
access 194 b/a DMSACC7231 B (194) RIO NOw, assemble the RSCS configuration table module (DMTSYS) using the VMFASM EXEC procedure. Specify DMTRnO as the control file. This
control file identifies DMTLOC as the macro library to be used during
the assembly. The DMTRnO control file is on the 194 minidisk. Invoke VMFASM as follows: VMFASM DMTSYS DMTRnO If an error occurs due to an incorrectly coded macro, correct the
macro and restart at Step 5. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 285

RSCS Generation Procedure STEP 7. INVOKE GENERATE TO CREATE THE RSCS NUCLEUS Invoke GENERATE to build the RSCS system nucleus as follows:
generate rscs build
GENERATE prompts you for the operands it needs to link to the RSCS system disk:
ENTER RSCS SYSTEM DISK LINK PARAMETERS: USERID VADDRl VADDR2 If you are following the examples in this procedure, you enter
rscs 191 195
The value you enter for vaddr2 must be the same value you specified for
vaddr2 on the LINK command issued in Step 3; otherwise, the link is not The you specify is the of RSCS virtual machine and the virtual address you specify for vaddr1 is the virtual
device address of the RSCS system disk in the RSCS virtual machine. You will be prompted for the write password of the disk.
GENERATE then links to the RSCS system (DMTNPT, DKTSKL, DMTAXS, and DMTLAX) to it.
message:
disk and copies four files You receive the following
TRANSFERRING 'RSCS' DISK RESIDENT TEXT ••• Finally, GENERATE builds and loads the RSCS nucleus. You receive the
following messages: DMTINI406R SYSTEM DISK ADDRESS = 195
DKTINI407R REWRITE THE NUCLEUS ? yes DKTINI409R NUCLEUS CYL ADDRESS = 003 (for a 2314 or 3340, or 004 for a 3330 or 3350) DKTINI410R ALSO IPL CYLINDER 0 (YES I NO) ? yes
For this example, respond as shown. You respond with the address of the RSCS system disk, in this case 195. You always respond with the same
address you specified as vaddr2 when you were prompted for link
parameters. The nucleus cylinder address depends on the device type of
the RSCS system disk. You receive the message DKTAXS103E FILE 'spoo1id' REJECTED -- INVALID DESTINATION ADDRESS This message reflects the purging of the RSCS nucleus from the card
reader. At this time you have an RSCS system generated and written to the RSCS system disk, as indicated by the message: DMTREXOOOI RSCS (VER n, LEV n, mm/dd/yy) READY You can now log on the RSCS virtual machine, IPL the RSCS system disk
and start your RSCS operations. See the VM/37Q for
information about using RSCS. 286 IBM VM/370 Planning and System Generation Guide