Logger event generation
Use this page to view the situations that cause logger events to be generated and to understand the circumstances in which logger events are not generated
A logger event message is generated in the following situations:
- When the LOGGEREV queue manager attribute is specified as ENABLED and the queue manager starts writing to a new log extent or, on IBM i, a journal receiver.
- When the LOGGEREV queue manager attribute is specified as ENABLED and the queue manager starts.
- When the LOGGEREV queue manager attribute is changed from DISABLED to ENABLED.
- When the LOGGEREV queue manager attribute is notified that the name of the oldest log extent, for which the queue manager is waiting for archive notification (ARCHLOG) has been archived.
Tip: We can use the RESET QMGR MQSC command to request a queue manager to start writing to a new log extent.
When logger events are not generated
A logger event message is not generated in the following circumstances:
- When a queue manager is configured to use circular logging.
In this case, the LOGGEREV queue manager attribute is set as DISABLED and cannot be altered.
- When a queue manager encounters an error trying to put a logger event on the event queue, in which case the action that caused the event completes, but no event message is generated.
Parent topic: Logger events
Related concepts
Related information