Can I monitor for a *DIAG msg? -- MIDRANGE-L

Subject: Can I monitor for a *DIAG msg?
From: Dean.Eshleman@xxxxxxxxxxxxxx
Date: Fri, 5 Mar 2010 14:40:46 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Can I monitor for a *DIAG msg? , Graap, Kenneth
Re: Can I monitor for a *DIAG msg? , Vern Hamberg

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.