.n.t' .... I, lJU 1
Recommended procedures
r--- '!QURQ!H! CNT]1 TEXT MACS DHKMAC CMSLIB OSMACRO LOC2 UPDTLCI LCL AUXLCL TEXT AUXRnO &1 &2 ABEND MACRO &1 &2 ACCTOFF COPY &1 &2 ACCTON COPY &1 &2 RDEVICE MACRO FIXPTF 194 (A-disk) DMKMAC l"IACLIB DMKMAC COpy 294 (C-disk) YOUROWN DMKRnO ACCTON ACCTON ACCTON RDEVICE RDEVICE RDEVICE CNTRL CNTRL ATJXFnO I R12576DK I R12263DKI AIJXRnO I R12024DKI FIXPTF I '--------- Figure 37. Files for VMFMAC lCCTON AUXRn.Q R12567DK
R12263DK R12024DK !f.:CTON ACCTON ACCTON RDEVICE R12263DK UPDTLCL FIXPTF 191 (B-disk) DMKMAC EXEC RDEVICE AUXLCL ACCTON UPDTLCL 394 (D-disk) ACCTON ACCTOFF ACCTON COpy COpy UPDTLCL 338 Vr/370 Planninq and System Generation Guide

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