TMF Reference Manual (G06.26+)

TMFCOM Messages
HP NonStop TMF Reference Manual—522418-002
A-4
Other Messages
As an example, for the following excessively long command, TMFCOM would report
the error as follows:
TMF 3> ALTER BEGINTRANS, TRANSCOUNTTHRESH (1500, 1600), TMFLIBMEMTHRESH (85,90), TMPM
EMTHRESH (90,95), TTRANSPERCPU (1024,1024), AUTOABORT 7200 SECONDS, RECRMCOUNT 256,
RMOPENPERCPU 128, BRANCHESPERRM 128 (more characters follow, exceeding 240 total...)
... (85,90), TMPMEMTHRESH (90, 95), TTRANSPERCPU (1024,1024), AUTOABORT 720 ...
^
**ERROR-7172** Expecting AUTOABORT, BRANCHESPERRM, RECRMCOUNT, RESET,
RMOPENCPU, TMFLIBMEMTHRESH, TMPMEMTHRESH, TRANSCOUNTTHRESH, or
TRANSPERCPU.
TMF 4>
Other Messages
Other messages are generated as part of the normal output from TMFCOM commands
such as INFO and STATUS. These messages are generally self-explanatory and are
not documented in this appendix; many examples, however, appear in the individual
command descriptions in Section 3, TMFCOM Commands.
Event messages, directed to the Event Management Service (EMS) log file through the
$0 collector process, also appear on your screen. They often appear in displays
produced by commands such as DUMP FILES, DISPLAY OPERATIONS, and
RECOVER FILES. These are not TMFCOM messages, but are instead produced by
other TMF processes; they are documented in the Operator Messages Manual, along
with the event messages generated by many other subsystems.
Error Information and Failure Data Capture
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
•
Description 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