Logger events

Logger events are notifications that a queue manager has started writing to a new log extent or, on IBM® i, a journal receiver. Logger event messages are not available with IBM MQ for z/OS®.

The event data contains the following information:

• The name of the current log extent.
• The name of the earliest log extent needed for restart recovery.
• The name of the earliest log extent needed for media recovery.
• The directory in which the log extents are located.
• The name of the earliest log extent for which archive notification is required.

  From IBM MQ Version 9.0.2, a logger event is generated for archive log management, that is, when ARCHLOG changes, and the ARCHLOG value will be included the logger event message.

  See DISPLAY QMSTATUS for more information on all these parameters.

  We can use the CURRLOG and ARCHLOG values to determine what should be archived. Whenever CURRLOG changes, files with numbers less than CURRLOG can be sent for archive and, once archiving has been completed for the extent, you should call SET LOG to notify the queue manager.

  If the program has stopped, we can use ARCHLOG to determine the oldest log extent that the queue manager is still waiting for information about.

  Once SET LOG has been called for this extent a new event is issued, as ARCHLOG will have changed, and you need to know what needs to be archived after the new event.

  If for some reason your archiving process fails, and a big build up of notifications happens, your administrator can manually issue the command RESET QMGR. This allows extents to be reused or deleted.

Every logger event message that is generated is placed on the logger event queue, SYSTEM.ADMIN.LOGGER.EVENT.