Starter Systems Aqain, the GENERATE EXEC procedure prompts you: DO YOU WISH TO HAVE A COpy OF DKKSNT, DKKSYS, DKKFCB, AND RELEASEn DIRECT PUNCHED TO CARDS? -- RESPOND (YEStNO): Enter "yes" to have these decks punched since you need to read in
updated copies of these decks in Step 16. "Part 2. Defining Your V"/370 System" contains a listing of the directory and the DKKSNT, DKKSYS, and
DKKFCB modules supplied with the starter system. The following messages
are issued to indicate the files that are being punched: PUNCHING ' DKKSNT ASSEKBLE ' ****** PUNCHING ' DKKSYS ASSEKBLE ' ****** PUNCHING ' DKKFCB ASSEKBLE ' ****** PUNCHING ' RELEASEn DIRECT ' ******
R;
Step 16. Build the VM/370 Directory and Assemble the Files Defining the Real I/O and System Devices
Create or update the following card files describing your installation's
version of the VK/370 directory, real I/O configuration, and system
devices and place them in the reader and invoke the GENERATE EXEC procedure to build the directory and assemble the files describing the
configuration. Kake sure your directory contains KDISK statements for KAINT's 193 and 294. Place the following cards in the card reader, in
the sequence shown:
ID CPGEN :READ filename DIRECT
(Directory program control statements)
:READ DKKRIO ASSEKBLE (Real I/O configuration macros)
:READ DKKSYS ASSEKBLE (system control macro statements)
:READ DKKSNT ASSEKBLE (system name table macro statements)
The Directory program control statements, real I/O configuration macros,
and system control macros are those you created according to the
instructions in Part 2. "Defining Your V8/370 System." You can code
your own system control macro statements or modify the sample files
supplied with the starter system.
New requirements demand that the user define space in the directory
for "Service Staging Areas". The minidisk addresses and suggested sizes
are described in the Kemo to Users for the SCP and later in this
publication under "Updating VK/370". These areas are used for the AUX files and PTF files contained on the system PUT. The files are loaded
by the individual service installation EXECs. Since the starter system's directory does not allocate space for the
minidisks, the "new user" service loaded in Step 13 did not attempt to
load these files. They will be loaded, however, when the rest of the
service is loaded, later in this procedure (Step 23) • 244 IB" V"/370 Planning and System Generation Guide

starter Systems Also, if you wish, you can change the printer forms control buffer
module (DMKFCB) to conform to local requirements. If you want to change
the printer forms control buffer, modify the file that was punched (in
step 15) and place it in the reader following the system name table
macro statements:
:READ DMKFCB ASSEMBLE (forms control macros)
:READ DMKSNT ASSEMBLE {system name table macros} Ensure that the cylinders specified for the directory as well as
the DMKSYS and DMKSNT source programs do not overlap each other.
Instructions for creating new forms control macro statements are in the 1&3 7 0 PrOQram!lll@S FORMAT OF THE READ CPNTROL STATEMENT The READ control statements must be punched according to the format
shown in Figure 26.
r I t Number of I I I ColumnlCharacterslContentsl !!eaning I , ,colon I : I Identifies card as a control card I , I 2-5 4 IREAD Identifies card as a READ control card I I , 6-7 2 , blank , I I 8-15 8 I fname Filename of the file punched I I 116 1 blank , 1 i i7-24 8 iftype Filetype of the file punched 1 1 125-80 56 1 blank
L
Figure 26. Format of READ Control Statement SPECIAL PROCEDURE IF YOU ARE USING ONLY ONE TAPE DRIVE If you are using only one tape drive, issue the command:
define 181 as 182
Now mount the scratch tape in place of the system PUT and ready the
device. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 245