Starter Systems VMSERV remaps the PUT because the 191 disk of MAINT is new and does not
contain the previously created map. 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 want
service for RSCS. Service for RSCS is applied when RSCS is installed.
The "Memo to Users" and the PUT document should be referenced concerning
the application of service with the VMSERV EXEC.
Any further SCP service not applied in Step 13 is applied at this
time (including service for CMS and IPCS). VMSERV prompts you with: DO YOU WISH TO CONTINUE APPLYING SERVICE? (YESINO) Respond "No". The following messages are displayed:
hh:mm:ss NO FILES PURGED SYSTEM LOAD DECK COMPLETE hh:mm:ss PUN FILE nnnn TO MAINT COpy 01 NOHOLD hh:mm:ss REWIND COMPLETE WHEN THE NEW CMS SYSTEM IS BUILT ISSUE: I CLOSE PRT' ...... (PRINTS THE LOAD MAP) At this point, the CMS nucleus is loaded via IPL from your virtual
card reader. When the new CMS nucleus is loaded, control passes to
module DMSINI, which then prompts you to specify where to save the
nucleus, what your CMS system residence address is to be, and so forth.
In the following example, the 190 you enter is the 190 minidisk that
belongs to the user MAINT; it is equivalent to the 190 minidisk that
belongs to CPGEN on the starter system. For instance, you specify
cylinder 108 as the nucleus cylinder address for a 23141 when responding
to message DMSINI609R. The 19E you enter is the address of a user disk that may contain any
user-written programs that run under CMS. If you enter a null line when prompted for version identification and
installation heading, CMS uses its own defaults. DMSINI606R SYSTEM DISK ADDRESS = 190 DMSINI615R Y-DISK ADDRESS = 1ge DMSINI607R REWRITE THE NUCLEUS ? yes DMSINI608R IPL DEVICE ADDRESS = 190 DMSINI609R NUCLEUS CYL ADDRESS = nucleus cylinder address1 DMSINI610R ALSO IPL CYLINDER 0 ? yes DMSINI611R VERSION IDENTIFICATION = DMSINI612R INSTALLATION HEADING = CMS V n.n -mm/dd/yy press ENTER When the procedure completes its execution, the CMS system residence
volume is updated with the most current object modules (text decks) and
load modules, and the new CMS nucleus is written on the CMS system
residence volume.
If there are any updates for the system assembler on the PUT, the
procedure updates that program and creates the corresponding new
auxiliary directory.
1The nucleus will reside on the last cylinder(s) of the minidisk 190. See the notes in the figures showing the allocation of the starter
system volumes when the starter system directory is used to determine
which nucleus cylinder address to specify. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 251

starter Systems
If there are any updates to the EREP package on the PUT, an updated
ERPTFLIB TXTLIB is loaded onto the CMS system disk. The CPEREP EXEC supplied with the system contains a statement: GLOBAL TXTLIB ERPTFLIB EREPLIB which ensures that the ERPTFLIB is searched first and the most current
level of each individual EREP module is used. Step 24. Save eMS If you used the sample DMKSNT and DMKSYS files supplied with the starter
system; and the sample allocations shown in Step 2, you can now save
your CMS system.
To save the CMS system, load it and then save it as soon after
loading as is possible. If you have defined your virtual machine as 2M before, issue the command:
define storage 2M Then IPL CMS: ipl 190 parm seg=null
and press the carriage return to complete the IPL. GENERATING THE CMSSEG SEGMENT If you have defined a CMSSEG discontiguous saved segment in your DMKSNT (or used the DMKSNT supplied with the starter system), access
your system disk as an extension and create one at this time by issuing:
access 190 B/A cmsxgen 100000 where 100000 is the hexadecimal load address of the CMSSEG segment; this
location must correspond to the CMSSEG page number in your DMKSNT entries. Figure 31 shows where the CMS segment will be loaded.
The segment name defaults to CMSSEG, but you can load an alternate by
specifying the alternate's name (for example, cmsxgen 100000 cmsseg1).
There must be an entry in the system name table for the alternate. CMSXGEN checks that the address specified is greater than or equal to X'20000' and less than 16M. It also checks that only valid characters
are specified. If an error is detected, the message DMSCMS095E INVALID ADDRESS 'address'
is issued and command execution is terminated.
Next, CMSXGEN checks that a read/write A-disk is accessed. If an A-disk is not available it issues the following error messaqe and
command execution is terminated. DMSCMS064E NO READ/WRITE A-DISK ACCESSED 258 IBM VM/370 Planning and System Generation Guide