Error Processing - Control Data Cyber 170 Series Operator's Manual

n
n+l
EXPORTL.
SYSTEM.
Export IImport; remote batch job input
loutput
However, the operator may instead enter the DSD command.
MAINTENANCE.
®
which performs the same function as AUTO but additionally assigns several maintenance
routines, according to mainframe type, to available control points and runs them as
normal jobs with minimum queue and CPU priorities. These routines are CPU or
central memory test routines designed to detect hardware errors. These routines
display error messages either at the control point on the B display (refer to section 4)
or in the system error log. The error log can be displayed by typing
A, ERROR LOG.
@
The operator should monitor these routines from time to time. If a maintenance routine
displays an error message indicating a hardware malfunction has occurred, a customer
engineer should be called.
It
is recommended that these programs be run at all times.
The maintenance programs use little memory, are run at minimum CPU and queue
priority, and are automatically rolled out if necessary; thus, system performance is
not severely affected. Descriptions of the maintenance routines can be found in the
On-Line Maintenance Software Heference Manual.
If an initial (level 0) deadstart was performed, it may be necessary to enter the follow-
ing command.
X.ISF.
@
This is the DSD command that calls the ISF program to activate system files VA LIDU S
(user validation), PHOFILA (project validation, if available), HESEXDF and HESEXVF
(resource management control files). This command is entered from the console,
unless it is an entry in the IPRDECK being used,
if
the system validation file (VALIDU S)
is to be used. The system checks the VALIDUS file when a user tries to access the
system to determine if he is a valid user. For additional information concerning the
ISF command, refer to 'section 1 in part IV of the Installation Handbook.
ERROR PROCESSING
Often, problems that may arise during deadstart may be detected visually. The following
list describes two such problems and the possible cause.
Problem
Tape moves but stops before any
display is activated.
60435600 A
Cause
• There is a parity on one of the first records
of the deadstart tape.
• The deadstart tape is not an I-mode unlabeled
tape.
• A 7-track tape is mounted on a 9-track drive
or vice versa.
• Tape unit is set to wrong density.
• Word 12 on deadstart panel is set incorrectly.
2-37