Re: Divide by zero and monitor group...

I have found that any errors captured by a monitor block end up in the job log. Dosen't make sense to me, but that is what happens. And as you have found out, there is not much difference between a handled error and one that is not handled.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Robert Rogerson <rrogerson@xxxxxxxxxxx> wrote: -----
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
From: Robert Rogerson <rrogerson@xxxxxxxxxxx>
Date: 07/01/2015 03:13PM
Subject: Divide by zero and monitor group...

Hi all,

I was somewhat surprised to find that a divide by zero error inside a
monitor group still wrote/added an error/message to the joblog. The
message I'm referring to is
MCH1211 Escape 40 Message . . . . : Attempt made to divide by zero for
fixed point operation.

I was pointed to this error as the reason for the program abending, but
when I checked (the specific line specified in the message) in the
program it was within a monitor group, so it was already being handled.
In the end the issue was elsewhere in the program.

With that being said, my question is, doesn't writing to the joblog take
up processing time and isn't this message misleading when the program is
already handling the error within a monitor group?
I know that checking the divisor before doing the divide operation would
avoid this issue, but I thought this was one of the purposes of the
monitor group.

Thanks,

Rob