If you want truncation: just use the old instructions; they still work like they used to do.

If you want to program around it:

IF FieldA * FieldB <= 99999 EVAL FieldC="FieldA" * FieldB ELSE do some error handling ENDIF 

If you want to handle it gracefully: use an exception handler.

---

AFAIK there is a special compiler option (which can be set in the "H" spec) which will activate the "old" method of truncating it. But a check with the %error function should work too (or not?).

---

Sorry, but "no" to both. The special compiler options you're probably thinking of (FLTDIV and EXPROPTS) only reduce the likelihood of overflow during expression processing by controlling the size of the temporaries used for sub-expressions. Even with these options, it's still possible to get overflow. %error doesn't act like MONMSG. You have to code an (E) extender on an opcode (not all opcodes allow it), and then afterward you can check %error to see if an error occurred. Just coding %error won't stop the exception. Joep already gave the possibilities for solving this: use the old opcodes if truncation really is a safe and correct thing to do, or use some form of exception handling (use an ILE condition handler, put the calculations in a subprocedure with its own *PSSR). -- Barbara Morris IBM Toronto Lab RPG Compiler Development

---