Section 1. Introduction To the Operational Control of the VM/370 System System operators, in almost all large System/370 installations, serve in
an apprentice capacity until they have acquired the skill and knowledge
to maintain the installation's operating system, be it DOS, OS, or YM/370. In an apprentice capacity, an operator acquires a basic proficiency
in mounting, making ready, and loading tape, DASD, line control, and
other hardware devices. Novice operators also learn the address
designations of all hardware devices attached to the system. They
become aware of those system resources that can be switched or patched
via alternate channel or telecommunication Fath to expedite system operations. The operator becomes aware of system console terminal operation as well as the function of most of the indicators, switches,
buttons, and alarlls that are part of the processer control,. All of this
knowledge is basic and must be acquired before considering the
operational control of any systell control program (SCP). The second phase of an operator's training is to be knowledgeable
about the SCP that is controlling the data precessing operations; he .ust be aware of its capability and its operating Fhilosophy. Tne operator must also be aware of the priorities and the demands placed
upon the system '. Much of this basic knowledge of VM/370 is described in the !ALJIQ In that document there is discussion on virtual machines; how they are built, identified, and used. Each facet of the virtual machine is described: the virtual processor6 virtual storaqe# virtual I/O devices, and the virtual system console.. Concurrent virtual machine usage and spooling operations are also described. The describes briefly the cOJlmandlanguage of CP and the other
components of Y8/370, namely, the Conversational ftonitor System (CftS), the Interactive Problem Control System (IPCS), and the Remote Spooling Communications Subsystem (RSCS). Wi th an understanding of Vfi/370 concepts, the power and versa tili ty of YM/370 is soon realized. The system operator is not just controlling
one process and its related storage and I/O with control and application programs; the operator is exercising control over the of multiple systems (virtual systems). Each virtual system with its own system operation, in turn, is being controlled by a user via a terminal
console. When additional facilities and resources or priorities are
needed by the virtual system, the virtual system operator must request
these services fro. the Vft/370 system operator. The system oper.ator
then delegates additional system resources to the virtual machine, if
feasible. Some of the operations that are exclusive functions perforlled by the VM/370 system operator are as follows: Reorder, purge, or copy any closed spool files Issue warning and high priority messages Attach and dedicate devices to specified virtual machines Automatically logon virtual machines Force users off the system when warranted Section 1. Intro. to operational Ctrl. of the V8/370 System 1
Change any virtual machine's dispatch Friority
characteristics
and opera ting
For details on
see "Section 3. how many of these and other functions are accomplished,
CP Commands" in this publication.
Depending upon the system installation, the system operator may also
be the operator of a large OS or DOS batch processing system that is run
in the virtual machine environment. Another duty of the system operator
is to control the data traffic from re.ote work stations. Information
on V8/370 control of such data transfer is detailed in the Regardless of the real system resources and the tasks and procedures
used, syste.s are subject to hardware and prcgram malfunction. The
Interactive Problem Control System of V!/370 provides a method of
recording and maintaining a history of V!/370 and virtual machine program problems. The V!fl70 Guide provides tpe details on how to use this system. Problems that are a result of a hardware fault are usually detected by the hardware itself, and trigger the recording of register contents
and sense values (related to the occurrence of the error) in V8/370's error recording area.
Regardless of whether the malfunction origin is hardware or software,
the system operator (in most cases) is notified of the seriousness of
the situations" by means of console indicators/alar.s or by console
diagnostic messages. These all serve to inform the operator that: The system operation can continue as before. The system operation can continue with reduced power/resource. System restart and recovery is co.mencing. System operation is'terminated. The type of recovery that is attempted is described in "System/370 Recovery 8anagement Support", which follows. System/370 Recovery Management Support IE! System/370 atte.pts correction of most aachine errors without program assistance. CP is notified, via an interruption, of both
intermittent and per.anent machine errors to allow error recording and
recovery procedures to The following recovery features are implemented in the IB! Systea/370 hardware: Retry of the failing processor operations Validity checking on processor and control storage to correct all
single-bit errors I/O operation retry facilities including an extended channel status vord (ECSlf), which provides channel retry data to channel and control
unit retry procedures Expanded machine check interruption facilities tc improve error
recording and recovery procedures
2 V8/370 Operator's Guide
Previous Page Next Page