Re: QRCVDTAQ

Steve Richter wrote:

modules have to throw exceptions. that's my rule! ahem.

How?
RPG doesn't have a mechanism to throw exceptions.  At least not the RPG
I work with (which is, by necessity, a few releases back from the
current GA version).

I use the QMNSNDPM api.  It sends and *escape message up the call stack.

I haven't observed that to be an well used technique.  Sending escape
messages in CL is common, but not in RPG.

In RPG I use MONITOR to catch exceptions and QMNSNDPM to throw them. (
actually in practice I throw exceptions a lot more than I catch them.
I worry too many MONITOR blocks will slow the code.down. )

Since RPG doesn't have the native ability to send a message, I think
that MONITOR is pretty much a waste of time.

I agree that if you code the dtaq application properly you will not
have any out of the ordinary problems.

As always, the technique you use should be based on the problem you are
trying to solve ... and regardless of the technique you use, it can
always be coded poorly or well.

david