Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 Updating CMS Updating eMS The procedures for updating source files and macro libraries are the
same as for updating CPa The order of search for CMS updates is:
191 A R/i 193 BIA RIO 190 CIA RIO 393 D/A PIO where 193 con tains PTFS, control files, and user updated TEXT decks and
393 contains the eMS source 190 contains the current eMS system,
including text decks, command modules, and the CMS nucleus. You might use the following steps when you update CMS: 1. Format the minidisk you are going to use to test the CMS nucleus,
if any. Use the VMFLOAD program to punch the updated eMS object modules.
3. Regenerate any disk-resident modules that have been updated. 4. Load the new CMS nucleus.
5. Save the CMSSEG discontiguous shared segment and the new operating system. eMS should be resaved whenever the S-disk is
updated. This will insure that the saved CMS system reflects the
physical system.
The exact steps that you take depend on whether you are testing the CMS nucleus before you load it onto the system disk, whether you are
using shared segments, and so on.
Disks for Updating eMS If you want to keep eMS source files on disk, the minidisk you use must
be at least 145 cylinders for a 2314 (or 2319), 80 cylinders for a 3330 disk, 190 cylinders for a 3340 disk, or 40 cylinders for a 3350 disk.
Then, you should have the eMS source tape mounted and attached to the
virtual machine, and issue the following commands to load the source
programs onto the eMS disk:
vmfplc2 fsf
vmfplc2 load (eof 2)
If you want to test the new eMS nucleus in a virtual machine before
you update the real eMS system, you should have a disk available for a
copy of the nucleus. The configuration shown for MAINT in "A Virtual Machine for Updating VM/370" shows a 6-cylinder minidisk at virtual
address 390 for testing the eMS nucleus. You can test updated disk-resident CMS modules on your A-disk before
moving them to the eMS system disk (190). Part 5. Updating VM/370 349

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