General Information General Information CP and C"S have separate system residence disks which may be located on
the same or different physical disks. The following procedure tells you
how to generate the CP system residence disk or move the CMS system
residence disk. Before you attempt to generate a VK/370 system, make
sure that the real I/O configuration file (DKKRIO), CP system control
file (DKKSYS), the VK/370 Directory file (DKKDIR), and, optionally, the
forms control buffer load (DMKFCB) and the system name table file (DKKSNT) are punched. Information about preparing these files is in "Part 2: Defining Your VM/370 System." If CMS is to be sa ved as a named
system, be sure that the NAKESYS macro is coded correctly in the DKKSNT file.
The VK/370 starter system is distributed on a 9-track tape (1600 or 6250 bpi), that can be restored to direct access volumes. You must
specify the device type (2314/2319, 3330, 3340, or 3350) when you order VK/370. The 3340 starter system fits on a 35 megabyte disk, so it can hp to of thp 33UO Qr 33UU- the starter svstem th; type (2314, 3330; 3340, or 3350) it was ordered for, you can use it to generate a VK/370 system for
residence on any other type of device as well as for the type of device
for which it was ordered. You should also specify the tape density
required (1600 or 6250 bpi).
The layout of the starter system's minidisk areas are constrained by the number of cylinders that may be dumped onto one volume of 1600 bpi
tape. Therefore, it is strongly recommended that KlINT's 190 (the CKS system disk) and 194 (the CP area) be reproduced on larger minidisks for
ease of maintenance. Also, "service staging areas" for CP/RSCS and CKS/IPCS (294 and 193 respectively), must be created to receive the
auxiliary files and "update" files from the system PUT. This process is
detailed later in this publication under the heading "Updating Vft/370" and in the Kemo-to-Users that is contained on the system PUT. The VK/370 system tapes are as follows: • The V"/370 starter system contains the base level of both the CP and CKS systems, the text decks with which to build these systems, and
the maclib and support procedures. • The SOURCE tape contains all source files, and macros of VK/370. • The system Program Update Tape (PUT) contains all source updates,
text decks, modules, macros and macro libraries, and procedures
required to build the latest level of CP, CKS, RSCS, and IPCS. • The SOURCE tape and the system PUT are created (and restored) with
the V"FPLC2 command.
Five optional sets of tapes can also be ordered: • The assembler tape containing source, macros, text, modules, and
procedures for the assembler • CP assembly listings (three tapes) • CP (AP) assembly listings (two tapes) • CKS assembly listings (two tapes) • IPCS and RSCS assembly listings (one tape)
228 IBK VK/370 Planning and System Generation Guide

Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0831
General Information
Generating CP and CMS Using the Starter
Systems
Except where otherwise noted, you can sUbstitute other values in place
of the device addresses, volume labels, and allocations shown. Note
that if you use the sample DMKSNT and DMKSYS files provided with the
starter system, and the sample allocations shown in Steps 2 and 3, you
can save your CMS system at the end of the procedure.
It is recommended that you use the sample allocations given
in Step 2 and the label VMRELn for the new system residence volume, to
ensure that you have sufficient TEMP space to complete the system
generation. (The TEMP space provided on the starter system volume may
not be sufficient for large systems.)
The examples of messages and responses assume that you are performing
the system generation at a typewriter terminal, such as a 3210, 2141, or
3767 (operating as a 2141). If you are using a display device, such as
the 3277, when you type the response to a prompting message, that
response appears in the user input area. When you enter that response,
it is redisplayed in the output area on the line below the prompting
message. Also, if the standalone service programs (such as the DASD Dump
Restore program or Format/Allocate program) send output to a terminal
display screen, the output is wrapped around immediately, when the
screen becomes full, to continue displaying. While you are generating the system, you may see some extraneous
messages as the starter system is processing. These are not shown in
the examples below. Only those messages that you should take note of,
or respond to, are shown. Step 1. load the Format Program from the Starter System Tape
Mount the CP starter system tape and IPL the tape. The CP Format/Allocate service program is the first file on the tape; it is now
loaded. Do not rewind the tape because the next file is needed later in
the system generation procedure (Step 4). Step 2. Format, label, and Allocate the System Residence Volume Use the CP Format/Allocate program to format, label, and allocate space
on the new system residence volume. This label must be VKRELn; where n
is the release level of the VM/370 System control program. VMRELn is
used in the starter system's system control file - SYSOWN marco -to
allow the volume to be used for paging, spooling, and TDSK allocations.
First, identify the system console by pressing the Request key (or
equivalent); if the console address is either 009 or 01F, you do not
have to press the Request key. Then, to execute the Format/Allocate
service program, respond to the prompting messages. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 229