. Kisco Home : products : iEventMonitor : Support : Problem Reports .
.
Page last updated on June 25, 2020

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 5 Problem Reports:


iEventMonitor Release 4 Problem Reports:


iEventMonitor Release 3 Problem Reports:


iEventMonitor Release 2 Problem Reports:


iEventMonitor Release 1 Problem Reports:


iEventMonitor Release Independent Problems:

I'm implementing the IEM Respond feature. The test page comes up after I've completed setting up the HTTP Server Instance, but when I test the feature using the test option, I get an "Internal Server Error" in the browser session. Looking in the server error logs, I can see a ZSRV_MSG0947 error code.

We have seen this for a few customers. First, check to make sure that the HTTP Service Instance was installed according to our instructions and that no short-cuts or alternative methods were used. If that checks out and you still have this problem, then it is most probably a security issue for accessing the application library named IEMLIB.

You can resolve this by running the following two commands:

GRTOBJAUT OBJ(QSYS/IEMLIB) OBJTYPE(*LIB) USER(QTMHHTP1) AUT(*USE)
GRTOBJAUT OBJ(QSYS/IEMLIB) OBJTYPE(*LIB) USER(QTMHHTTP) AUT(*USE)

Once this has been done, end and restart the IEVENTMON server instance and try the failing link again.


My test email is not going through - when I look in the joblog, I see "Command failed. reason -203 failed to connect remote server (connect(), 3425:A remote host refused an attempted connect operation.

This message normally indicates that a validation process back to your IBM i system is failing. The first place to look for this is the email help available at this location. If the PING command works and the address is reachable, then the problem may be caused by using a non-standard port number for SMTP on your IBM i system. The default port value of 25 is normally used and is the default value used by iEventMonitor.

You can check the port number being used on your system with the following command:

WRKSRVTBLE SERVICE('smtp')
If you need to change the default port number for iEventMonitor on your system, it is stored as a hexadecimal value in positions 796-800 of the data area named IEMCONTROL in library IEMLIB. The default value for port 25 is shipped with iEventMonitor stored as X'0000000019'. If you need to change this value, determine the correct hexadecimal value to use and change the value using a CHGDTAARA command such as this:
CHGDTAARA DTAARA(IEMLIB/IEMCONTROL (796 5)) VALUE(X'0000000019')
If you change the default port value, you should end and restart the SMTP server.
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, if you decide you don't want to use the software, you can delete them using the RMVSMTPLE (Remove SMTP List Entry) command. It would be nice if IBM provided a WRKSMTPLE command, 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 5 Problem Reports:

Several more fixes - see details.

Several customer have reported different issues which have now been fixed. These include:

  1. Some messages arriving at a message queue were generating alerts in iEventMonitor. This has now been corrected.
  2. The user profile watch was not always honoring the shift times and days as posted in the IEMSET command. This has been corrected.
  3. Under unusual conditions, the IEM Respond process that generates a joblog of the job with the error message could fail when the message is manually responded to before the joblog processing completes. This has now been fixed.
  4. The message date and time has now been added to the detail display for the history log.

The fix for these problems is available as a PTF. This PTF can only be installed on a Release 5.02 version of iEventMonitor. The correction is available in PTF package IEPTF504. E-mail us and request the PTF package.


Several fixes - see details.

Several customer have reported different issues which have now been fixed. These include:

  1. A problem with the new Test Error Message function was fixed. It was failing when the IEMLIB library was not in the session library list.
  2. A fix was made to the message queue monitor function. It was calling the IEM Respond setup process when a message did not call for a response.
  3. One customer reported an MCH3601 error from program UTIL21. This has been identified and corrected.
  4. Some customers reported that option #1 on the MASTER menu was showing that the ASP Watch was inactive when it was actually running.
  5. One customer reported that a file named WEBPRINT was not allocated with enough records for a specific situation they encountered. The file has now been enlarged.
  6. The Reminder Option was causing errors when a value larger than 99 was entered.

The fix for these problems is available as a PTF. This PTF can only be installed on a Release 5.02 version of iEventMonitor. The correction is available in PTF package IEPTF503. E-mail us and request the PTF package.


We are seeing multiple SV Audit Alerts for time adjustments.

Some systems are configured for automatic time adjustment. These changes are reported as System Value changes and can happen regularly. We have now updated the SV Audit Watch to ignore all time adjustment changes and stop issuing these as alerts.

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


iEventMonitor Release 4 Problem Reports:

Three changes for iEventMonitor.

