Re: Sending Escape Message from service program withoutkilling it with MCH3402

*DIAG is not cause the program to fail, meaning it is not executing the
on-error routine for application that monitor for error. For
application that not monitor for error, the *DIAG message is not causing
the program to fail.

"Carel Teijgeler" <coteijgeler@xxxxxxxxx> wrote in message
news:<mailman.2190.1224093306.30674.rpg400-l@xxxxxxxxxxxx>...

You can change the exception error mesage to a diagnostic message.

there is

an API for that.

I tested this many years ago, and IIRC it even worked on "divide by
zero"-errors ( no error message screen).

Hope this helps.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 15-10-2008 at 10:17 Lim Hock-Chai wrote:

I've an export procedure in a service program that will send an

*ESCAPE

message to the caller when encountered a particular type of fatal

error.

The caller has a choice of monitor for the *escape message or, in

most

case, just error out. I'm having a problem on caller that monitor

for

the *escape message. When the *escape message is monitored by the
caller, subsequent call from the caller to the procedure in the

service

program is being error out with MCH3402. Is there a way to get

around

this?


thanks
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing

list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


No virus found in this incoming message.
Checked by AVG.
Version: 8.0.101 / Virus Database: 270.8.0/1723 - Release Date:

13-10-2008

18:42