starter Systems The GENERATE EXEC issues the following message:
THE FOLLOWING STANDALONE SERVICE PROGRAMS ARE BEING PUNCHED ** FORMAT - DIRECT - DUMP/RESTORE - IBCDASDI ** PUNCHING I IPL FMT ' ****** PUNCHING • IPL DIR ' ****** PUNCHING • IPL DDR • ****** PUNCHING • IPL IBCDASDI I ******
Each program deck is preceded by a CP userid card and several
separator cards, all of which may be discarded. The format of these
cards is described in the V8L1IQ Operator's Guide. For more information
about the GENERATE EX EC procedure, see "Part 5. Updating V!/310." Step 15. Print or Punch the Starter System Suppiied
Directory, DMKSNT, DMKSYS, and DMKFCB
After the service programs are punched, the GENERATE EXEC asks you
whether you want a copy of the directory printed. Respond "yes." PRINT COpy OF RELEASEn DIRECT? -- RESPOND (YES I NO) : yes
This prints a copy of the directory, as well as copies of ASSEMBLE CP system control file), D!KFCB ASSEMBLE control buffer file), and DKKSNT ASSEMBLE (the system
provided with the starter system. The GENERATE EXEC procedure issues the following message:
A SAMPLE DIRECTORY IS BEING PRINTED TO AID YOU. the DMKSYS (the forms
name table)
IT SHOWS WHERE THE VIRTUAL DISKS ARE LOCATED ON ICPRnLO' YOU KAY USE THESE KINIDISKS FOR OTHER VIRTUAL MACHINES, IN PARTICULAR THE CMS SYSTEM DISK (MAINT 190 ) AND
THE CP STAGING AREA DISK ( MAINT 194 ) INCLUDED IN THIS DIRECTORY IS THE USERID: !AINT WHICH WILL BE USED FOR FUTURE SUPPORT OF THE SYSTEM. THIS USERID SHOULD BE INCLUDED IN THE DIRECTORY YOU BUILD FOR YOUR FLOOR USE. ** CAUTION ** IF YOU DESTROY USER MAINT'S AREAS, IT WILL BE NECESSARY TO RE-BUILD THE ENTIRE SYSTEM. A SAMPLE OF DMKSYS, DMKFCB, AND DMKSNT ASSEMBLE ARE ALSO BEING PRINTED TO AID YOU. THIS SAMPLE DKKSNT IS BASED ON THE INFORMATION INCLUDED IN THE SAMPLE DMKSYS AS WELL AS THE EXAMPLE ALLOCATIONS FOR VMRELn PROVIDED IN THE SYSGEN GUIDE. A COPY OF THIS DMKSNT MODULE HAS BEEN INCLUDED IN THE CP NUCLEUS, SUCH THAT IF ONE USES THE INCLUDED DMKSYS AND THE SAKPLE ALLOCATION PROVIDED IN THE SYSTEM GENERATION GUIDE, HE WILL BE ABLE TO SAVE HIS CKS SYSTEM UPON COMPLETION OF THE SYSTEM GENERATION PROCEDURE. A COpy OF DMKFCB HAS BEEN INCLUDED IN THE NUCLEUS AND NEED NOT BE RE-ASSEMBLED FOR SISTEPI GENERATION. IT HAS BEEN INCLUDED FOR THE USER WHO WOULD LIKE TO MODIFY OR ADD TO THE EXISTING BUFFER L01D. NOTE: IF THE USER WISHES TO MODIFY THE SAMPLE DMKSNT AND/OR DPIKFCB HE !AY INCLUDE THE UPDATED SOURCE WITH THE SOURCE INCLUDED UNDER THE OPTION 'GENERATE VK310', OF THE SYSTEM GENERATION PROCEDURE. IF PRESENT, IT WILL AUTOMATICALLY BE ASSEMBLED AND INCLUDED IN THE NEW CP NUCLEUS. Part 3. Generating VK/310 (CP, CMS, RSCS, and IPCS) 243

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