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.
Register your E-mail address to receive automatic notification when this product is updated.
Index:
iEventMonitor Release Independent Problem Reports:
iEventMonitor Release 7 Problem Reports:
iEventMonitor Release 6 Problem Reports:
iEventMonitor Release 5 Problem Reports:
iEventMonitor Release 4 Problem Reports:
iEventMonitor Release 3 Problem Reports:
iEventMonitor Release Independent Problems:
iEventMonitor seems to have stopped working.
We recommend a full reset of iEventMonitor to see if that resolves this issue.
You can do the reset using the following process:
If this does not resolve your issue, contact support@kisco.com
Some email alerts going to Gmail users are being rejected by Google with the message "550 - Messages missing a valid messageId".
If you are using the SNDSMTPEMM option (on the IEMSET settings), this can happen and is an issue in the IBM i OS, not in iEventMonitor. IBM now recommends PTFs for OS releases 7.3, 7.4 and 7.5 to address this problem. If you are having this issue, please install the following IBM PTFs on your system:
My test email is not going through - when I look at the joblog, I see "Command failed. reason -108 failed to retrieve path information (PATH-/TMP,3525:Object is too large to process.)
The 108 code indicates that either the /TMP folder in the IFS does not exist on your system or that when you ran your test SNDALERT, it was locked and unavailable.
If it does not exist, all you need to do is create it. You can do so with the following command:
MD DIR(tmp)
If it was locked because of a save operation running on the folder, then it should work once that save has completed.
The message queue watch process has stopped working following a system error associated with the watch process.
There are several reasons possible for the message queue watch to stop working. To do a full reset of all iEventMonitor processes, issue the ENDIEM command from the IEMLIB library and then wait for the IEMONITOR subsystem to end. Once you have confirmed that the subsystem has ended, issue the STRIEM command, also from the IEMLIB library, to restart all iEventMonitor tasks. Issuing the STRIEM command when the subsystem is not running will force all internal settings in iEventMonitor to reset during the startup.
In some cases, however, this will not resolve an issue with the message queue monitor not responding to messages in the message queue. When that happens, the IBM i OS watch API process may need to be reset. The easiest way to do this is to IPL your system, but doing an IPL is not always convenient.
IBM appears to be aware of this issue and they have published the following support article with a manual recovery process that you can use:
https://www.ibm.com/support/pages/watch-programs-stopped-working
We have had mixed results when using this process. You should be aware that some system functions use the watch API process and this manual reset calls for you to manually end them all. You may need to contact IBM support to get those processes restarted correctly.
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 iEventMonitor 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 7 Problem Reports:
1 - When IEM was left running for a long period of time on a system with a lot of alerts being issued, it could fail because a limit on profile swaps was reached. This has been corrected.
2 - The size of the joblog on some tasks has been reduced to improve performance.
3 - A new parameter was added to the command that sends diagnostic information to Kisco for support purposes.
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 7.05. The correction is available in PTF package IEPTF706. E-mail support@kisco.com to request the PTF package.
Issue with duplicate message queue alert suppression
In some cases, the duplicate message queue alert feature would not work when it has clearly been activated. This could happen when the customer was specifying SNDSMTPEMM email delivery protocol.
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 7.00. The correction is available in PTF package IEPTF701. E-mail support@kisco.com to request the PTF package.
iEventMonitor Release 6 Problem Reports:
The Output Queue Watch feature could fail with the MCH1210 message if there were an unusually high number of spool files in the monitored output queue. This has been fixed.
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 6.03. The correction is available in PTF package IEPTF604. E-mail support@kisco.com to request the PTF package.
The message queue monitor reminder option was issuing reminder alerts for messages that were already answered under certain unusual situations. This has been addressed.
The WRKIEM process (option #1 on the MASTER menu) has been updated to perform a software license validation each time it is used. This will advise customers with the software on trial when the trial period has expired.
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 6.02. The correction is available in PTF package IEPTF603. E-mail support@kisco.com to request the PTF package.
On some systems, the Audit Monitor could experience a problem with a data queue read. That read has been changed to check for an error and deal with it without interrupting the process.
The Network Watch has been corrected to prevent looping when a total loss of network connection is experienced.
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 6.01. The correction is available in PTF package IEPTF602. E-mail support@kisco.com to request the PTF package.
corrects a problem with a CPF1015 that could happen on a message queue monitor when the reminder option was specified
The fix for these issues is available as a PTF. This PTF can only be installed on iEventMonitor Release 6.00. The correction is available in PTF package IEPTF601. E-mail us and request the PTF package.
iEventMonitor Release 5 Problem Reports:
Customers reported the following two issues with iEventMonitor:
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.24 version of iEventMonitor. The correction is available in PTF package IEPTF523. E-mail us and request the PTF package.
I am having problems stopping and starting some Job Watches.
A customer reported this problem when they were running multiple Job Watches for the same Job Name but different user profiles. We were able to identify the problem and correct it.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.23 version of iEventMonitor. The correction is available in PTF package IEPTF522. E-mail us and request the PTF package.
See details for several fixes.
Several customer have reported different issues which have now been fixed. These include:
These issues have all be corrected.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.18 version of iEventMonitor. The correction is available in PTF package IEPTF519. E-mail us and request the PTF package.
See details for several fixes.
Several customer have reported different issues which have now been fixed. These include:
These issues have all be corrected.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.16 version of iEventMonitor. The correction is available in PTF package IEPTF517. E-mail us and request the PTF package.
See details for several fixes.
Several customer have reported different issues which have now been fixed. These include:
These issues have all be corrected.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.14 version of iEventMonitor. The correction is available in PTF package IEPTF515. E-mail us and request the PTF package.
When I start a message queue monitor, it does not appear to be working.
iEventMonitor now uses the IBM i OS Watch exit program feature to monitor message queues. For this to work, the QUSRWRK subsystem needs to be up and running. On some systems, this is normally not started. We have changed the monitor startup process to make sure that the QUSRWRK subsystem has been started with the watch exit program prestart jobs also started.
The fix for this issue is available as a PTF. This PTF can only be installed on a Release 5.13 version of iEventMonitor. The correction is available in PTF package IEPTF514. E-mail us and request the PTF package.
See details for several fixes.
Several customer have reported different issues which have now been fixed. These include:
These issues have all be corrected or had work arounds added to the product.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 5.12 version of iEventMonitor. The correction is available in PTF package IEPTF513. E-mail us and request the PTF package.
We are missing an occasional message queue monitor alert.
Under certain conditions, especially when message queue entries have been manually removed from the message queue, we found that the IBM i OS API's for direct reading of the message queue had poor recovery abilities. To correct for this issue, we have re-engineered the Message Queue Monitor feature to avoid this from happening. The feature now uses a completely different method for monitoring message queues.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.11 version of iEventMonitor. The correction is available in PTF package IEPTF512. E-mail us and request the PTF package.
Our monitor stopped working with an error message about a file named IEMLOGF.
We found that a size restriction setting for the activity log file named could result in an error on systems with a lot of activity and where the file had not been purged to remove older records. We have now removed the size restriction on this file to avoid problems.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.09 version of iEventMonitor. The correction is available in PTF package IEPTF510. E-mail us and request the PTF package.
Several customer have reported different issues which have now been fixed. These include:
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 IEPTF508. E-mail us and request the PTF package.
Option #6 on the AUDIT menu fails.
If the iEventMonitor library named IEMLIB is not in the session library list, this option will not work correctly. This has now been corrected and a PTF update is available.
The fix for these problems is available as a PTF. This PTF can only be installed on a Release 5.06 version of iEventMonitor. The correction is available in PTF package IEPTF507. E-mail us and request the PTF package.
The ASP Watch only lets me specify up to ASP number 99.
A customer reported that they needed to watch an ASP with a three digit number. The IBM i OS supports using up to a maximum value of 255, so iEventMonitor has now been updated to support this full range of ASP numbers.
The fix for these problems is available as a PTF. This PTF can only be installed on a Release 5.05 version of iEventMonitor. The correction is available in PTF package IEPTF506. E-mail us and request the PTF package.
Several more fixes - see details.
Several customer have reported different issues which have now been fixed. These include:
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 customer have reported different issues which have now been fixed. These include:
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:
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.
© 2021 KISCO SYSTEMS LLC
54 Danbury Rd. | Suite 439 | Ridgefield, CT 06877
