Tandem Failure Data System (TFDS) Manual

Dependencies and Compatibility
HP Tandem Failure Data System (TFDS) Manual—540122-003
B-3
TFDS Product Dependencies
TFDS Product Dependencies
TFDS has these dependencies:
•
TFDS process dumps depend on the Inspect subsystem (IMON and INSPSNAP).
•
TFDS uses the Persistence Manager ($ZPM) to start or restart the TFDS monitor
and TFDS helpers, which are defined under the Kernel subsystem.
•
TFDS uses the Visual Inspect snapshot server services to create snapshot files.
•
TFDS uses eGarth to gather information about processor software failures.
•
TFDS uses FUP to move files and to copy event log data.
•
TFDS needs the OS millicode to provide a single TFDS break value, plus another
one reserved for future use.
•
TFDS needs the OS millicode to handle the __break instruction.
•
TFDS uses the NonStop OS utility RcvDump to dump processors.
•
TFDS uses the NonStop OS utility RELOAD to reload failed processors.
•
TFDS requires the services of OSM for two distinct reasons:
°
Dial-out of incident alerts (via EMS messages logged in $ZLOG) to your
service provider.
°
Initial processing of Processor Down message. OSM and TFDS share an
interface where OSM tells TFDS if and when to proceed with the dump-related
tasks for that processor. OSM and TFDS are two distinct processes; the
interface exists to time the sequential nature of the work OSM needs to
accomplish before TFDS.
•
TFDS reads the contents of the SYSnn OSDIR file to get the list of files that should
be collected along with a processor failure.
•
TFDS uses the BACKUP program to move incident information to tape.
•
The incident database record layout is different on Integrity NonStop NS-series
systems. incident databases created on NonStop S-series systems are not
compatible with TFDS on Integrity NonStop NS-series systems. For more
information, see Migration Considerations on page 1-8.