Updatinq eMS FORMATTING A DISK TO TEST THE CMS NUCLEUS Before you can use the minidisk you have available for testing CMS, it
must be formatted with the CMS FORMAT command. For example, to format
the 390 minidisk, you might issue:
format 390 g. NOw, you must reissue the FORMAT command with the RECOMP option, so that
the number of cylinders on the disk is recomputed to reserve space for
the nucleus at the end of the disk. To do this, format the disk with one or two cylinders fewer than it actually has (one cylinder on a 3330 or 3350, two cylinders on a 2314 or 3340). For example, if the 390 minidisk is a 3-cylinder 3330, enter
format 390 g 2 (recomp
The 390 disk is now ready for use as the CMS test nucleus. You should not have to reformat the disk again; you can use it each
time you update CMS. CONSIDERATIONS FOR CREATING A NEW CMS SYSTEM DISK If you want to create a new CMS system disk that contains all the CMS text and MODULE files as well as the CMS nucleus, do the following: • If you are goinq to save this CMS system, be sure that the operands VSYSADR, SYSCYL, and VSYSBES in the NAMESYS macro corresponding to
this system are correct. • After copying all the existing files with filetypes of TEXT and onto the new disk, regenerate any modules that use auxiliary
directories (such as the ASSEMBLE command). Auxiliary directories
are described in the VM/37Q You can use
the CMSGEND EXEC procedure to regenerate the assembler. Some IBM Program Products may also use auxiliary directories.
Punching the eMS Nucleus When you
access to
decks that CMS system these text
prepare to build a new CMS nucleus, be sure that you have
the text decks on the system disk, as well as any updated
you may have created. Since the CMS text decks are on the
disk (usually 190), you should access it so that you have
decks available for the VMFLOAD program:
access 190 a
Be sure that your virtual card punch and reader do not have any files in
them and that your virtual punch is spooled to your virtual reader:
close punch purge punch all
close reader
purge reader all
spool pu nch to * 350 IBM VM/370 Planning and System Generation Guide

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