TFDS Manual

Using TFDS
Tandem Failure Data System (TFDS) Manual—520628-003
2-2
How TFDS Works
•
Instrumentation calls embedded in code to indicate a detected internal
software failure. When a failure is detected, TFDRTL collects the failure
specification and notifies the TFDS monitor.
•
TFDSCOM requests for configuration changes or actions such as manual
dumps or reloads.
2. When a software failure is detected, TFDS collects sufficient failure data from the
processor to build a failure signature and performs rediscovery analysis.
3. The failure signature is compared to a local database of previous signatures to
determine whether the failure is a first-time occurrence or the result of a recurring
defect. This database is created and appended to by TFDS as unique failure
events are identified.
•
If TFDS determines that the current failure is a first-time occurrence, TFDS
captures the data and records the failure signature as a new incident record in
the local database.
•
If TFDS determines that the current failure is a recurrence of a previous
incident, the dump file is suppressed (unless DUMPOVERRIDE is enabled),
and the number of occurrences for the particular failure is updated in the local
incident database.
Figure 2-1. TFDS Operational Model
TFDS
TFDS
Monitor
3
1
CPU DOWN
Instrumentation Calls
Failure Data
Dump
Reload
Backup
(optional)
Service
Provider
6
Dial-Out
(optional)
Run-Time
Library
(TFDRTL)
Tape
Local
Incident
Database
TFDSCOM
5
User Interface
Server
NonStop
Processor
Rediscovery
Engine
2
4
$0, $ZLOG
VST001.vsd
Log
EMS