Re: The target for a numeric operation is too small!!!!!

>
>All he is asking for is the ability to minimize the damage!  The program
>should HALT but you should be able to continue processing once you have
>identified the problem.

Really? Minimize the damage?

Many years ago, when i was responsible for running such jobs "bombing" with 
division by zero (there were some :-),
i had to find the cause, restore to a saved status and re-run the job. With 
save files nowadays, this should be much faster and easier.

 From experience: the consequences of such errors are seldom investigated 
deep enough when there is an I option, and correcting that, some time 
later, is much more work & pain. And users are willing too easily to enter 
n1 to n2 times "I" before they finally cancel, which is also not minimizing 
the problem.

Possibly better than ignoring might be starting a debug session and guiding 
the program execution through the wild, providing proper values. I didn't 
try it now, but i do think that it is possible to start the debug, set a 
break point, enter a "G" and do the rest in the debugger. (I bet that this 
program (still) has it's observabilities... :-)

Pretty the same work as correcting it.

So i still think that it is quite good and
Mit freundlichen Grüssen / Best regards

Anton Gombkötö
mailto:Gombkoetoe@ASsoft.com

AS Software GmbH
http://www.assoft.com

Jedleseer Strasse 3
A-1210  Wien

Tel: +43 1 278 15 01-0
Fax:+43 1 278 15 01-22

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---