dmpmqlog (dump MQ formatted log)

Purpose

Use the dmpmqlog command to dump a formatted version of the IBM MQ system log to standard out.

The log to be dumped must have been created on the same type of operating system as that being used to issue the command.

LOG RECORD - LSN <0:0:4615:42406>
**********

HLG Header: lrecsize 212, version 1, rmid 0, eyecatcher HLRH
Creation Time: 2017-01-30 13:50:31.146 GMT Standard Time (UTC +0)

Optional parameters

Dump start point

Use one of the following parameters to specify the log sequence number (LSN) at which the dump should start. If you omit this, dumping starts by default from the LSN of the first record in the active portion of the log.

-b

Start dumping from the base LSN. The base LSN identifies the start of the log extent that contains the start of the active portion of the log.

-s StartLSN

Start dumping from the specified LSN. The LSN is specified in the format nnnn:nnnn:nnnn:nnnn.

If you are using a circular log, the LSN value must be equal to or greater than the base LSN value of the log.

-n ExtentNumber

Start dumping from the specified extent number. The extent number must be in the range 0 - 9999999.

This parameter is valid only for queue managers using linear logging.

-e EndLSN

End dumping at the specified LSN. The LSN is specified in the format nnnn:nnnn:nnnn:nnnn.

-f LogFilePath

The absolute (rather than relative) directory path name to the log files. The specified directory must contain the log header file (amqhlctl.lfh) and a subdirectory called active. The active subdirectory must contain the log files. By default, log files are assumed to be in the directories specified in the IBM MQ configuration information. If you use this option, queue names associated with queue identifiers are shown in the dump only if you use the -m option to name a queue manager name that has the object catalog file in its directory path.

On a system that supports long file names this file is called qmqmobjcat and, to map the queue identifiers to queue names, it must be the file used when the log files were created. For example, for a queue manager named qm1, the object catalog file is located in the directory ..\qmgrs\qm1\qmanager\. To achieve this mapping, you might need to create a temporary queue manager, for example named tmpq, replace its object catalog with the one associated with the specific log files, and then start dmpmqlog, specifying -m tmpq and -f with the absolute directory path name to the log files.

-m QMgrName

The name of the queue manager. If you omit this parameter, the name of the default queue manager is used.

Note: Do not dump the log while the queue manager is running, and do not start the queue manager while dmpmqlog is running.

-d

Do not include log data (only information about the log is output).

-z

Normalize the format log output to make it easier to pass into other commands.

• All timestamps are output in ISO 8601 format, rather than in local time, enabling use of -t and -u options.
• XIDs are reformatted, enabling them to be processed by the -r XID option.

-t StartTime

Start dumping from the specified time. The time is specified in ISO 8601 format. Cannot be specified at the same time as -b, -s, or -n parameters. The base LSN value of the log is used as the starting search point for records.

This parameter is not valid on IBM i.

-u EndTime

End dumping from the specified time. The time is specified in ISO 8601 format. Cannot be specified at the same time as -b, -s, or -n parameters. The base LSN value of the log is used as the starting search point for records.

This parameter is not valid on IBM i.

-r Filter

Filter the output from the dmpmqlog. Multiple filters can be specified simultaneously, and a log record is displayed if it matches any of the specified filters. The possible filters are:

Data=hexadecimal_string

Display log records containing or associated with the data string in hexadecimal. The string can consist of 2 through 48 hexadecimal symbols (0-9, A-F) (24 bytes), and must have an even number of characters.

LogRecdType=log_record_type

Display log records with the specified numeric type. For example, -r LogRecdType=1025 displays ALM Start Checkpoint records.

ObjectName=object_name

Display log records associated with the specified object name.

TranNum=transaction_number

Display log records associated with the specified MQI transaction number in the format High.Low or High,Low.

XID=XA_transaction_identifier

Display log records with the specified XA transaction identifier in the format XA_FORMATID[a],XA_GTRID[b],XA_BQUAL[c] where [a] represents a signed 32-bit integer, and [b] and [c] represent a series of hexadecimal symbols (0-9, A-F). See the -z option.