PUT Updates System Program Update Tape (PUT) IBM regularly distributes a system Program Update Tape (PUT) containing
updates to The system PUT updates are cumulative, and contain: • Updated text decks, for a one-to-one replacement of existing text
decks on MAINT's 194 disk. • Update files with UPDATE control statements, and auxiliary control
files to control the application of these updates to the source files
on KAINT's 394 disk. The PTF's and AUX files may be loaded on 294, if you want to apply the updates in conjunction with
local updates.
The second file on the system PUT contains the Memo to Users, which describe in detail all of the updates that are currently available. The Memo to Users also provides step-by-step instructions on how to apply
updates. These files can be loaded on your A-disk and printed, using
the VMSERV EXEC. Program level change service updates involve the use of the VMSERV EXEC, which is the same procedure that you used to install VM/310 during
system generation. The VMSERV EXEC is always provided in the first tape
file of the system PUT, along with the VMFPLC2 module, which is used to
read the tape.
If you have no local updates to apply to any VM/310 modules w you
should follow the instructions in the Memo to Users; this memo always
contains up-to-date documentation on how to use the VMSERV EXEC. The Memo to Users also tells you when you must perform additional steps
before invoking VMSERV. For example, if a macro library has been
updated and your system definition files (DMKRIO, DMKSYS, and so on)
must be reassembled, the user memo tells you to use the VMFASM EXEC to
reassemble the source files.
The VMSERV EXEC builds a new CP, CMS, or RSCS nucleus from the
replacement text decks on the system PUT. If you have local updates to
some system modules, you may not want to use VMSERV. For example, if you have written a local accounting routine and
assembled it into the module DMKACO, and the Memo to Users indicates a
PTF is to be applied to DMKACO, you may want to reassemble the source
module to create a text deck that contains your modification, as well as
the PTF. In this case, you have to load the DMKACO AUXRnO file and the
PTF (DMKACO RnnnnnDK) file from the system PUT. The Memo to Users indicates the location of these files on the tape; remember to use the VMFPLC2 module to load the files, rather than the CMS TAPE command. VMFPLC2 uses a blocking factor of 50:1 thereby better utilizing the
system PUT and insuring maintenance will be contained on one tape.
The procedures that you use next are the same procedures you would
use to apply a local update without the system PUT: you would use VMFASM to assemble the source files for all modules you wish to update, and VMFLOAD to punch a ney CP nucleus. Before you use however, you
want to make sure that you have loaded, from the system PUT, the updated
text files for those modules you are not reassembling.
The procedures for applying updates to VM/310 are described next. Part 5. Updating VM/310 331

332 VM/370 Planning and System Generation Guide