Paqe of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837
Recommended Procedures
When all the updates have been applied, VMFASM calls the assembler to
assemble the updated source file, which has a temporary name of $DMKCFC. When the assembly is complete, VMFASM uses the update level identifier
of the most recent update that was found and applied by the UPDATE command to rename the text file produced by the assembly: in this
example, the output file is named DMKCFC TXTLCL. The updated source file created by the UPDATE command is erased.
The UPDATES file produced by a multilevel update is concatenated into
the output text deck so that when this object code is loaded,
information pertaining to its creation is contained in the load map.
Next, issue the VMFASM command to assemble DMKSCN ASSEMBLE: vmfasm dmkscn your own
The UPDATE command searches for files named DMKSCN AUXRnO and DMKSCN AUXLCL. Neither of these files exists; however, DMKSCN UPDTLCL (the
local update you created) does exist. This update is applied, the
source file is reassembled, and the output file is named DMKSCN TXTLOC2. The updated source file by the UPDATE command is erased. The UPDATES file produced by a multilevel update is concatenated into the
output text deck, so that when this object code is loaded, information
pertaininq to its creation is contained in the load map. Note: creates (or replaces, if it already exists) a temporary
workfile with a fileid of 'assemble-filename control-filename A1'. This
file is erased when VMFASM is finished with it. If the user already has
a file with this name it should be renamed using the CMS RENAME command,
to prevent its loss. For example, if you enter
vmfasm dmkrcf yourown
the work file is named DMKRCF YOUROWN A1. If the object modules created have a filetype of "TXTxxxx" and are
to be used with one of the GEN EXECs (CMSGEND, DOSGEN, VSAMGEN, etc.),
they must be renamed with a filetype of "TEXT". Using VMFMAC To Update iViacro Libraries
The VMFMAC EXEC procedure is similar
except that it is specifically designed
must provide:
to the VMFASM EXEC procedure,
to update macro libraries. You • Update files, with UPDATE control statements to modify the macro
library members. You must also have available any IBM PTFs that have
been distributed for the macro library. • A control file that lists update files or auxiliary control files to
be updated. • An EXEC file listing the names of the members to be included in the
macro lil-rary. The files to be used for updatinq RDEVICE and ACCTON COpy are shown
in Fiqure 37. In addition to these disKs, you should have access to the
source COpy and MACRO files on MAINT's 394 and the CMS system disk. The
search order should be:
194 A 'R/W 191 BIA RIO 294 CIA RIO 394 D/A RIO 190 S RIO Part 5. Updating VM/370 337

.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