FFST: IBM MQ client for HP Integrity NonStop Server
Describes the name, location, and contents of the First Failure Support Technology™ (FFST™) files for HP Integrity NonStop Server systems.
For the IBM MQ client for HP Integrity NonStop Server, FFST information is recorded in a file in the MQ_INSTALLATION_PATH/var/mqm/errors directory.
An FFST file contains one or more records. Each FFST record contains information about an error that is normally severe, and possibly unrecoverable. These records indicate either a configuration problem with the system or an IBM MQ internal error.
FFST files are named AMQ.nnn.xx.ppp.qq.FDC, where:
- nnn
- The name of the process that is reporting the error.
- xx
- The processor number on which the process is running.
- ppp
- The PIN of the process that we are tracing.
- A sequence that starts at 0. If the full file name exists, this value is incremented by one until a unique FFST file name is found. An FFST file name can exist if a process is reused.
Each field can contain fewer or more digits than shown in the example.
An instance of a process writes all FFST information to the same FFST file. If multiple errors occur during a single execution of the process, an FFST file can contain many records.
To read the contents of an FFST file, we must be either the creator of the file, or a member of the mqm group.
When a process writes an FFST record, it also creates an EMS event.
Figure 1 shows a typical FFST report for an IBM MQ client on a HP Integrity NonStop Server system:
+-----------------------------------------------------------------------------+
| |
| IBM MQ First Failure Symptom Report |
| =================================== |
| |
| Date/Time :- Mon April 29 2013 10:21:26 EDT |
| UTC Time :- 1367245286.105303 |
| UTC Time Offset :- -240 (EST) |
| Host Name :- MYHOST |
| Operating System :- HP NonStop J06.14, NSE-AB 069194 |
| |
| PIDS :- 5724H7222 |
| LVLS :- 7.1.0.0 |
| Product Long Name :- IBM MQ for HP NonStop Server |
| Vendor :- IBM |
| Installation Path :- /home/cmarti/client/opt/mqm |
| Probe Id :- MQ000020 |
| Application Name :- MQM |
| Component :- Unknown |
| SCCS Info :- S:/cmd/trace/amqxdspa.c, |
| Line Number :- 3374 |
| Build Date :- Apr 24 2013 |
| Build Level :- D20130424-1027 |
| Build Type :- ICOL - (Development) |
| File Descriptor :- 6 |
| Effective UserID :- 11329 (MQM.CMARTI) |
| Real UserID :- 11329 (MQM.CMARTI) |
| Program Name :- dspmqtrc |
| Addressing mode :- 32-bit |
| LANG :- |
| Process :- 1,656 $Y376 OSS 469762429 |
| Thread(n) :- 1 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- krcE_UNEXPECTED_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- AMQ.3.520.sq_tc.0.TRC |
| Comment2 :- Unrecognised hookID:0x3 at file offset 0x4b84 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xcsGetEnvironmentInteger
-{ xcsGetEnvironmentString
...
The Function Stack and Trace History are used by IBM to help problem determination. In many cases, there is little that the system administrator can do when an FFST report is generated, apart from raising problems through the IBM Support Center. However, there are some problems that the system administrator might be able to solve, for example, if the FFST report shows Out of resource or Out of space on device.
For more information about FFST, see First Failure Support Technology (FFST).
Parent topic: First Failure Support Technology (FFST)