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
VMFLOAD 1. The distributed system uses the following loadlists: Lo.sdlist APLOAD APVRLOAD CPLOAD EXEC VRLOAD EXEC CMSLO AD EXEC DMTLOAD EXEC CP nucleus without V=R for the attached processor CP nucleus with V=R for the attached processor CP nucleus without V=R for uniprocessor CP nucleus with V=R for uniprocessor CMS nucleus
RSCS nucleus
For example, to punch a new CP nucleus with the distributed
loadlist
vmfload cpload DKKRnO The GENERATE EXEC and the VMSERV EXEC uses VMFLOAD to generate a
new CP nucleus.
2. After you have punched a new nucleus with VMFLOAD, you can either
move the nucleus to tape, using the MOVEFILE command, or, if the
nucleus is in your virtual card reader, you can IPL it:
ipl OOc When you IPL the virtual card reader, the loade r is read first, and
it loads the rest of the object modules. If the loader is
successful, the nucleus is written on disk, and the load map is
spooled to the virtual printer. If you want to preserve a disk
copy of the load map, you should spool your printer to your virtual
card reader, then read the file onto disk. SYSTEM LOAD DECK COMPLETE This message is displayed when all the files in the loadlist have been
punched. INSUFFICIENT OR INVALID ARGUMENTS The command line was incorrectly entered. NO CONT ROL FIL E The control file could not be located. ERROR IN CONTROL FILE
The control file contains an invalid record. NO LOAD LIST
The loadlist could not be located. ERROR IN LOAD LIST
The loadlist contains an invalid record.
fn ft NOT FOUN D
No text file was found. ERROR ON PUNCH An error occurred punching a file. Part 5. Updating V8/370 389
Previous Page Next Page