VMFLOAD VMFLOAD Use the VMFLOAD EXEC procedure to generate a new CP, CMS, or RSCS nucleus. The VMFLOAD program uses two files, a loadlist EXEC file and a
control file, to produce a punch file that has several object modules. VMFLOAD requires a virtual machine with 320K. The format of the VMFLOAD command is:
r I VMFLOAD I loadlist ctlfile
L
loadlist is the filename of an EXEC file that contains the names of
object modules in the order in which they are to reside in the
complete load file for the nucleus. For example: &CONTROL OFF & 1 &2 fn [ft]
& 1 &2 fn [ft]
where fn and optionally ft, are the filename and filetype of
an object module to be punched. The object modules are
punched in the order specified, beginning at the.top of the
loadlist EXEC. If a filetype is specified, VMFLOAD searches
for that specific file, and, if it finds it, punches it
without a header card.
If the file type is not specified in the loadlist, VMFLOAD uses
the control file to determine which object module is the level object module available. VMFLOAD searches the
control file from top to bottom. When it finds the
appropriate object module, VMFLOAD punches it.
ctlfile is the filename of the control file. This is usually the same
control file used to apply updates to modules via the V!FAS! or UPDATE commands. This file identifies the highest level
object module available, if the filetype is not specified in
the loadlist.
1. Before the the files specified in the loadlist are punched, VMFLOAD issues a SPOOL PCH CONT command to ensure that the punched files
appear as one deck. You may wish to specify SPOOL PCH TO userid
before you invoke VMFLOAD to transfer the punched output as a file
to your own (or another) virtual machine as a reader file. If you
want to perform any additional controls, you should write an EXEC procedure to perform the control and invoke VMFlOAD from that EXEC procedure.
2. For each entry in the loadlist that VMFlOAD searches the control file to
object module.
does not specify a filetype
determine the filetype of the Part 5. Updating VM/370 387

VMFLOAD 3.
The filetypes are based on the update level identifiers in the
control file. These are the identifiers used by the VMFASM to
assign filetypes to object decks. Remember that updates applied to
source files are applied from the bottom of the file towards the
top. Therefore, VMPLOAD searches the control file from the top
towards the bottom to locate the most recent update level.
For example, if a control file contains the records and control
file, you would issue: TEXT MACS DMKMAC LOCAL FIXl SPEC A UX 11 1 1 PTF R12765DK IBMl AUXRnO Then for each entry in the loadlist, the VMFLOAD search order is: • fn TXTLOCAL • fn 'f'X'f'51'EC • fn TXTIBM 1 As soon as VMFLOAD locates a file, it punches it, then continues
processing the next entry in the loadlist. If none of the above
filetypes exist for the loadlist entry, VMFLOAD searches for
filename TEXT. If there is no TEXT file, VMFLOAD displays a
message and continues processing with the next entry in the
loadlist. VMFLOAD ignores records that have an update level identifier
of PTF, and so searches for the next lowest level identifier when
determining the filetypes of object modules to punch. When all the object modules are punched, VMFLOAD issues the
commands SPOOL PUNCH NOCONT CLOSE PUNCH If you issued the command
spool punch to *
prior to invoking VMFLOAD, the completed load deck is placed in
your virtual card reader.
loadlist EXEC contains the filenames, and optionally filetypes,
of the object modules to be punched. DMKLDOOE LOADER the loader, which should be the 1st entry in the
loadlist EXEC object modules with filetypes of TEXT or TXTxxxxx, where xxxxx is
the update level identifier in a control file, used by VMFASM to
name the object module.
load deck punched to your virtual machine 38R IBM V"/370 Planning and System Generation Guide