Recommended Procedures Since the program uses your virtual card reader and virtual
punch, you must be sure there are no files in either of these devices
before you begin. You can issue the commands:
close punch
purge punch all
close reader
purge reader all
and you must be sure to spool your virtual punch to your own card
reader:
spool punch * When you issue the command
vmfload yourload yourown YOTJFI.nln F.Y'F.r +0 ;'p+prm;np +.0 Tn onr
example, EXEC is identical to the distributed EXEC file,
except that you have added an entry for your module DMKCMD. uses the loadlist to establish the filenames of modules to be
punched, and it punches them in the order they appear in the loadlist.
Thus, DMKLDOOE LOADER is punched first. If a filename and a filetype
are specified in the loadlist, VMFLOAD punches the file. When a filetype is not specified (as is usually the case), VMFLOAD uses the update level identifier field in the control file to determine
the filetype. Since control files are structured so that the most
recent update is named at the top of the file, VMFLOAD begins reading at
the top of the file. Since the next entry in the loadlist, DMKPSA, does not provide a
filetype, VMFLOAD looks at the control file. In our example, since the
update level identifier for the first update record is LOC2, VMFLOAD searches for the file DMKPSA TXTLOC2. Since this file does not exist, VMFLOAD looks at the next lowest identifier: LCL. It searches for DMKPSA TXTLCL. Since this file does not exist, it reads the next lowest
identifier, TEXT. DMKPSA TEXT exists on the 194, so it is punched.
Then VMFLOAD returns to the loadlist EXEC and repeats the same procedure
for the next entry. You can see that when VMFLOAD reaches the entry for DMKCFC in the
loadlist, it locates the file DMKCFC TXTLCL, the DMKCFC module that
contains your updates. Notice that although there are copies of DMKCFC TXTLCL on both the A-disk and the B-disk, V"FLOAD punches the one on the
A-disk, since it uses the standard CMS order of search.
The loading process continues
loadlist EXEC file. When all of
receive the messages SYSTEM LOAD DECK COMPLETE in this way until the
the modules have been PUN FILE 0821 TO MAINT COpy 01 NOHOLD 342 IBM VM/370 Planning and System Generation Guide
end of the
punched, you

These messages indicate that a
card reader. This CP nucleus
disk, except that the files: DMKCFC TXTLCL DMKSCN TXTLOC2 copy of the new
contains all the
Recommended Procedures
C P n uc Ie us is
text decks on
in your
the 19q have been punched instead of their TEXT counterparts; the files DMKACO TEXT A DMKRIO TEXT A
have been punched instead of their counterparts on the C-disk; and your
new command module, DMKCMD, is included. Once the new nucleus has been punched into your card reader, you can load it and test it. considerations for loading and testing each of the VM/37Q components are discussed separately in the following pages. Part 5. Updating VM/370 3q3