Re: What's the proper way to "reraise" in a CLP?

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 06/16/2017
07:37:56 PM:

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.

Yes, sorry, I left out a lot of detail while presuming you were
familiar with at least some of it -- for example, message keys and where
to re-send the original escape message just to mention a couple. But, I
would like to point out Brian's post (quoted below) in case you missed the
point there. I asked if someone could correct what I originally posted
and I feel that his post is just such a correction. He seems to be saying
that -- using the condition handler mentioned -- you can get control
*before* the system issues the original exception message, examine the
diagnostics immediately, and then tell the system whether to actually
issue the exception message or not. This would be a much cleaner
solution, I think.


"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 06/15/2017
07:10:15 PM:

From: Brian Johnson <brian.johnson.mn@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/15/2017 07:11 PM
Subject: Re: What's the proper way to "reraise" in a CLP?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Register a User-Written Condition Handler (CEEHDLR)

A condition handler gets to decide if it wants to handle the exception.
This is the basic capability the OP needs.

I wrote one years ago that took in (via the TOKEN provided to CEEHDLR) a
list of message IDs that should be handled. This gave non-CL callers of
QCMDEXC (for example) a MONMSG-like capability.

Sincerely,

Dave Clark