Re: Removing a message from the job log

Duane

I might agree with you, but after being bit by odd messages sent from various places, I like bracketing like this. It gets me every message that the job gets, no matter where from, and it's easy to have a procedure you call to do the bracketing and that returns the key, then another procedure to check things.

But if you can trust the process, that's cool.

Vern

Christen, Duane wrote:

Dean;

For this just do a QMHRCVPM call for the last message, of any type, right after the close cursor if the sqlstt is not 00000. There is no need to "peg" both sides of the message, as there is only going to be one if the close failed.

Duane Christen


--


Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx

Visit PAETEC.COM


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dean.Eshleman@xxxxxxxxxxxxxx
Sent: Wednesday, April 01, 2009 1:38 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Removing a message from the job log

Vern,

Thanks for the tip. I never would have thought of that option. I'll check it out.

Dean Eshleman,
MMA, Inc.

On Wed, 01 Apr 2009 12:17:39 -0500, in midrange.midrange-l you wrote:

Dean

An old but venerable technique is to send a message before a process with a msg key, do the process, then send another message with a msg key
- you have to receive both to get the keys. Then you loop between the keys and check for the ID you want to remove - very fast, cuz it encompasses very few messages. It doesn't matter where the messages came from.

Here is a link to the IBM document with how to do this. It has examples in CL and C - use the C example to see how to call the QMHRCVPM API by key for this process.

*http://tinyurl.com/d4a6xx

*HTH
Vern

Dean.Eshleman@xxxxxxxxxxxxxx wrote:

I have an SQLRPGLE program that executes a close cursor instruction at

the

beginning of the program. Sometimes, this generates a message in the

job

log "Cursor SQL_EXTRACT not open." I would like to remove the message from the job log when this happens. However, I'm not sure if I can.

When

I look at the details of the message, the from program and to program

are

both QSQRUN4 which is probably below my program in the call stack. I tried using the QMHRCVPM API to retrieve the message, but no luck. Can

I

remove this message?

I guess my other option is to prevent the message in the first place. I

guess I'll look into that as well.

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.
______________________________________________________________________
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. --
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.