Manualshelf

SNAX/HLS Diagnosis and Support Manual

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series
71727374757677787980
SNAX/HLS Log Messages
C–2 104706 Tandem Computers Incorporated
process nam
e
: Backup abended too many times
Cause. Within the past 30 minutes (approximately) there were more than five
successive attempts to initiate a backup process, all of which resulted in abnormal
termination of the backup.
Effect. No further attempts to start a backup process are made.
Recovery. This might be either a hardware problem or a programming error in the
subsystem. If you determine that it is a programming error, gather the information
discussed at the beginning of Section 1, “Problem Determination” and contact your
Tandem analyst.
If you want to run the process with a backup, select an alternate backup CPU number.
process nam
e
: Backup in CPU
n
stopped unexpectedly
Cause. The backup process in CPU n stopped for reasons other than the result of a
STOP command from the primary process.
Effect. The SNAX/HLS
process name
is no longer backed up. An attempt is made
to restart the backup.
Recovery. Determine why the backup stopped. It could have been stopped from
another command interpreter, the CPU could have failed, or a programming error in
the backup caused the backup process to stop.
If the CPU failed, you can restart the backup in another CPU. If the process was
terminated by another user, the primary restarts it automatically. If the process
stopped for other reasons, it probably represents a programming problem in the
backup. If the problem persists, gather the information discussed at the beginning of
Section 1, "Problem Determination" and contact your Tandem analyst.
process name
: Backup open without primary open, process
process-nam
e
Cause. An open message was received from a backup process and no corresponding
primary open was found.
process-name
is the process that issued the open
message.
Effect. The open message is rejected and the OPEN command fails. The program and
backup are out of synchronization.
Recovery. This typically indicates a programming problem in the requester. Correct
the error.