Re: "Monitor" does not monitor for RNQ0103 (target for numeric operation is too small)?

Yeah, depending on your company's interpretation, SOX compliance can be a
hassle. [?]

The reason for the extra variable was to reasonably not generate an error in
the first place. Also using *hival (and the extra field) to represent max
values of numeric data versus 99999 precludes you having to maintain the
code, even if the variable size changes (like if it's based on a database
field or something). Keep it in mind for future development -- it saves me
maintenance time when I write code that I don't have to worry about again!

Stu



On Wed, Sep 30, 2009 at 09:16, <KLockwood@xxxxxxxxxxxxxxxxxxx> wrote:

Thanks, Stu. It is kind of nice to know that "Monitor" SHOULD be catching
this error...

When I debugged through the code, "Monitor" did handle it correctly. Maybe
it was a bad compile?????

Also, thanks for your solution. I thought about it, but I hate to add
another variable just for this test - mostly because it is annoying to
have to work around something that SHOULD be working. I think I will wait
to see if it happens again. Sarbanes compliance makes minor program mods
like this a pain.

Kerry,

Here's how I might do it without regard to any status code.
Honest, I've never had an RPG run-time exception that monitor did not

catch.

----------------------------------------------

D MinutesLate S 5p 0
D realMinutes S 20u 0

MinutesLate = *hival;
realMinutes = *hival;

monitor;
realMinutes = %diff( %timestamp: LateTS: *minutes );
on-error;
endmon;

if realMinutes < MinutesLate;
MinutesLate = realMinutes;
endif;

----------------------------------------------

Ought not to cause any error ever.

Stu

Mr. Kerry Lockwood
Celadon Trucking, Inc.
9503 E. 33rd Street
Indianapolis, IN 46235
(317) 972-7000 ext. 2147
--
This is the RPG programming on the IBM i / System i (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.