. Kisco Home : products : iEventMonitor : Support : Problem Reports .
.
Page last updated on October 20, 2017

The following is a list of problems reported for iEventMonitor along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.

To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE.


iEventMonitor Problem Reports

Index:

iEventMonitor Release Independent Problem Reports:


iEventMonitor Release 2 Problem Reports:


iEventMonitor Release 1 Problem Reports:


iEventMonitor Release Independent Problems:

Following an IPL, I cannot start some iEventMonitor functions.

If some iEventMonitor functions are active when you do an IPL, this can happen. The easiest solution is to always shut down any active functions in iEventMonitor before you do an IPL.

If you do find that certain functions will not start, especially following an unscheduled outage on your system, please see the following:

If your message queue monitor job(s) will not start, then you just need to run the following command to clear a data area in the system:

CHGDTAARA DTAARA(IEMLIB/CONTROLMSG *ALL) VALUE(' ')

If your ASP% Watch function will not start, run the following command:

DLTDTAQ DTAQ(IEMLIB/TWCHASP)
If there are other functions that will not start, contact support at Kisco Information Systems for assistance.

Note: added May 10, 2017 - this issue was signficantly addressed in release level 2.05 (PTF IEPTF205). Updating your software to that level or higher will help.


My test email is not going through - when I look in the joblog, I see "Command failed. reason -301 negative response from SMTP server .... Relaying blocked at this site.

This message indicates that the SMTP server on your system is set to disallow email relays. For iEventMonitor's email to work, this will have to be changed. The setting is conrolled by the ALWRLY parameter (Allow relayed mail) on the Change SMTP Attributes (CHGSMTPA) command. Prompt this command using the F4 key and roll up until you see this parameter.

(Note: Your user profile must have special authority *IOSYSCFG to use the CHGSMTPA command. We recommend that you make changes to this command from a profile that is a security officer.)

When you first check this setting, you will probably find the ALWRLY set to *NONE. This will stop all iEvetMonitor email from being sent. Changing this value to *ALL will allow email to be sent, but it is not the best solution to enabling email. The preferred solution is to change this value to *LIST. This will restrict email relays to only those IP addresses that you specifically authorize.

Once you have relaying configured and have specified the *LIST setting, you will then have to update the SMTP list to indicate who can relay mail. This is done using the ADDSMTPLE (Add SMTP List Entry) command. There are a lot of options for this, but as a simple example letís set up an entry that will permit mail to be relayed from your IBM i (iSeries, AS/400). If your system has an IP address of 10.100.2.1, then you would add a relay accept transaction that looks like the following:

ADDSMTPLE TYPE(*ACCEPT) INTNETADR('10.100.2.1')
SUBNETMASK('255.255.255.255')
This entry will accept all SMTP mail that is sourced from the specific IP address indicated in the INTNETADR parameter. The subnet mask used here is coded so that only the specific IP address will be processed. You can also use this command to post a *REJECT entry to the SMTP list to indicate specific IP addresses to be rejected. Varying the subnet mask can let you define ranges of IP addresses and if you need help on how to code these entries, feel free to contact us (support@kisco.com). Once entries have been added to the SMTP list, you can delete them using the RMVSMTPLE (Remove SMTP List Entry) command. It would be nice if IBM provided a WRKSMTPLE command too, but the test system I work on has no sign of this feature.

After you get these changes made, you should end and then restart your SMTP server before testing for the results. Ending the SMTP server is done with the following command:

ENDTCPSVR SERVER(*SMTP)
and restarting it is done with the following:
STRTCPSVR SERVER(*SMTP)

