Cleaning up IBM MQ files

If you traced IBM MQ to diagnose a problem, those trace files will be in the /var/mqm/trace directory. Binary trace files are named AMQxxxxx.y.TRC, AMQxxxxx.y.TRS, and formatted traces are named AMQxxxxx.y.FMT, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0. Binary GSKit trace files are named AMQ.SSL.TRC and AMQ.SSL.TRC.x, where x is a sequence number, normally 1.

If you used the runmqras command to collect information for IBM support, it created a .zip file containing diagnostic information for IBM, by default under the /tmp directory. Save your runmqras .zip files until your IBM MQ problem is fully resolved, then delete them manually. For example:

Back to top

Windows

IBM MQ files are always created under the directory given by the WorkPath registry key. To find the work path, use the amquregn program and the amquregn.ctl control file shipped with any IBM MQ installation and ignore the double backslash characters in the result.

IBM MQ creates FFST files in the errors subdirectory of the work path. On Windows, these files are named AMQxxxxx.y.FDC, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0. For certain serious errors, IBM MQ for Windows may also create AMQxxxxx.x.y.dmp files in the same directory, where x is a thread identifier number and y is a sequence number, normally 0.

If you traced IBM MQ to diagnose a problem, those trace files will be in the trace subdirectory of the work path. Trace files are pre-formatted and are named AMQxxxxx.y.TRC and AMQxxxxx.y.TRS, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0. Binary GSKit trace files are named AMQ.SSL.TRC and AMQ.SSL.TRC.x, where x is a sequence number, normally 1.

If you used the runmqras command to collect information for IBM support, it created a .zip file containing diagnostic information for IBM, by default under the current user's temporary directory (given by the TEMP environment variable). Save your runmqras .zip files until your IBM MQ problem is fully resolved, then delete them manually. For example:

Back to top

IBM i

IBM MQ creates FFST files in the /QIBM/UserData/mqm/errors directory. On IBM i, these files are named AMQxxxxx.y.FDC, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0. IBM MQ for IBM i also writes job log information to files named AMQxxxxx.x.y.JOB files in the same directory, where x is a thread identifier number and y is a sequence number, normally 0.

If you traced IBM MQ to diagnose a problem, those trace files will be in the /QIBM/UserData/mqm/trace directory. Binary trace files are named AMQxxxxx.y.TRC, AMQxxxxx.y.TRS, and formatted traces are named AMQxxxxx.y.FMT, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0. Binary GSKit trace files are named AMQ.SSL.TRC and AMQ.SSL.TRC.x, where x is a sequence number, normally 1.

If you used the runmqras command to collect information for IBM support, it created a .zip file containing diagnostic information for IBM, by default under the /tmp directory. Save your runmqras .zip files until your IBM MQ problem is fully resolved, then delete them manually. For example:

Delete unwanted spool files created by IBM MQ programs and make sure the spool files for the QMQM account are maintained. You can use WRKSPLF option 4 to delete spool files, or delete IBM MQ spool files for a user based on job name.

Optionally, you can configure IBM MQ job descriptors so they do not generate job logs except when there is an error. For example:

IBM MQ may log problems with IBM i when it detects an unusual situation. Review problems logged by IBM using WRKPRB option 8, then using option 20 to close resolved problems:

Back to top

HPE Integrity NonStop

IBM MQ creates FFST™ (First Failure Support Technology) files in the var/mqm/errors sub-directory of the IBM MQ OSS installation directory when it detects an unusual situation which may require investigation.  IBM MQ V8.x for HPE Integrity NonStop FFST files are named AMQnnnnnnnn.c.p.y.FDC, where nnnnnnnn is the name of the program that created the file, c is the CPU, p is the PIN number, and y is a sequence number, normally 0. WebSphere MQ V5.3 for HP NonStop Server FFST files are named AMQxxxxx.y.FDC, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0.

If you traced IBM MQ to diagnose a problem, those trace files will be in the var/mqm/trace sub-directory of the MQ OSS installation directory.  IBM MQ V8.x for HPE Integrity NonStop binary trace files are named AMQnnnnnnnn.c.p.y.TRC, AMQnnnnnnnn.c.p.y.TRS, and formatted traces are named AMQnnnnnnnn.c.p.y.FMT, where nnnnnnnn is the name of the program that created the file, c is the CPU, p is the PIN number, and y is a sequence number, normally 0. WebSphere MQ V5.3 for HP NonStop Server binary trace files are named AMQxxxxx.y.TRC, AMQxxxxx.y.TRS, and formatted traces are named AMQxxxxx.y.FMT, where xxxxx is the process identifier that created the file and y is a sequence number, normally 0.

If you used the sdcp command to collect information for IBM support, it created an archive file containing diagnostic information for IBM, by default in the current directory of the user who ran sdcp. Save your sdcp archive files until your IBM MQ problem is fully resolved, then delete them manually. For example:

If an IBM MQ process or application terminates abnormally, DMON may create a SAVEABEND file named ZZSAxxxx in the volume and subvolume containing the program, where xxxx is a number chosen by DMON. After the cause of the abend is determined, delete the SAVEABEND files manually in TACL. For example:

Back to top