Managing the logs

Managing the logs

Use this topic to understand how to manage your IBM MQ log files, including the log archiving process, using log record compression, log record recovery, and printing log records.

This topic describes the tasks involved in managing the IBM MQ logs. It contains these sections:

Archiving logs with the ARCHIVE LOG command
An authorized operator can archive the current IBM MQ active log data sets whenever required using the ARCHIVE LOG command.
Controlling archiving and logging
We can control compression, printing, archiving, recovery and logging with using the CSQ6LOGP, CSQ6ARVP, and CSQ6SYSP macros. Note, that changes to private objects only are logged in IBM MQlogs. Changes to GROUP objects (like shared inbound channels) are also logged, because the definitions are propagated around the group and held locally.
Discarding archive log data sets
We can discard your archive log data sets and choose to discard the logs automatically or manually.
The effect of log shunting
Long running transactions can cause unit of work log records which span log data sets. IBM MQ handles this scenario by using log shunting, a technique which moves the log records to optimize the quantity of log data retained, and queue manager restart time.
Resetting the queue manager's log
Use this topic to understand how to reset the queue manager's log.
Implementing the larger log Relative Byte Address
Before Version 8.0, IBM MQ for z/OS used a 6-byte log RBA to identify the location of data within the log. From IBM MQ Version 8.0, the log RBA can be 8 bytes long, increasing the period of time before we have to reset the log.
Parent topic: Managing IBM MQ resources on z/OS