Re: Can I monitor for a *DIAG msg?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Dean

You can't monitor for diagnostic messages. What you CAN do is use the 
technique of sending bracketing messages with message keys, then loop 
through them with a RCVMSG or QMHRCVPM and start at the lower key, go to 
the higher one. Then look for any message that matches your criteria and 
RMVMSG or QMHRMVPM (I think).

I posted a link to the article a couple weeks ago - 
*http://tinyurl.com/yzzq9yk points to it.

HTH
Vern
*
Dean.Eshleman@xxxxxxxxxxxxxx wrote:
> Hi,
>
> We have a production program that is generating multiple "Cursor MYCURSOR 
> not open" messages in the job log.  This message is a Diagnostic message 
> and has a message ID of SQL0501.  Can I prevent this message from showing 
> up in the job log by adding a MONITOR group in my RPG code around the code 
> that is trying to close the cursor?  I did notice that when I look at the 
> message details, it is being sent to program QSYS/QSQRUN4.  I suppose this 
> is another clue that I might not be able to monitor for it.  Our programs 
> always try and close the cursor before opening it just in case it was left 
> open for some strange reason.  Maybe I need to look at that logic more 
> closely.  TIA
>
> Dean Eshleman,
> MMA, Inc.
>
> ______________________________________________________________________
> Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information.  If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmissions errors in the future. Thank you. 
>