April 1, 1981 Updating CMS If you do not enter "yes" or "no," the message DMSINI081E INVALID REPLY - ANSWER "YES" OR "NO" is issued. Message DMSINI610R is reissued so that you can
enter a valid response.
If your response is valid, message DMSINI611R is issued. DMSINI611R VERSION IDENTIFICATION =
Enter up to 32 bytes of information, including blanks, to
specifically identify the version and· level of CMS; this
information is printed each time you IPL the crtSsystem now being
generated. The default identification (specified by a carrier
return) is: CMS VERSION n.n -mm/dd/yy
where n.n is the version and level of CMS, and mm/dd/yy is the
month, day and year the CMS nucleus was created. DMSINI612R INSTALLATION HEADING =
Enter up to 64 bytes of information, including blanks, to serve as
an installation standard beading at the beginning of each output
file. The default heading (specified by a carrier return) is: CONVERSATIONAL MONITOR SYSTEM The nucleus is then written on the specified disk cylirider and the
version identification is displayed, indicating that the CMS system is
loaded successfully and is ready to accept CMS commands. You can use this copy of CMS to test updates and changes, including
changes to CMS modules that you may have made with the CMSGEND EXEC. Before you test the CMS system, you can create a disk file from the CMS nucleus and the nucleus load map:
spool rdr nohold
close prt
close rdr PRT FILE 0342 TO MAINT COpy 01 NOROLD Now you can read a copy of the CMS nucleus onto disk:
read cmsnuc nucleus a1
and read a copy of the CMS load map:
read cmsnuc loadmap a1 RECORD LENGTH IS '132' BYTES. You now have two CMS files on your 191 disk: CMSNUC NUCLEUS, which
contains the eMS nucleus created above, and CMSNUC LOADMAP, the load map
for this nucleus.
After you test the new eMS nucleus on 390, and you are satisfied that
it is all right, you can use the disk file to create the new nucleus on
the system disk (190). Part 5. Updating VM/370 355

Updating CMS To regenerate a nucleus which exists as a disk file (CMSNUC NUCLEUS, for example), issue the following commands:
spool pun to *
punch cmsnuc nucleus a1 (noheader)
ipl OOc You may then answer the IPL messages previously described. This
time, you specify the IPL address as 190 instead of 390, and enter the
correct cylinder for your system disk. Now you can go on to save the CMSSEG and the eMS saved system, if you wish. If a named saved system has been built from this CMS system disk,
it must be resaved because the SSTAT is recreated only when the disk is
loaded (for example 190). Appendix C details what must be regenerated
for changes in any CMS text file. Saving CMSSEG and the CMS System If your system has entries in the system name table (DMKSNTBL) for a CMSSEG discontiguous segment and a named CMS, you should now save these
system names. To do this, first be sure that you have defined virtual
machine storage to a value above the location of CMSSEG and the loader
tables, for example 2M.
Then, you can IPL CMS and issue the CMSXGEN command to save the CHSSEG segment:
ipl 190 parm seg=null
(null line) Y (19E) RIO R;
access 190 b/a
R;
cmsxgen 100000 where 100000 is the hexadecimal address where the segment is loaded.
This number must correspond to the starting page number specified in the NAMESYS macro for the CMSSEG saved system name. CMSXGEND generates a LOAD MAP on OOE which will appear in your reader and is required by IPCS. When the CMSXGEN procedure is completed, you should IPL the CMS system disk again, and issue the CP SAVESYS command immediately, before
pressinq a carriage return to complete the IPL:
ipl 190 savesys cms
In this example, CMS is the name of the saved CMS system. If you have
specified another name for the saved CMS system, you should specify that
name when you issue the SAVESYS command. SAVESYS is a CP privilege
class E command; it allows you to write on the CP system residence
volume. NOw, the saved portion of CMS may be shared among many users, who can
load CMS by referrinq to its saved name, for example
ipl ems
When you IPt a saved CMS system, CMS operates as if an IPL specific device had occurred, with the single exception that
directory for the system disk is part of the nucleus.
356 IBM VM/370 Planning and System Generation Guide
of a
the