Tandem Failure Data System (TFDS) Manual

Introduction to TFDS

HP Tandem Failure Data System (TFDS) Manual—540122-003

1-7

Files Included in Failure Data Collection

Failure incident numbers are used to create names for subvolumes to which files that

might be helpful in resolving problems are copied. These subvolume names have the

form ZDMPnnnn, where nnnn is the incident number.

The set of files that is collected depends on the type of incident that has occurred and

whether or not the incident is a rediscovery. In general, however, when an incident

occurs, the TFDS monitor:

1. Copies to the incident subvolume any logs used by $ZLOG and $0 within thirty

minutes of the failure. (Thus if there was a log file switch within the previous thirty

minutes, a copy of the previous log would also be in the incident subvolume.)

2. Moves the processor dump file from the ZDMPTEMP subvolume to the incident

subvolume. After moving the dump file, the TFDS monitor purges the copy in the

ZDMPTEMP subvolume.

3. Copies the file $SYSTEM.SYSnn.OSDIR, and the files referenced by OSDIR, to

the incident subvolume.

4. Copies the files referenced in the permanent and temporary ACQUIREFILES lists

to the incident subvolume. (For more information, see ACQUIREFILES on

page 3-4.)

5. Moves the snapshot file created by eGarth from the ZDMPTEMP subvolume to the

incident subvolume.

6. Copies OSM alarm files ($system.zservice.zzaa*) and hardware snapshot files

($system.zservice.zzsn*) created within thirty minutes of the failure to the incident

subvolume.

Note. The EXCLUDEFILES command can be used to keep specific files from

being copied to the incident subvolume. For more information, see

EXCLUDEFILES on page 3-21.