Upda ting CMS Then you can issue the VMFLOAD command specifying the CMS loadlist EXEC filename and the control file filename: VMFLOAD CMSLOAD DMSRnO In this example: the system-supplied CMSLOAD EXEC and DMSRnO CNTRL files
are used to punch a new CMS nucleus. When you receive the messages SYSTEM LOAD DECK COMPLETE PUN FILE 0353 TO MAINT COpy 01 NOHOLD a new copy of the CMS nucleus is available in your card reader. Before
you go on to load the new nucleus, you may want to regenerate any CMS MODULE files that have been updated. This procedure is described next.
To determine whether an update requires module regeneration see
"Appendix C: CP/CMS Regeneration Requirement." If you do not need to
regenerate any modules, see "Loading a CMS Nucleus."
Creating CMS Disk-Resident Modules The CMSGEND EXEC procedure creates CMS disk-resident command modules
from CMS text files. CMSGEND is invoked by specifying the filename of
the module to be generated. For example, if there is a change to the
text file DMSACF, you must generate a new ACCESS MODULE. cmsgend access CMSGEND will rename any existing file from 'ACCESS MODULE A2' to 'ACCESS MODOLD Al'. After an existing file of 'ACCESS MODOLD All is
erased CMSGEND then loads the text files that comprise the ACCESS command module and generates a new ACCESS module A2. When you use CMSGEND, you must access the S-disk as your read/write A-disk, and have all pertinent text files available: The text files
must have a filetype of TEXT; thus, if you have updated an object module
using VMFASM, and the most recent object file has a filetype such as TXTLOCAL, you must rename it to a filetype of TEXT. (Note that if there
is currently a text file on the system disk, you may want to rename it
also, so that your updated text file, on some other disk, is the one
tha t is loaded.) CMSGEND displays status messages as it executes. For example:
cmsgend access
*** CURRENT STATUS: FILE' ACCESS MODULE A21 DOES NOT EXIST FILE I ACCESS MODOLD Al' DOES NOT EXIST *** LOADING: INVALID CARD -
* Cl1SL IB l1ACLIB INVALID CARD -
* DOSMACRO MAC LIB INVALID CARD -* D!!SACC ASSEMBLE ACCESS SD OOEOOO INVALID CARD -* CMSLIB MACLIB READFST SD OOEBCO DMSACM SD 00EF10 READMFD 00EF10
A2 RnM190 12/04/75
A2 RnM190 10/16/75 Al RnM303 12/03/75
A2 RnM196 10/16/75 04:20 23: 19 04:02 23: 19
Part 5. Updating VM/370 351

Updating CMS INVALID INVALID DMSAlU RELUFD SORTFST END$RELU CARD - * CARD - * SD 00F4A8 00F4 A8 00F716 00FF38 *** RESULTS: OSMACRO MACLIB OSMACR01 MACLIB S2 RnM290 10/16/75 S2 RnM290 10/16/75 , ACCESS MODULE A2' CREATED FROM TEXT DECK ( S ) DMSACC DMSACF DMSACM DMSALU WITH ATTRIBUTES TRANS SYSTEM NOMAP 22:47
22:49
Since CMSGEND renames the existing module, users who are currently
using the CMS system disk are unaffected by the regeneration procedure.
This is because the SSTAT (system status table) of the CMS system disk
is still pointing to the old (renamed) module. Whenever 190 is
subsequently IPLed, the SSTAT points to the updated modules, so that the
old module can be erased.
Loading a CiviS Nucieus
When you are ready to load the CMS nucleus, you should plan ahead for
two si tuat ions.
If you are going to test the CMS nucleus on a minidisk other than 190 (we are using 390 in this example), you may want to save the nucleus
reader file so that you do not have to repeat the VMFlOAD procedure if
the nucleus tests out all right. To do this, issue the command:
spool reader hold You may also want to issue the command
spool printer to *
so that the nucleus load map is routed to your card reader, instead of
the virtual printer.
If your CMS system uses the CMSSEG discontiguous saved segment, you
should anticipate that it may not be compatible with the new CMS nucleus. Later, you will want to use the CMSXGEN procedure to save the
segment, but for testing purposes, you do not need it. Therefore, to
prevent CMS from attempting to attach CMSSEG after IPL, you can define
your virtual storage to 2M: define storage 2m
Now you can issue the IPL command to load the CMS nucleus:
ipl clear
During the 1PL sequence, you must respond to the following messages. DMSINI606R SYSTEM DISK ADDRESS = cuu
Enter the device address (cuu) of the system disk (S-disk). This
is usually 190. On this disk CMS expects to find all CMS system
information and programs not contained within the CMS nucleus, such
as the disk-resident command modules. If the eMS nucleus is written
on this disk, then cuu is also the IPL device address.
352 IBM VM/370 Planning and System Generation Guide