Each day as the workload shifts, you can take down MQSeries, make the necessary parameter changes and then restart. Or, you can configure the system to optimize the processing for one shift or use an average set of parameters for both sets of users. Changing parameters will result in an MQSeries outage, while not changing parameters means that some users efforts will not be optimized. This means that an MQSeries outage is no longer required to make parameter changes to optimize conditions for users. Tuning for Workloads Active and Archive Logs MQSeries uses log files to track activity.
Several problems can occur with the logs.
First, if there are too few active logs, it is possible to overwhelm them with high update activity. If this happens, MQSeries stops processing until it has a chance to archive the active logs. In either case, you must make changes to fix the problem before MQSeries will begin processing again. Dynamically Adding New Active Log Files With dynamic tuning, you can deal with log file problems before they cause MQSeries to shut down. First, you can generate new active logs on the fly.