× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Mon, Jun 19, 2017 at 9:46 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
On 6/16/2017 7:37 PM, John Yeung wrote:
So, nobody mentioned it explicitly, probably because it's too obvious
to everyone who knows what they are doing, but after further
experimentation it seems that the key to this is to specify
TOPGMQ(*SAME) when issuing the SNDPGMMSG that repeats the originally
caught *ESCAPE message.

Generally, I would send to *PRV; that is, to the caller.

That is the default, and I tried that as well as a few other
combinations. None of them do what I wanted, except for TOPGMQ(*SAME).
I hope it is clear that my paragraph quoted above is all about how I
established, *through experimentation* that TOPGMQ(*SAME) works for
me. It does what I wanted, at least on my system.

Sending it to
the program that just handled the message would result in a loop unless
there was code to detect that we've seen this one before.

Are you talking about global MONMSG? I'm only using MONMSG immediately
following a command that I know may fail. I'm not getting any looping
behavior.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.