Re: Can you find it out?

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

Bryan Yates wrote using HTML:

-snip about overflow error-

>If you are using RPGIII then you need 
>to code an indicator in LO for each write
>operation to the print file, monitor for 
>this indicator on after a write to know 
>when to put your headings out.
>
>If you are using RPGIV the use the Write(E) 
>opcode and monitor for %ERROR to trap
>overflow.

Please be aware that there are other error conditions that will trigger the
error indicator besides overflow.  Unprintable character, invalid character
in barcode, etc.  Also, logging these errors to the job log will degrade
performance noticeably.  Sure, use the error indicator, but use it for
errors, not overflow detection.

Brad's suggestion of detecting overflow before you print a line is good, as
is using an overflow indicator to "normally" handle overflow.  For external
printer files, use a numeric indicator in the F specs instead of OF.

Buck Calabro
Aptis; Albany, NY
"We are what we repeatedly do.
 Excellence, then, is not an act, but a habit." --Aristotle


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| 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
+---