Plan your logging environment

Use this topic to plan the number, size and placement of the logs, and log archives used by IBM MQ .

Logs are used to:

  • Write recovery information about persistent messages
  • Record information about units of work using persistent messages
  • Record information about changes to objects, such as define queue
  • Backup CF structures

and for other internal information.

The IBM MQ logging environment is established using the system parameter macros to specify options, such as: whether to have single or dual active logs, what media to use for the archive log volumes, and how many log buffers to have.

These macros are described in Create the bootstrap and log data sets and Tailor the system parameter module.

Note: If we are using queue sharing groups, ensure that you define the bootstrap and log data sets with SHAREOPTIONS(2 3).

This section contains information about the following topics:

  • Log data set definitions
    Use this topic to decide on the most appropriate configuration for the log data sets.
  • Use MetroMirror with IBM MQ
    IBM Metro Mirror, previously known as Synchronous Peer to Peer Remote Copy (PPRC), is a synchronous replication solution between two storage subsystems, where write operations are completed on both the primary and secondary volumes before the write operation is considered to be complete. Metro Mirror can be used in environments that require no data loss in the event of a storage subsystem failure.
  • Plan your log archive storage
    Use this topic to understand the different ways of maintaining your archive log data sets.
  • How long do I need to keep archive logs
    Use the information in this section to help we plan your backup strategy.
  • Plan to increase the maximum addressable log range
    We can increase the maximum addressable log range by configuring your queue manager to use a larger log relative byte address (RBA).

Parent topic: Plan for the queue manager