Help required in writing a CL program which will monitor QSYSOPR msgq for specific h/w failure msg ID’s and shoot email ?

30 pts.
Tags:
CL Program
CL/400
OS/400 and iSeries
Hi All – Could any one help me in writing a CL program which will monitor the QSYSOPR msgq for specific h/w failure MSGID's and shoot email ? Regards, Madhu

Software/Hardware used:
AS400, iSeries

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    First, QSYSOPR shouldn't be monitored for critical messages such as hardware failures. Those messages shouldn't be sent to QSYSOPR; they should be sent to QSYSMSG. In order to enable QSYSMSG, all you need to do is create a message queue named QSYSMSG in library QSYS, and the OS will automatically use it for critical system messages.
    .
    Second, are you sure the program will be able to run after a hardware failure?
    .
    Third, IBM provides Example: Receiving messages from QSYSMSG. If you really want QSYSOPR, all that example needs is to use the other name. (It's not a good idea to use QSYSOPR.)
    .
    Fourth, we don't know how your system sends e-mail, so you'll have to do that part on your own. If you run into a problem, you can post your code and describe the problem. We can help when we know what some problem is.
    .
    Fifth, using Management Central is probably better than writing programming for this. Why write a program if the system will do it for you? You can find an example in Scenario: Message monitor. That example is about QSYSOPR and *INQUIRY messages, but a different name can be used and different messages can be listed.
    .
    Tom
    125,585 pointsBadges:
    report
  • Madhura0
    Hi Tom, Thanks a lot for your valuable inputs. Currently i am using message monitors in Management Central to alert me using SNDDST command when ever the specified message ID's occur in QSYSOPR. These monitors working absolutely fine till the monitors are in 'Started' status. But these monitors are not reliable as these are going to "Failed" status randomly. I don't even get proper solution also from IBM from past 6 months. so, I am looking for alternative solution. Now, I have created a session using the command STRWCH which monitors the message queue and call the program. The program contains only SNDDST command, but i dont see it is working.The below session is for testing. The session details : Session ID . . . . . : ALERTMON Started: Started by: Date . . . . . . . : 05/17/13 Job name . . . . . : QPADEV0008 Time . . . . . . . : 05:35:35 User . . . . . . . : QSECOFR Call exit program: Number . . . . . . : 034200 *WCHEVT Watch program . . . : ALERT Library . . . . . : MADHUTST Origin . . . . . . . : STRWCH Run priority . . . . : 25 Message Job Message queue Library name User Number CPIEF01 QSYSOPR QSYS Bottom Please suggest & advise if this approach works to monitor QSYSOPR (or) QSYSMSG. Rgs, Madhu
    30 pointsBadges:
    report
  • TomLiotta
    I don’t even get proper solution also from IBM from past 6 months.
    .
    I don't quite understand. Have you been trying for 6 months with Management Central (MgtC)? This question thread is only 11 days old.
    .
    You have the STRWCH command, so you are at least at V5R4, i.e., on a supported release. There are at least three elements needed to handle failed monitors properly on any current release.
    .
    First, there are PTFs. If you've been working with IBM, they should have verified that you have the appropriate ones installed.
    .
    Second, the MgtC Properties need the 'Automatically restart monitors on failed systems' option checked.
    .
    But the third element is a tricky one. The "Name" of the monitor needs to include the word "&RESTART". I'm not at all clear why that is a requirement, and it's not easy to find. (I'm not sure I can even find the documentation again.)
    .
    So, for example, I have a Message Monitor and its Properties show:
    .
    Name: Test &RESTART
    .
    When a failure occurs, it has no problem starting back up automatically. In my current setup, I'm running MgtC on V5R3 as the Central system, with V5R3 and 6.1 as Endpoint systems. If you have V5R4, it should work better (with any needed PTFs).
    .
    For STRWCH, I don't yet have good useful info on failures. I don't any history on failed watches yet, so there's not much I can say.
    .
    However, you need to understand that various failures are at least just as likely if you create your own function. And if you create your own, elements such as object (message queue) locks can cause problems.
    .
    Do you know anything about the causes of 'Failed' status? Are you running a single system or is it a network of AS/400s? If you have multiple AS/400s, what are the oldest releases you have?
    .
    Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following