TFDS Manual

EMS Messages and Templates
Tandem Failure Data System (TFDS) Manual—520628-003
D-3
EMS Messages
Recovery. Mount a tape (on the tape drive specified through the TFDSCOM TAPE
command) and put the tape drive online, or issue a CANCELBACKUP command.
4
Cause. The backup operation requires more tapes.
Effect. The backup is waiting for the next tape.
Recovery. Mount a tape and put the tape drive online.
5
Cause. A new incident was stored in the incident database.
Effect. A new register was stored in the incident table. The affected processors are
dumped and reloaded automatically.
Recovery. Informational message only; no corrective action is needed.
6
Cause. An incident has already been defined in the database.
Effect. The number of occurrences is tabulated. The affected processors are dumped
and reloaded automatically.
Recovery. Informational message only; no corrective action is needed.
7
Cause. Either a dump was requested through TFDSCOM or a CPU DOWN message
arrived.
Effect. A dump is started by RCVDUMP. (Dumping a processor usually takes from 5 to
20 minutes and can slow system performances during this time.) TFDS attempts to get
a successful dump and automatically reloads the processor according to your
TFDS *0004* $ZDMP : BACKUP Load Next Tape on: xxxxxxxx
TFDS *0005* $ZDMP : Product #nnnn, Halt code %nnnnnn
New Problem Logged, File(s) Located at xxxxxxxxxx
Symptom String : xxxxxxxxx
TFDS *0006* $ZDMP : Product #nnnn, Halt Code %nnnnnn
Recurrent Problem Logged, Symptom String: xxxxxxxx
TFDS *0007* $ZDMP : DUMP; Starting a ReceiveDump for CPU : nn