OI GCLU-ltlUl-l0 As Updated April 1, 1981 by TNL GN25-0837 GENERATE
GENERATE
GENERATE is a multipurpose EXEC used to generate VK/370. use it to perform updating and maintenance of • CP, eMS, and RSCS • VM/370 service programs You may also You may also use it to regenerate your VK/370 operand after updating • The directory • The real I/O configuration (DHKRIO) • The system control file (DHKSYS) • The forms control buffer load (DKKFCB) • The system name table (DHKSNT) Instructions for coding the control statements and macros that define
your VM/370 directory, and DHKRIO, DMKSYS, and DKKSNT files are in "Part 2. De[iniug Your VM/370 Instructions for coding a new DKKFCB module are in the VHlJ70 programmer-s The GENERATE EXEC procedure assumes the following: Virtual RSCS/IPCS tape address = 181 Virtual CP nucleus tape address = 182
virtual address of CMS build area = 190 virtual address of CP and RSCS build area = 194 Virtual card reader = OOC The format of the GENERATE EXEC command is:
GENERATE VM370 VM370 DIRECT (ONLY] DMKRIO [ONL I] DMKSYS [ONL I] DMKFCB [ONLY] DMKSNT [ONLI] IPLDECK SRVCPGM r , ICP I NUCLEUS [NOLOAD] ICMSI L .J FSCS [BUILD] builds a new VM/370 directory, assembles DMKRIO and DKKSIS (also assembles DMKFCB and DMKSNT, if they are supplied),
writes the CP nucleus to tape and optionally loads it. You must have the appropriate files in your virtual card
reader at address OOC. place the following in your card
reader, in the order shown:
: READ fn DIRECT
{Directory program control :READ DMKRIO ASSEMBLE 380 IBM VM/370 Planning and System Generation Guide

(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