Initialization of the eMS Virtual Machine
Environment
There are four steps involved in initializing a CMS virtual machine: Processing the IPL command for a virtual card reader. Processing the IPL command for a disk device or a named or saved
system. processing the first command line entered at the CMS virtual console. Setting up the options for the virtual machine operating environment. DMSINI and DMSINS are the two routines that are mainly responsible
for the one-time initialization process in which the virtual card reader
is initial program loaded. DMSINI also handles the IPL process when a
named or saved system is loaded. The C!S command interpreter, DMSINT, processes the first line entered from the console as a special case; the
processing performed by this code is a part of the initialization
process. DMSSET sets up the user-specified virtual machine environment
features; DMSQRY allows the user to query the status of these settings. Initialization: Loading a CMS Virtual Machine from
Card Reader When a virtual card reader is specified by the IPL command, for exaaple OOC, initialization processing begins. Initialization refers to the
process of loading from a card reader as opposed to reading a nucleus from a cylinder of a CMS minidisk or reading a named or shared system
(description follows).
IPL OOC invokes the CMS module DMSINI, which requests that the
operator enter information sucb as the address of the DASD where the
nucleus is to be written, the cylinder address where the write operation
is to begin, and which version of CMS is to be written (if there is more than one to choose fro.). When all questions are answered, the requested nucleus is written to
the DASD. Once written on the DASD, a copy of the nucleus is read into virtual
.achine storage. One track at a tiae is read from the disk-resident
nucleus into virtual storage. DMSINS is then invoked to initialize
storage constants and to set up the disks and storage space required by
this virtual machine. DMSINS performs three general functions: Initializes storage constants and system tables. Processes IPL command line parameters (SEG= and BATCH). Initializes for as SVC processing, in the case where a saved segment
is not available for use in processing os simUlation requests. CMS Method of Operation and progras OrganiZation 2-57
INITIALIZES STORAGE CONTENTS AND SYSTEM TABLES DMSINS ---Saves the address of this virtual machine in NUCON. Locates and returns the address of the ADT for this virtual machine. DMSFRE free storage to be used during initialization. DMSFRE -- Allocates all low free storage so that the system status table (SSTAT) will be built in high free storage. DMSACM ---aeids the S-disk ADT entry and builds the SSTAT. DMSFRE --Releases the low free storage allocated above (to force SST.AT into
high storage) so that it can be used again. DMSINS ---Stores the address of SSTAT into ASSTAT and ADTFDA in NUCON. Sorts the entries in the PROCESSES IPL COMMAND LINE PARAMETERS DMSINS -- Checks for parameters BATCH, and SEG=, or AUTOCR. If BATCH is
specified, DMSINS sets the flag BATFLAGS. If SEG= is specified, DMSINS loops through again to read the segment name. At this point,
all the parameters on the com.and line have been scanned.
If SEG= is specifiad, the DIAGNOSE 64 FINtSYS function is issued
to determine whether the segment specified on the command line
exists. If it does, the DCSSIVAL flag is temForarily set.
If AUTOCR is specified, a local flag is set so that the subsequent
console read aay be bypassed and the null line input simulated. This
action causes a PROFILE EXEC to be executed. Issues DIAGNOSE 24 to obtain the device type of the console. DMSCWR ---WrItes the system id message to the console. DMSCRD --Reads the IPL command line from the console. Puts the IPL command line in PLIST format. DMSINS ----If-the FINDSYS DIAGNOSE validated the segment name specified on the IPL command line, DMSINS issues a DIAGNOSE 64 SAVESYS function for
that segment.
2-58 IBM VM/370 System Logic and Program Determination--Volume 2
Previous Page Next Page