348 IBM VM/370 Planning and System Generation Guide
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
Previous Page Next Page