Updating RSCS Updating RSCS The same procedure used to update CP and CMS can be used to update RSCS. However, unlike CP and CKS, RSCS can test the system that is built; it
does not need to test a duplicate copy of the system that is built.
Again, the KAINT virtual machine can be used to do the updating. You should link to the RSCS virtual machine's 191 minidisk as your 195 and
access it as your A-disk.
The order of search for updating is:
195 A R/i 194 B/A RIO 190 S R/O To build a new RSCS nucleus, you must create a new RSCS system disk
and generate a new RSCS nucleus.
Creating an RSCS System Disk Use the following procedure to create a new RSCS system disk:
1. tog on as KAINT. 2. IPt 190. 3. tink to the mini disk that you want to contain the new RSCS nucleus
as lq5 in write status and access it as your A-disk.
4. Issue the CMS FORKAT command to format that minidisk.
5. Issue the eMS command with the RECOMP option to format the same minidisk with one or two cylinders less than the total number
of cylinders on the disk (one less on a 3330 or 3350, two less on a
2314 or 3340). The last cylinders are used for the RSCS nucleus.
6. If you wish to change the RSCS configuration, re-create the AXSLINKS, tAXLINES, and TAGQUEUE COpy files and create a new DKTLOC macro library. See "Part 3. Generating VM/370 (CP, CMS, RSCS and IPCS) .n 1. Generate a new RSCS nucleus using the commands described in the
following section.
Generating the RSCS Nucleus 1. Load the RSCS files onto the CP system disk (the 194 minidisk
belonging to KAINT) if they are not already there.
2. Access the KAINT 194 disk as an extension of the RSCS system disk.
access 194 b/a Part 5. Updating VM/370 363

Updating RSCS If you want to apply your own updates, they should be on the
294 disk. Then disk access should be:
access 294 b/a
access 194 cia 3. Assemble the RSCS configuration table module, DMTSYS, using the VMFASM EXEC procedure. The control file DMTRnO CNTRL identifies DMTLOC as the macro library. VMFASM DMTSYS DMTRnOl If an error occurs due to an incorrectly coded macro, correct the
macro and restart by generating a new DMTLOC macro library. If you do not have enough disk space to assemble, acquire
additional T-disk space.
4. Close and clear the punch and reader. Spool the punch to your
virtual card reader. Use the VMFLOAD EXEC procedure to punch the RSCS nucleus. The loadlist EXEC, DMTLOAD, contains the filenames
of all the RSCS TEXT modules.
close pun
close rdr
purge rdr all
purge pun all
spool pu n to *
vmfload dmtload DMTRnO SYSTEM LOAD DECK COMPLETE PUN FILE spoolid TO userid
5. Copy the RSCS supervisor text decks, DMTAXS and DMTLAX, from the MAINT 194 disk to your RSCS system disk.
6.
copyfile dmtaxs text b1 = = a1 (replace olddate
copyfile dmtlax text b1 = = a1 (replace olddate
Copy the required line driver TEXT from the MAINT 194 disk to the RSCS disk can now be released and detached.
decks, DMTNPT system disk.
copyfile dmtnpt text b1 = = a1 (replace olddate
copyfile dmtsml text b1 = = a1 (replace olddate
release 194
detach 194 DEV 194 DETACHED
and/or DMTSML, The MAINT 194 7. IPL your card reader which contains the RSCS nucleus A series of
prompting messages requests information relative to the physical
location and disk address of the RSCS nucleus. Answer them as
shown.
ipl c DMTINI406R SYSTEM DISK ADDRESS = 195 DMTINI407R REWRITE THE NUCLEUS ? yes DMTINI409R NUCLEUS CYL ADDRESS = 003 (for 2314 or 3340, or 004 for 3330 or 3350) DMTINI410R ALSO IPL CYLINDER 0 ? yes IDMTRnO may be DMTR40, DMTR50, DMTR60 and so forth, depending on the
release leve 1.
364 IBM VM/370 Planning and System Generation Guide