Introduction
The operating systems that can run in virtual machines are: ,-- I Batch or , DOS I DOS/VS lOS/PCP , OS/MFT I OS/MVT , OS/VS1 I OS/VS2 lOS-ASP I RSCS L- l1yltiple=!££g,§,§ VM/370 Time Sharing Option of as CMS provides each these with virtual device support and virtual
storage. The operating systems themselves execute as though they were
controlling real devices and real storage, but they must not violate any
of the restrictions listed in "Appendix F: VM/370 Restrictions."
Introduction to VM/370 System Generation
The purpose of the system generation is to create a system that meets
your installation's particular needs.
The first step in the system generation procedure is to restore the
starter system, a small working copy of a basic VM/370 system. Using the starter system, you tailor a VM/370 system to your own hardware
configuration. You also describe your DASD volumes and define how they
are to be used.
The following versions of the starter system can be ordered: • 2314 Starter System • 3330 Starter System • 3340 Starter System • 3350 Starter System All starter systems must be restored to a compatible disk (that is, 2314
starter system to a 2314 disk), but all starter systems can then be used
to build any supported system residence volume type (2314, 3330, 3340, or 3350).
Before you begin the system generation procedure, you should: • Know which devices to include in your VM/370 system. • Create the real I/O configuration (DMKRIO) file describing your I/O configuration. If an IBM Mass Storage System is to be attached to VM/3 7 0, you must coordinate the real I/O configuration with the Mass Storage Control's tables.
4 IBM VM/370 Planning and System Generation Guide

Introduction • Decide how many virtual machines to define. • Create the VM/370 directory control statement file describing the
virtual machines. • Decide which volumes are to be owned and used by
residence, paging, spooling, and so on), the amount
available to VM/370, and the user identification of
operator. CP (for system
of real storag e
the real system • Create the CP system control (DMKSYS) file describing CP-owned
volumes, the real storage size, and so on. • If you wish, you can create your own forms control buffer (module DMKFCB) and system name table (module DMKSNT). These modules are,
however, supplied with the starter system. Once you have defined your VM/370 system with these files, you can
begin the system generation procedure. You should read the rest of Part 1 to be sure you have all the information you need to generate your
system. Part 2 has the information you need to code the files that
define your system. Part 3 describes the system generation procedure
step-by-step. Before you start the system generation procedure be sure
you have the following manuals available: VM/37Q VM/3
7
Q VM/31Q § If you are using the MSS support, you will also need the following: OS/VS Order No. GC35-0068
or Order
No. GC26-3792
During the system generation procedure, you apply the system Program Update Tape (PUT) supplied with the starter system. This updates your
system to the current level. Then use the Installation Verification
Procedure (IVP) to verify that the VM/370 system is functioning
properly. Part 1. Planning for System Generation 5