How do you raise alerts based on the Job Log of active jobs currently running on your IBM i? How do you ensure that routine jobs run without any catastrophic error?

For example; A critical job may look to be running okay to the untrained eye – it’s active, it’s not consuming an excessive amount of CPU and isn’t in message wait (MSGW). But internally (in the joblog) it could be generating spurious escape messages indicating access to a SQL database is no longer possible. These messages would not appear on any message queues or history logs, but it will be clearly visible in the Job Log. Using the Halcyon Job Log Monitor makes it easy to track down and monitor these messages.

Job Log Monitor has been made available as part of the Message Manager Product via CHG0657. Its purpose is to look at the Job Logs of currently active jobs and Alert based on the messages contained within. Job Log Monitor allows you to create Rules to identify the Jobs to be monitored by “Job name”, “User name”, “Subsystem” and/or “Job type”:

Setting Job Log Criteria

plus the messages to be monitored for including “MessageID”, “Message file”, Message type” and/or “Message severity”:

Specifying Message Criteria

When found it then Alerts, performing the Actions defined on the Rule:

Display Alert Detail


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: January 03, 2019