Email Notification

Email Notification

Hi guys, Here is my CL program to monitor selected messages from QSYS/QSYSMSG and send email whenever such messages are received. I still have some more improvements in mind, but this should do quite nicely as a starting point for anyone else interested in this topic. By the way, lest you be misled, the built in time delay is arbitrary. It only determines how often the program checks for a shutdown condition. There is no delay-time involved in the detection and email of notices.

monsys.txt

Email Notification

Thanks David. But I was thinking of something much simpler and more focused on the intended function. Will get back to you next week.

[dchristie]

Email Notification

See This previous post on this subject.

Email Notification

Alan, Who said anything about Cobol? I develop all my utilities in RPG and CL. Anyway, I thank you for giving me the idea. I will be writing my own code to send me the email notifications. Until now, I have been relying on a small CL program that automatically sends me the whole QSYSMSG queue twice a week via snads. I suppose some people may think this stuff is so trivial, but when you are monitoring up to 15 remote AS/400s running different applications under different time schedules and with not so reliable communication lines the tediousness just piles up. If you have snads setup at your sites, I can give you the CL's source code. Or maybe latter next month, I should be finished with my new program to send email notifications. Just hope this forum is still open by then.

Email Notification

Hi Alan, I've setup monitoring on our systems that uses basic CL and REXX as the programming/scripting languages and it works well, so I don't think your not having COBOL will hurt you. There are always better ways of doing things of course. If you're not interested in programming, there are a number of products available that do the majority of the work for you (two that I've looked at are MessengerPlus and ICOM/400)...all you do is simply tell them what to monitor for, what to do when an event is encountered and they take care of the rest. You'd have to weigh the software cost against how much of the available functionality you'd actually use (and how long it would take/how much it would cost to have your staff write your own code). In both solutions (purchased or home-grown), you still have to research what you want to monitor for to support your environment. Good luck and I hope this helps, Steve Carvaines

Email Notification

I appreciate your response however it poses two problems for me. One, we do not have Cobol we have RPG and two I cannot write code. I guess I was hoping to find a simpler way to do this. Thanks anyway.

OS/400 puts critical messages into the QSYS/QSYSMSG message queue. If I were you, I would code a program to check this message queue and filter out those message-ids that require immediate attention. These selected messages should then be emailed to me asap. For course some kind of control (example: compare date/time of last extraction)is needed to make sure I do not get the same message over and over again. Some checking for duplicate messages would be nice too (to avoid redundant emails) Some of these messages-ids are: CPF1393 - Subsystem ... disabled user profile ... on device ... CPF0907 - Serious storage condition may exist. Press HELP. CPI099C - Critical storage lower limit reached. CPPEA05 - *Attention* Contact your hardware service provider. CPI1165 - One or more device parity protected units still not fully operational. CPI1166 - Units with device parity protection fully operational. Just remember, this is basically a short-listed set of alerts. Once in a while, you should still go in and take a hard look-around for problems.