|.||  Kisco Home : products : iEventMonitor : Support||.|
Page last updated on February 23, 2019
The following is a list of frequently asked questions about iEventMonitor. If you have a
question that is not covered here, ask us via
To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE.
iEventMonitor Frequently Asked Questions:
Some customers may choose to use multiple monitoring software products concurrently. The reminder alert process uses the QIBM_QMH_REPLY_INQ exit point. If another software product has a program already registered to this point, iEventMonitor will not register its own exit program and, as a result, the reminder logic will not work correctly.
You can verify this by running the following instruction:
WRKREGINF EXITPNT(QIBM_QMH_REPLY_INQ)Place an 8 next to the displayed exit point to view the program(s) currently registered. If you find a program there, then this is why the iEventMonitor reminder is not working correctly.
To correct for this, shut down your message queue monitor in iEventMonitor for the message queue in question. Review the jobs running in the IEMONITOR subsystem and cancel any jobs shown with a job name that starts with REMxxxxxx. Then, run the following command from the command line:
CHGDTAARA DTAARA(IEMLIB/IEMCONTROL (628 4)) VALUE(X'00000002')This will change iEventMonitor to register its exit program in the second (2) seat for the exit point. Once this change has been made, you can restart the message queue monitor with the reminder option active. If you view the exit point programs again, you will see two programs registered to the exit point.
For customers who have Release 2 or later of iEventMonitor installed, this is taken care of by granting permission using option #8 on the INSTALL menu.
The following response applies only to customers with release 1 of iEventMonitor installed.
As shipped from Kisco, iEventMonitor can only be used by someone with *ALLOBJ authority. This is typically a security officer like QSECOFR. You may not want to grant such a high level of authority to someone who legitimately needs to be able to administer iEventMonitor.
In a future release, Kisco will be making this process easier, but for now you can accomplish this by just granting access rights to the library and objects for the specific user in question.
To grant the necessary permission, just run the following two commands, changing the lower case values to the appropriate values for your situation:
GRTOBJAUT OBJ(QSYS/IEMLIB) OBJTYPE(*LIB) USER(myuserid) AUT(*USE)Once this has been done, then the user specified will be able to use the software. If you have several users where you want to set this up, consider creating a group profile and assigning them all to the group. If they are already part of a group, a supplemental group will also work.
Yes, you can.
When a user profile becomes disabled, the IBM i OS sends a status message to the special message queue named QSYSMSG in library QSYS. If your system does not have this message queue, you can create it as it is a user optional message queue. To create it, use the following command:
CRTMSGQ MSGQ(QSYS/QSYSMSG) TEXT('System Security Message Queue')Once the message queue has been created, set up a monitor for it in iEventMonitor and check for all messages from severity level zero and higher. All important security events will be reported to this message queue including user profiles that become disabled due to using incorrect passwords too many times.
Watch tasks end when you do an IPL or when you bring your system into restricted state. Following either of these events, they need to be restarted. You can do this, for both situations, by updating your system startup up program (system value QSTRUPPGM). In your startup program, you will need to add the following command:
CHGDTAARA DTAARA(IEMLIB/TWCHLOG) VALUE(' ')This will clear the watch task registry area. Once this is done, then you can restart the specific watch tasks you want active by issuing the "Start a Watch Task" command (STRIEMWAT) from the iEventMonitor application library named IRMLIB. You can issue this command multiple times, once for each watch that you want to activate.
Check with your cell phone provider to find out the email address format that you should use and then just configure iEventMonitor to use that email address. For example, we use Verizon Wireless here at Kisco Information Systems. Verizon supports sending an email to a Verizon Wireless smartphone by using the email address format of: [areacode+phonenumber]@vtext.com. If your phone number is 518-555-1111, then the email address at Verizon Wireless would be "email@example.com". Just use this email address in iEventMonitor and you will get a text message for the alert notification.
Here are the email to text formats currently available for the most common cell carriers available in the USA:
iEventMonitor includes a built-in command that you can call from your own applications to issue alerts using the methods and delivery implemented by iEventMonitor.