iEventMonitor Release 2 Problem Reports:

  • Sometimes there is a time delay between when a message is posted to a message queue and when iEventMonitor sends us an alert about it.

    Sometimes there is a time delay between when a message is posted to a message queue and when iEventMonitor sends us an alert about it.

    Under certain unusual circumstances, we found a situation where the processing of messages arriving at a message queue could result in a delay in alert notification. This has now been corrected.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.10 version of iEventMonitor. The correction is available in PTF package IEPTF211. E-mail us and request the PTF package.


    I set up an exit program on a Watch Task, but the program is not running when the watch is satisfied.

    The exit programs all run in the IEMONITOR subsystem. If the subsystem was not running, the exit programs were stacking up in a job queue. We have modified the watch process to issue a start for the subsystem if an exit program is active for a watch task.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.09 version of iEventMonitor. The correction is available in PTF package IEPTF210. E-mail us and request the PTF package.


    I am seeing a CPF0804 error associated with a Watch Task.

    We found that when a Watch Task was set for a message ID with no associated data fields, this error could be issued. This has now been fixed.

    In addition, this fix includes a minor fix to clear up a working data area also associated with the Watch Task functions.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.08 version of iEventMonitor. The correction is available in PTF package IEPTF209. E-mail us and request the PTF package.


    Some functions will not start following an IPL.

    If you do an IPL without shutting down various monitor functions, restarting those functions could sometimes be a problem. With this change, steps have been taken to recognize when this has happened and adjust for it automatically.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.04 version of iEventMonitor. The correction is available in PTF package IEPTF205. E-mail us and request the PTF package.


    When starting an Audit Monitor, sometimes the EMAIL parameter is not being used.

    When starting an Audit Monitor from option 1 on the AUDIT menu (IAMSCAN), when the EMAIL parameter was changed from the default value to any other value, the monitor that started reverted to the default value. The monitor was started and ran correctly, but the notifications were not sent out according to the value entered. This has now been corrected.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.02 version of iEventMonitor. The correction is available in PTF package IEPTF203. E-mail us and request the PTF package.


    We are missing information on text notifications from watch tasks.

    Release 2 includes additional information on watch task notifications and this ended up overflowing for customers using text notifications. We have changed the format for watch task notifications to make them more compatible with text users.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.00 version of iEventMonitor. The correction is available in PTF package IEPTF201. E-mail us and request the PTF package.



    iEventMonitor Release 1 Problem Reports:

    The Utilization Monitor feature is failing with a PTF9845 error.

    For some customer, we found that when the Utilization Monitor feature was run for a long period of time with out ending it and restarting it. We have now fixed this problem and the Utilization Monitor feature can be run for a long period of time without interruption.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.14 version of iEventMonitor. The correction is available in PTF package IEPTF114. E-mail us and request the PTF package.


    I started a job queue monitor and it keeps reporting that there are more than 50,000 jobs waiting to run in that queue.

    We found that when a job queue monitor was started for a job queue that does not exist on your system, this could happen. iEventMonitor has now been updated to prevent a job queue monitor from being started when the job queue does not exist.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.13 version of iEventMonitor. The correction is available in PTF package IEPTF113. E-mail us and request the PTF package.


    Active monitors are ended when I end a message queue monitor, I want them to stay active.

    We have updated iEventMonitor so that the subsystem stays active until all monitor tasks running in the IEMONITOR subsystem have ended normally.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.10 version of iEventMonitor. The correction is available in PTF package IEPTF111. E-mail us and request the PTF package.


    The file monitor maintenance fails with MCH3401 when working on a summary report option.

    We found that there was a missing *PGM object in the distribution library that affected this. It has now been corrected.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.06 version of iEventMonitor. The correction is available in PTF package IEPTF107. E-mail us and request the PTF package.


    The message queue monitor start function is failing on a CPF0001 error.

    After installing a recent PTF update, a customer reported this problem. We discovered that a *CMD object distributed with the PTF/Version was pointing to an incorrect library. This has now been fixed.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.04 version of iEventMonitor. The correction is available in PTF package IEPTF105. E-mail us and request the PTF package.


    I am seeing message replies posted as alerts.

    A customer reported this to us and we found that it could happen when the message severity level is set a zero ('00'). The software has now been updated to suppress replies.

    The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.02 version of iEventMonitor. The correction is available in PTF package IEPTF103. E-mail us and request the PTF package.


    Contact Information
    Kisco Information Systems
    89 Church Street
    Mt Kisco, New York 12983

    Phone: (518) 897-5002 Fax: (518) 897-5003

    E-mail your questions or suggestions: Support@Kisco.com

  • .
    .
    Kisco Information Systems 89 Church Street Saranac Lake, NY 12983
    phone: 518.897.5002 | fax: 518.897.5003
    sales@kisco.com about kisco kisco products product support kisco consulting services useful links