The following three changes have improved iEventMonitor:

  1. The ASP% Watch has been enhanced to now allow for iASPs from number 33 to 99 to be monitored.
  2. The IEMSET process (option #9 on the INSTALL menu) has been fixed. Under certain conditions, the optional header and trailer information along with the off-shift days could not be updated.
  3. The reminder alert process has been improved to better work with automatic system replies.

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


We can only start 25 Job Watch tasks. Is that the limit?

The limit for Job Watch tasks is 50, but we discovered that there was an issue that was limiting the number of Job Watch tasks to 25. This has now been corrected.

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


We are seeing error code MCH0603 issued from program IEMONCLT.

We found that under rare situations, this could happen and it has now been corrected.

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


We are having two problems with Watches not running correctly.

Two intermittent problems were discovered in the Watch function. First, some Watches were not getting restarted with the correct exit point level parameter set. The other problem was that some Watches were ended before they were stopped by the customer. Both issues have now been corrected.

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


We want to run a large number of Watches, but when we start more than 32, the new Watches fail to start.

The first implementation of the Watch feature had a limit of 32 concurrent Watches. As of this change, this limit is raised to 1,600 Watches.

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


The RUNCHK option on the Job Watch only allows for a maximum value of 999 minutes.

A customer reported that this limitation affected them. We have expanded this value to allow up to 1440 minutes which translates into a full day (24 hours).

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


A utilization monitor is showing as "Inactive" when it is actually active and working.

When a utilization monitor was started to watch *ALL subsystems, it would show as "Inactive" when displayed using option #1 on the MASTER menu. The monitor was running correctly, just not showing the correct status. This has now been fixed.

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


The message queue reminder option, when activated, sends reminder alerts even after a message has been answered.

We found that for certain customer, under unusual circumstances, the reminder alerts could be sent out over and over again even after the message was answered and cleared. The issue was traced to an exit point registration failure. This has now been corrected.

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


Sometimes, the &JOBNO macro function on the Alert Subject Text for the message queue monitor does not work correctly.

The &JOBNO macro function for the Alert Subject Text on the message queue monitor will now always report the correct job number information.

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


Sometimes, the macro function on the Alert Subject Text for the message queue monitor does not seem to work.

We found that when you specify a macro function with the Alert Subject Text and also specify start and stop notification, then the macros were not resolved on these start and stop alerts. This has now been fixed.

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


The lock-wait fails when set for all users and all types.

We found that this could happen on larger systems with a high number of active tasks. We have now re-engineered the lock-wait watch to work without issuing an error message.

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


A user watch is failing to start.

The customer who reported this problem was monitoring the message queue for the user profile that they then wanted to watch with the User Profile Watch feature. We have now re-engineered the user watch feature so that it can support this concurrent process.

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



iEventMonitor Release 3 Problem Reports:

The Lock Wait Watch function is not reporting a lock wait situation.

We discovered that when the Lock Wait Watch was used for *ALL job types and *ALL user profiles, an internal table within iEventMonitor was not large enough to process correctly. This has now been corrected.

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


Occasionally, not all tasks are ending when we run the ENDIEM process.

While using iEventMonitor in our shop, we discovered that an unusual sequence of events could result in the ENDIEM process failing to shut down all active monitor and watch tasks as designed. This has now been corrected.

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


Restarting all monitors and watches following an IPL will fail sometimes.

If the monitors and watches were not shut down normally prior to the IPL, this problem could happen when you have either the output queue watch, MX Wait watch or Lock Wait Watch active. This issue has now been corrected.

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


The output queue monitor is failing intermittently.

This problem has now been corrected. Also, with this fix, we have expanded the code description on all Audit Alerts. Prior to this change, just the audit code was shown in the base alert message.

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


I specify to be reminded about unanswered messages, but the reminder jobs sometime fail and at other times they fail to end.

We discovered that the reminder feature needed a little tweaking. The reported issues have all now been corrected.

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


When I change the settings for a task and press ENTER, the changes are not saved.

A customer reported this issue after upgrading to release 3.15. We have now identified the cause and fixed it.

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


The message queue monitor is constantly running and will not stop when I run the option to stop it.

A customer reported this issue after upgrading to release 3.11. We have now identified the cause and fixed it.

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


Message queue reminder issues resolved.

Several issues with the message queue reminder feature have now been corrected. The process will now ignore messages that have been set up with automatic replies from the system reply list or that are set for a default reply. The message queue monitor will also not allow message removal (*RMV) when a reply reminder is also specified when the message queueu monitor is started.

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


Only one Job Watch is being stored for a given user profile.

A customer wanted to watch jobs with the same job name being run by different user profiles. iEventMonitor allowed these to start but the STRIEM/ENDIEM process was only supporting a single job for a given job name. This has now been fixed.

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


The automatic watch startup is failing on a Job Watch function.

We found that when multiple Job Watches were set, then the shut down process was not clearing certain indicators on the system. This was causing the subsequent startup process to fail. This has now been corrected. Users not using the Job Watch function were not affected.

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


The "Work With Authorized Users" option on the INSTALL menu (option 8) fails immediately.

The most recent CD master for iEventMonitor was missing a program object needed for this function. It has now been restored to the application library.

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



iEventMonitor Release 2 Problem Reports:

iEventMonitor fails when starting an Audit Monitor.

We found that an Audit Monitor task would fail on any system running with a date format other than *MDY. 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 IEPTF212. E-mail us and request the PTF package.


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