Re: CL: Identifying the 'real' message. -- MIDRANGE-L

Subject: Re: CL: Identifying the 'real' message.
From: Ken Sims <mdrg8066@xxxxxxxxxxx>
Date: Wed, 17 Sep 2014 13:22:51 -0700
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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Rob -

On Wed, 17 Sep 2014 16:08:06 -0400, rob@xxxxxxxxx wrote:

Now I can take the &msgid from here.
Sure would make more sense if I could simply do the monmsg, receive the
exception, then receive the previous message. Just can't get the darn key
to work right with that logic though.

I really did research the archives. And Chuck seem to allude that the
technote shouldn't be necessary within the same program. I just couldn't
get anything else to work right.

I'm not where I can look at any of my own code, but if you receive the
msgkey of the exception message, and then specify that msgkey with
*PRV on the next RCVMSG, I think that will get the message that you
want.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.