example recovery scenarios, delays in off-loading, problem, active log, short of space on active log, CSQJ110E message, DEFINE LOG command, adding new active log, adding" />
Active log is becoming full
The active log can fill up for several reasons, for example, delays in off-loading and excessive logging. If an active log runs out of space, this has serious consequences. When the active log becomes full, the queue manager halts processing until an off-load has been completed. If the off-load processing stops when the active log is full, the queue manager can end abnormally. Corrective action is required before the queue manager can be restarted.
- Symptoms
Because of the serious implications of an active log becoming full, the queue manager issues the following warning message when the last available active log data set is 5% full:
CSQJ110E +CSQ1 LAST COPYn ACTIVE LOG DATA SET IS nnn PERCENT FULLand reissues the message after each additional 5% of the data set space is filled. Each time the message is issued, the off-load process is started.
- System action
- Messages are issued and off-load processing started, as detailed above. If the active log becomes full, further actions are taken. See Active log is full
- System programmer action
- Use the DEFINE LOG command to dynamically add further active log data sets. This permits WebSphere MQ to continue its normal operation while the error causing the off-load problems is corrected. For more information about the DEFINE LOG command, see WebSphere MQ Script (MQSC) Command Reference.