2. Take a storage dump if the automatic dump routine failed.
3. Try to preserve spooling and accounting data by issuing theSHUTDOWN command if it has not been done automatically.
4. Try to force error recording if it did not occur.
5. Attempt to analyze theproblem by whatever means at his disposal
and if necessary, reallocate resources and priorities.
6. Call for technical assistance if necessary.Whenever there are indications that I/O errors require further
analysis or that basic integrity of a device needs to be determined,
other service programsmay be invoked to help make such an assessment.
For example, to test the operational 3344 or 3350DASD devices, the
operator may invoke theOS/VS and DOS/VS Analysis Prograa-1 (AP-1).
This utility program, if resident in theOS/VS or DOS/VS library of a
virtual machine, can be used to check the Froper operation of the
device. The use of this program alongwith error messages and user
action is detailed in thegnd (AP-l) In the event that technical assistance is required, it can be
obtained from the following sources:• The customer's own system programmer(s). • The service representative, who has special test equipment for
hardware problem isolation.e The IBM Program Support Bepresentative
6who can also assist with VK/370 system problem diagnosis. You can assist with problem diagnosis by being alert for the
following error recording messages:DKKIOG550E I/O ERROR RECORDING AREA 90 PERCENT FULL; RUN CPEREP DKKIOG551E I/O ERROR RECORDING AREI FULL; RUN CPEREP You should then duap the error recording data to some other device
(usually a tape drive) and clear the error recording area to insure
enough space toreco=d additional error records. Information on how to
run CPEREP is contained in thegDg RecQrdiBg Additional information on OS/VS EREP, the program to which CPEREP passes
control is detailed in theRe£Q£ginq !ng E£in!ing publication. Other errors may not be severe enough to cause V8/370 system failure,
butmight cause a specific virtual machine to abnormally terminate. In most cases, the user can IPt the virtual machine again. Should the V8/370 aachine enter an unexpected WAIT state or loop, see
the§y!de referring to the section entitled
"How ToUse the VK/370 Facilities To Debug." Section 2. Initiating V8/370 Operation 25
3. Try to preserve spooling and accounting data by issuing the
4. Try to force error recording if it did not occur.
5. Attempt to analyze the
and if necessary, reallocate resources and priorities.
6. Call for technical assistance if necessary.
analysis or that basic integrity of a device needs to be determined,
other service programs
For example, to test the operational 3344 or 3350
operator may invoke the
This utility program, if resident in the
virtual machine, can be used to check the Froper operation of the
device. The use of this program along
action is detailed in the
obtained from the following sources:
hardware problem isolation.
6
following error recording messages:
(usually a tape drive) and clear the error recording area to insure
enough space to
run CPEREP is contained in the
control is detailed in the
but
the
"How To