RSCS Generation Procedure You can use a 2314, 3330, 3340, or 3350 disk as the RSCS system disk.
The RSCS nucleus occupies two cylinders on a 2314 or 3340, and one
cylinder on a 3330 or 3350 disk.
The following system generation procedure for RSCS assumes you have
the "AINT virtual machine supplied with the V8/370 starter system in
your VM/370 directory. STEP 1. LOG ON AS MAINT AND IPL CMS To build the RSCS nucleus, you must log on the software system support
virtual machine (MAINT) and IPL the CMS system.
logon maint cpcms
ipl 190 STEP 2. APPLY THE RSCS UPDATES FROM THE VM/370 PROGRAM UPDATE TAPE Press the carriage return to complete IPL. Mount the system PUT and attach to MAINT as 181. Service for RSCS is
initiated by issuing the commands:
access 191 c
vmserv restart 5749010 rscs noipl
The keyword "rscs" allows the procedure to load wha t is required
(from the system PUT) for RSCS. You are prompted for 'various information concerning your system
(including staging area addresses and the service that you want
applied). Respond 'NO' when asked if you wish service for IPCS. Service for IPCS has already been applied. The user memOs 'and the PUT document should be referenced concerning the application of service with
the VMSERV EXEC. After service has been applied, you will receive this message: DO YOU WISH TO BUILD RSCS SYSTEM -- RESPOND (YESINO) You must respond "no". STEP 3. FORMAT THE RSCS SYSTEM DISK You must link to the RSCS system disk and format it. If you used the VM/370 directory entry for the RSCS virtual machine supplied with the
starter system, your LINK command is:
link to rscs 191 as 195 w pass= password
This makes the Rses system disk (address 191 in the Rses virtual
machine) available at virtual address 195 in the MAINT virtual machine.
Remember the address you specify for MAINT. You must use this same
virtual address later in the RSCS generation procedure (you use 195 when
you invoke GENERATE again to build the RSCS nucleus in Step 7). Then,
format the RSCS system disk.
format 195 a Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 283

RSCS Generation Procedure Next, format the RSCS system disk again. You must use the recompute
function of the FORMAT command to make the last cylinders of the RSCS system disk unavailable to the CMS file system. The last one or two
cylinders contain the RSCS nucleus. If the RSCS system disk is a 2314
or 3340, the last two cylinders are needed for the nucleus. For a 3330 or 3350, only the last cylinder is needed. The FORMAT command for a
2314 or 3340 RSCS system disk is:
format 195 a 3 (recomp
The FORMAT command for a 3330 or 3350 RSCS system disk is:
format 195 a 4 (recomp STEP 4. CREATE THE COpy FILES THAT DEFINE YOUR RSCS SYSTEM the Editor to AXSLINKS, LAXLINES, and TAGQUEUE. The macros you need to
these files are described in a preceding section, "Defining System." YOu need: include in Your RSCS When you code the GENLINK macros for the AXSLINKS COpy file, you may
include GENLINK macros with no operands. These macros reserve extra
link table entries which can be defined later with the RSCS DEFINE
command. Also, the local linkid (local location ID) must be specified
on the first GENLINK macro in the AXSLINKS file. When you code the GENTAGQ macro for the TAGQUEUE COPY file, remember
that the total number of tag slots must be equal to or greater than the
number of holdslots defined either explicitly or implicitly in the AXSLINKS COpy file.
The following example shows the creation of the AXSLINKS, LAXLINES, and TAGQUEUE COPY files:
edit axslinks copy NEW FILE:
EDIT:
input INPUT: *copy axslinks
genlink id=mylocid,type=dmtnpt
genlink id=newyork,class=a,keep=2,line=079,task=m1,type=dmtnpt
genlink id=sanfran,class=a,keep=2,line=07a,task=m2,type=dmtsml
genlink id=london,class=a,keep=4,line=07b,type=dmtsml
genlink
genlink
genlink
EDIT:
file
R;
284 IBM VM/370 Planning and System Generation Guide