Recommended Procedures You must have the 194 in read/write status because VMFMAC renames the
existing MACLIB and writes a new one. When you issue the command:
vmfmac dmkmac yourown
the EXEC procedure uses the EXEC to rebuild MACLIB. VMPMAC calls the UPDATE command to update each of the macro and copy
files named in the EXEC. In this example, ACCTON COpy is updated with YOUROWN CNTRL as
follows:
1. The IBM updates named in ACCTON AUXRnO, R12263DK and R12576DK, are
applied, in that order.
2. Since no ACCTON AOXLCL file exists, the next entry in the control
file results in no update.
3. The update file ACCTON OPDTLCL is applied.
For each entry in EXEC, checks to see if there are any
updates; if not, then the existing MACRO or COpy file is included in the
new MACLIB without any changes. When the entry for RDEVICE is reached, RDEVICE MACRO is updated with YOOROWN CNTRL as follows:
1. The IBM update named in RDEVICE AOXRnO, R1202QDK, is applied.
2. The update named in RDEVICE AOXLCL, RDEVICE FIXPTF, is applied.
3. Since no RDEVICE OPDTLCL file exists, the last entry in the control
file results in no update being applied.
After all the entries in the list DMKMAC EXEC are processed, V"F"AC erases the existing MACLIB and creates a new D!KMAC MACLIB with
the updated members. An additional file, D8KMAC COPY, is produced; this
file contains a record of the updates that were applied. DKKKAC COpy is
also added to MACLIB, to provide you with a record of changes. NOW, since macro and copy changes affect CP modules, you must
reassemble DMKACO and DMKRIO using the new DMKMAC MACLIB. If you have
no local updates for these assembler source files, you can use the DMKRnO CNTRL file to update them: VMPASM DMKRIO DMKRnO (or DMKRnA) DMKRnO You must be sure that all the current PTFs and auxiliary control files
are available on 29Q. The text decks produced by these assemblies are not uniquely named,
since the update level identifier in DKKRnO is always TEXT. However,
the update log produced by VMFASM does indicate the macro libraries used
in the assembly, so you have a record of update activity. Part 5. Updating V"/370 339

Recommended Procedures VARIATIONS: If you do not want to use VMFMAC to update all of DMKMlC "ACLIB (it is very large, and V"FKAC is not practical if you are
updating only one or two members), you may want to consider manually
updating the macro and copy files using the UPDlTE command and then
using the "lCLIB REP command to update D"KMAC MACLIB. Or, you may want
to use V"FMAC to create a local macro library containing your changes,
and use this library, in addition to DMKMAC "lCLlB, when you reassemble CP modules.
Consider the files:
goto label25 RDEVlCE MACRO goto label25 ACCTON COpy IQU ROW N CNT RL TEXT MACS LCLMAC DKKMAC C"SLIB OSMACRO toe 2 TJPDTtCL LCL AUXLCL TEXT AUXRnO When you issue the command:
vmfmac lclmac yourown
the macro library LCLMAC KACLlB is created, containing only the members RDEVICE and ACCTON. When you use YOUROWN CNTRL with the V"FASH EXEC procedure, LCL"AC KACLIB is searched before DMKMAC MACLIB for the assembly, so your macros are found first.
Using VMFLOAD To Punch a New Nucleus After you have reassembled all the modules that require updating, you
may build a new CP nucleus that contains the updated text decks. In our
example, you also want to include your new module, DMKCMD, in the CP nucleus.
To punch a new nucleus, you use the V"FLOAD program, which requires: • A loadlist file, which must have a filetype of EXEC. It contains the
filenames of the object modules in the order in which they are to
reside in the nucleus. • A control file, from which VMFLOAD can determine the filetypes of the
latest level text decks, so it can punch them.
The files to be used for creating a new CP nucleus are shown in
Figure 38. This nucleus incorporates the updates described in the
preceding pages. The search order is:
191 A R/W 29q B/A RIO 19q CIA RIO 190 S R/O 3QO IBM VM/370 Planning and System Generation Guide