Introduction The IBM Virtual Machine Facility/370 is a System Control Program (SCP) that manages a real computing system so that all its resources -- ma1n processor, attached processor, storage, and input/output devices --are
available to many users at the same timee Each user has at his disposal
the functional equivalent of a real, dedicated computing system.
Because this functional equivalent is simulated by VM/370 and does not
really exist, it is called a "virtual" machine.
The processors that VM/370 supports are listed under the
"Processors" later in Part 1. The real System/370 must have the
Address Translation feature, a hardware facility that translates
storage addresses to real storage addresses, and the System facility. Also, it must operate in extended control mode, a
which all the features of a System/370, including dynamic
translation, are operational. VM/370 has four components:
heading
Dynamic
virtual
Timing
mode in
address The control program (CP), which controls the resources of the real
computer to provide multiple virtual machines. The Conversational Monitor System (CMS), which provides a wide range
of conversational and time-sharing facilities. Using CMS, you can
create and manage files, and compile, test, and execute problem
programs. The Remote Spooling Communications SUbsystem (RSCS), which transfers
spool files between VM/370 users and remote locations over
telecommunication lines. The Interactive Problem Control System (IPCS), which provides VM/370 problem analysis and management facilities, including problem report
creation, problem tracking, and CP abend dump analysis.
For an overview of the functions performed by VM/370, see the !ML31Q In.iIQdu£iio1!. Virtual Machine Operating Systems While the control program
the virtual machines, it
managing the work flow
virtual machine executes
one may use a different
same operating system.
of VM/370 manages the concurrent execution of
is also necessary to have an operating system
within each virtual machine. Because each
independently of other virtual machines, each
operating system, or different releases of the Part 1. Planning for System Generation 3
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
Previous Page Next Page