IBM MQ logging configuration for z/OS®

Store the queue manager log data sets and page data sets across multiple volumes. For optimal performance, store the logs on DASD volumes with low usage.

Also, use a DASD volume that is fast-write cache enabled, and ensure that the volume has an adequate cache size to reduce log I/O and improve performance.

Allocate enough primary space for the log data sets, with no secondary allocation. When the first log data set fills, IBM® MQ switches to the next available one. Always preformat the log data sets.

When you create the log data sets, dual logging improves the speed of recovery in a disaster scenario without adding significant performance costs versus single logging. In some MQ versions, all writes to dual logs are done in parallel if the primary log data set is on a write-cached DASD.

Use VSAM striped data sets for better performance. Switching to active logs that use VSAM striping can lead to improved throughput in situations where performance is being constrained by the log data rate.