Kisco Information Systems announces Release 2 of its system monitoring tool for the IBM i platform. iEventMonitor lets you watch your IBM i system for important events and then send out alert messages to let the right people know about the events in real time.
New with Release 2, Kisco has added Security Audit Monitoring to the package. This will let you set up monitoring and automatic notification when selected security audit events take place on the system. The feature integrates with the IBM i security audit journal for reporting security events. Event notifications can be in near-real time or done periodically throughout the course of a day.
In addition, new security controls have been implemented to provide access to the product for users who do not have all object authority. The allows specific user profiles to use the product without granting access to all users. Two levels of access are allowed, user and administrative.
Another new feature implemented for Release 2 is automatic restart for iEventMonitor Watch Tasks. These tasks let you set up watches on specific message queues in the system for specific message IDs. Previously, following an IPL, each watch had to be restarted individually. With Release 2, you can set these watches up for automatic restart. Then, by running a single start command, all autostart watches will start up at the same time with the same settings as before.
Also added to iEventMonitor since the initial Release 1 announcement are several abilities that customers have already been using via PTF updates. These include watching critical job queues to make sure that they don’t get backed up with jobs waiting to run and watching CPU utilization for jobs in a given subsystem to see if any jobs might be in a runaway state.
The core features of iEventMonitor have also been improved with Release 2. As always, it can watch any message queue in the system. This includes the critical QSYSOPR system operator message queue and the optional security event message queue QSYSMSG. A monitor can be set to watch for critical events based on a minimum severity level. When a qualifying message arrives at the message queue, iEventMonitor will send out an alert message. Provision is made to ignore true operator messages for things like forms changes and printer interventions.
Alerts can be sent as email messages, text messages or a break messages. Multiple recipients can be specified. For break messages, you just specify a user profile and the software checks to see if that user is signed onto the system before sending them a break message wherever they are working.
In addition to watching message queues, iEventMonitor can keep an eye on your system disc space. If that space varies up or down by a percentage that you specify, then an alert is sent advising that a critical disc space change has happened giving you time to react before a system shutdown.
You can also configure iEventMonitor to keep an eye on critical database files in your system. It can send alerts when records are added, changed, deleted or even just read. File alerts can be detailed (sent for each event) or summarized and only sent after each nth event.
iEventMonitor alerts can also be added directly into your own CL programs by using Kisco’s standard format commands for sending alerts.
The software is compatible with systems using IBM’s i/OS 6.1 software release and higher, including i/OS 7.2.
Complete product information is available at www.kisco.com/iem .
MC Press Online