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

IPLDECK SRVCPGM r ,
If you want to add or replace
must place your FCB macro in
file; after label DMKFCBLD. GENERATE the IBM supplied FCB image, you the IBM supplied DMKFCB assemble
If you specify ONLY, only the DMKFCB module is assembled. You must place the forms control buffer load macros in your virtual card reader at OOC, as follows:
:READ DMKFCB ASSEMBLE (forms control buffer load creates the standalone service programs on disk from their
associated object modules (text decks). These files must be
on the eMS system disk (S-disk). You are prompted to enter
the names of the service programs you wish to generate. You can respond ALL, DDE, DIE, or If you respond ALL, the DASD Dump Restore, Directory, and Format/Allocate standalone
programs are built on disk. punches all the standalone service programs (DMKDIR, DMKDDR, DMKFMT, and IBCDASDI). rCp I NUCLEUS [NOLOAD] ICMS! generates the CP or CMS nucleus. If you specify CP
L J NUCLEUS, the CP nucleus is loaded onto tape.
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.
Attached Processor support will be included in the nucleus, if
desired. If you specify CP NUCLEUS NOLOAD, the tape is
created with the new nucleus but the disk is not loaded.
If you specify CMS NUCLEUS, a card-image deck is created and
placed the virtual card reader. GENERATE issues a
prompting message to see if you want a card-image copy of the CMS nucleus put on disk. If you respond "yes," GENERATE
writes a copy of the CMS nucleus on disk, and loads the
nucleus. The card-image copy of the CMS nucleus is a file (CMSNUC NUCLEUS) that can later be loaded to create a CMS nucleus. If you specify CMS NUCLEUS NOLOAD, the new nucleus
remains in the virtual card reader. RSCS [BUILD] Prepares the RSCS build area
nucleus, as described in
Installing RSCS."
and, optionally, builds the RSCS the section "Generating and
The GENERATE EXEC procedure issues many descriptive responses, most of
which are shown in the system generation procedures in Part 3.
Generating VM/370 (CP, CMS, RSCS, and IPCS). Part 5. Updating VM/370 383