Updating CMS If the IPL device you designated is not currently defined, is not
in read/write status, or is an unsupported device type, the message DMSIN1082E IPL DEVICE ERROR - REENTER
is issued. Message DMSINI608R is then reissued. At this time, you
may enter CP mode by pressing the Attention key (or equivalent) ,
then determine the status of the device you designated by entering
the CP command QUERY VIRTUAL cuu
and take the corrective action necessary to define the device for
your virtual machine or to access it in read/write status. You may
reenter CMS by issuing the CP command
BEGIN
Then you must reenter the device address. Once the device address
is accepted, message DMSINI609R is issued. DMS1NI609R NUCLEUS CYL ADDRESS = nnn
Enter the 1-to 3-digit cylinder number (nnn), for the device
entered in response to message DMSINI608R, where the CMS nucleus is
to be written. The number (nnn) must be between 1 and m-1 (where m
equals the number of cylinders on the disk). The number nnn must be entered in decimal. This is the cylinder you reserved when you
formatted the disk with the RECOMP option. In our example, since
the nucleus is written on the last cylinder of MIINT's 390, you
enter: 2
If you do not enter a valid decimal cylinder number, the message INVALID CYLINDER NUMBER - REENTER
is issued. Message DMSIN1609R is reissued and you may enter a
valid cylinder number.
If the cylinder specified is
cylinders already in use on the
file directory, then the message
not greater than the number of
device (as indicated in the master DMSINI083E NUCLEUS WILL OVERLAY FILES - RECOMPUTE is issued. You may respond with a larger cylinder number, or IPL CMS and format the specified IPL device with the RECOMP option. DMS1N1610R ALSO 1PL CYLINDER 01 (YESfNO) The initial IPL text is always written on the same cylinder as the CMS nucleus (the cylinder designated in response to message DMS1NI609F). The initial IPL text is a bootstrap program which
reads the nucleus from the designated cylinder. If it is not also
written on cylinder 0, then you must enter the cylinder number when
subsequent IPL commands are issued for the system being generated. See the IPL command description in the CP iQt Qgneral Your response has the following meaning:
yes Initial 1PL text is written on cylinder 0 as well as on the
cylinder designated in response to message DMSINI609R. no Initial 1PL text is written only on the cylinder designated in
response to message DMSINI609R. 354 IBM VM/370 Planning and System Generation Guide

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