(real I/O configuration macros)
:READ DMKSYS ASSEMBLE (CP system control macros)
GENERATE
where fn is the filename of your VM/370 directory. GENERATE
prompts you for the filename of your directory. OptionallYr you can place new versions of DMKFCB and/or DMKSNT in your
card reader following the DMKSYS macros:
:READ DMKFCB ASSEMBLE (forms control buffer load macros)
:READ DMKSNT ASSEMBLE (system name table macros)
GENERATE reads the files in the reader. It invokes the
Directory program to build the VM/370 directory and invokes
the VMFASM EXEC procedure to assemble all the ASSEMBLE files in the reader. VMFASM is invoked with the current IBM-supplied
control file to ensure that the proper macro libraries are
available when the modules are assembled and to assign the
correct filetype. Then, GENERATE invokes the VMFLOAD EXEC procedure to place all the CP object modules on tape in the
correct order. If an error is detected during any of these
processing steps, GENERATE terminates at the end of that step.
For a CP nucleus without a virtual=real area, GENERATE
loads the tape, thus loading the newly generated CP nucleus.
For a CP nucleus with a virtual=real area, GENERATE writes the
nucleus to tape and exits. You are instructed to shutdown the
system. Then you can IPL the tape on a real machine or on a
virtual machine that has enough virtual storage. The "Specifying a Virtual=Real Machine" section of Part 1 tells
you how much virtual storage you need.
DIRECT (ONLY] builds a new VM/370 directory.
If you do not specify ONLY, GENERATE executes exactly as if
you specified GENERATE VM370. If you specify ONLY, only the VM/370 directory is built. You must place the Directory program control statements in your
virtual card reader at address OOC, as follows:
:READ fn DIRECT
(Directory program control statements)
where fn is the filename of your VM/370 directory. GENERATE
prompts you for the filename of your directory file. DMKRIO (ONLY] assembles the real I/O configuration file (DMKRIO) by invoking VMFASM. If you do not specify ONLY, the GENERATE EXEC procedure
executes just as if you specified GENERATE VM370 (except that
it does not build a new VM/370 directory). Consequently, you
should follow the directions for issuing GENERATE VM370, except do not place the Directory program control statement
(nor the corresponding :READ statement) in your card reader.
If you do specify ONLY, only the DMKRIO module is assembled. Part 5. Updating VM/370 381

GENERATE You must place the real I/O configuration macros in your
virtual card reader at OOC, as follows:
:READ DMKRIO ASSEMBLE (real I/O configuration macros) DMKSYS [ONLY] assembles the CP system control file (DMKSYS) by invoking VMFASM. If you do not specify ONLY, the GENERATE EXEC procedure
executes just as if you specified GENERATE VM370 (except that
it does not build a new VM/370 directory and does not assemble
a new DMKRIO). Consequently, you should follow the directions
for issuing GENERATE VM370, except do not place the Directory
program control statements or real I/O configuration macros
(nor their corresponding :READ statements) in your card
reader.
If you do specify ONLY, only the DMKSYS module is assembled. You must place the CP system control macros in your virtual
card reader at OOC, as follows:
:READ DMKSYS ASSEMBLE (CP system control macros) DMKS NT [ONLY] assembles the system name table (DMKSNT) by invoking VMFASM. If you do not specify ONLY, the GENERATE EXEC procedure goes
on to invoke'the VMFLOAD EXEC procedure to place all the CP object modules on tape. If no error occurs, and if the CP
nucleus does not have a virtual=real area, GENERATE then loads
the tape, thus loading the CP nucleus (with the new version of DMKSNT) • If you do specify ONLY, the DMKSNT module is assembled, but
the CP nucleus is not written to tape and is not loaded.
To assemble DMKSNT, you
macros in your virtual
follows:
must place the
card reader, at
:READ DMKSNT ASSEMBLE (system name table macros) DMKFCB [ONLY] system name table
address OOC, as
assembles the forms control buffer load (DMKFCB) by invoking VMF ASM. If you do not specify ONLY, the GENERATE EXEC procedure
executes just as if you specified GENERATE VM370 (except it
does not build a new VM/370 directory and does not assemble
new DMKRIO or DMKSYS modules. Consequently, you should follow
the directions for issuing GENERATE VM370; except do not place
the Directory control statements, real I/O configuration
macros, or CP system control macros (nor their corresponding
:READ statements) in your card reader. 382 IBM VM/370 Planning and System Generation Guide