TMF Operations and Recovery Guide (G06.24+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-002
3-23
Gathering Information About Errors and Failures
The following command removes transaction number 5769602 that originated in
CPU 4 of the system in which the command is issued:
TMF 50> DELETE TRANSACTION 4.5769602
You can use the DELETE TRANSACTION command only if you are logged on under
the super ID. (The super ID is the person with the user ID 255,255—in effect, the
group manager of the super user group.) See the TMF Reference Manual for more
information on using the DELETE TRANSACTION command.
Gathering Information About Errors and
Failures
If a TMF internal error or a software or hardware failure occurs, capture as much
information about the problem as possible. Then, contact the Global Customer
Support Center (GCSC) or your service provider and supply all the relevant
information.
For all problems, please capture and provide the following standard items:
•
Your system serial number
•
Product numbers and versions of TMF software and all related products involved in
the problem
•
Descriptions of the problem and the accompanying symptoms
•
Event Management Service (EMS) log files, containing recent event messages
written during the last 12 to 24 hours, (usually located on $SYSTEM.ZLOGnn, or if
that subvolume does not exist, $SYSTEM.SYSTEM.OPRLOG)
•
SAVEABEND files generated at the time of failure; these will be located on the
same volume and subvolume as the program files (typically $SYSTEM.SYSnn)
•
TMF configuration files (including the TMF catalog), whose location is listed in the
INFO TMF command display
•
All pertinent notifications and reports from the HP Tandem Service Management
(TSM) Notification Director Application
Caution. The DELETE TRANSACTION command can leave your database in an inconsistent
state that cannot be corrected by the TMF recovery process. Contact the Global Customer
Support Center (GCSC) or your service provider before issuing this command.
Use the DELETE TRANSACTION command only when all other efforts to abort the transaction
have failed and data availability is more important than data integrity.