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

Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 starter Systems
Then CMSXGEN loads all the text files needed to create the CMS shared
segment, starting at the address specified on the command line. If
there are any unresolved external references, the CMSXGEN command
terminates with the message: DMSCMS111E CMSXGEN FAILED DUE TO LOAD ERRORS To ensure storaqe protection for the named segment, CMSXGEN assigns a
storage key of X'D' (decimal 13) to the segment. CMSXGEN invokes the SETKEY command: SETKEY 13 segmentname
If any errors occur during the SETKEY command execution, the message: DMSCMS412S CMSXGEN FAILED DUE TO SETKEY ERROR is issued and
occurred during SAVESYS command. CMSXGEN execution is terminated. If no errors have CMSXGEN processing, the segment is saved via the CP If an error occurs at this point, the message: DMSCMS141S CMSXGEN FAILED DUE TO SAVESYS ERRORS is issued and CMSXGEN execution is terminated. Otherwise, the segment
is successfully saved, the load map is printed, and the completion
message: DMSCMS7151 CMSXGEN COMPLETE is issued. SAVING THE CMS SYSTEM Now, you should redefine your virtual storage to 960K and IPL CMS: define storage 960K ipl 190 -or- ipl 190 parm seg=segname Where segname is the shared segment created here, if not named CMSSEG. When the terminal unlocks, do not press 'ENTER', but immediately issue
the command:
savesys ems I Then press 'ENTER'. If CMS is successfully saved, the message
hh:mm:ss SYSTEM SAVED CMS VERSION n.n -mm/dd/yy hh:mm
is displayed. Your CMS system is now saved; you can issue IPL CMS instead of 1PL 190, when you wish to run CMS. If you named your CMS system something other than CMS, such as CMS1, the entry you made in the system name table would be for eMS1; you would have to save CMS1 (SAVESYS CMS1) and then you could 1PL CMS1. For more
information about how to save CMS, see the VMLJ70 or the "Saved Systems" section of this manual. At th is point, llse the Installation Verification Procedure (IVP) to
test the new system. Log off the userid MAINT and log on aqain as the
userid OPERATOR, using the password OPERATOR. The IVP is described
la ter in Part 3. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 259