Re: RCVMSG *DIAG (seemingly) not working

[Dan <dan27649@xxxxxxxxx>]

You mean, like yesterday?
https://archive.midrange.com/midrange-l/201705/msg00732.html

Must've blown right past that when I searched the archive for RCVMSG *DIAG.

Thanks!
- Dan

On Thu, May 25, 2017 at 7:03 PM, Kevin Wright <kevin.wright@xxxxxxxxxxxx>
wrote:

> Hi all,
>
> I thought that Rob Berendt recently (in the last week or so) posted most
> of a CL program that demonstrates how to do this.
>
> Overall, this is something like the structure of what can be done:
>
> Issue a program message to the current invocation stack, retrieving the
> message key as "from message key"
> Remove the program message just issued
> Perform the action that doesn't do messaging as you expected
> Issue a program message to the current invocation stack, retrieving the
> message key as "to message key"
> Remove the program message just issued
> Iterate from the "from message key" to the "to message key" as integer
> incrementing by 1
> Attempt to retrieve the message via the iterating message key
> If the message was retrieved and fits your criteria, do something with it.
>
> Don't ask me how I know this.
>
> Regards,
>
> Kevin Wright | IBM i Developer, LPC
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Nathan Andelin
> Sent: Friday, 26 May 2017 8:29 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: RCVMSG *DIAG (seemingly) not working
>
> I've put a few dozen hours recently into trying to understand call-stack
> message queues and how they work. It's something of a dark art. I never
> have figured out how to receive messages from call-stack entries that have
> already completed and returned control to your program. In your case the
> call stack pertaining to the SQL I/O, has already completed.
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD