Re: Overflow

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

I've come across this too, when using exception printing.  The page headings
are done automatically if you use the RPG cycle, but if you don't use the cycle,
things get a bit tricky.  Remember, that the overflow is checked onces per
cycle, and it is very possible to print more than one line per cycle (or this 
has
been my experience, if anyone has a better explanation, I would like to know
it).

One solution, I believe, is to check for overflow yourself.  Somethign like:
         Except SomeDetail
         If         *INOF
         Except  Headers
         Eval     *INOF = *OFF
         EndIf
         Except SomeDetail2
         If         *INOF
         etc...

As you can see, it becomes quite tedious to keep repeating this.  So, I
usually write a quick sub routine to check for overflow then I just say

        Except    SomeDetail
        ExSr       CheckOF
        Except    SomeDetail2
        ExSr       CheckOF

I am not sayign this is the best way to handle this situation, just that I've
done somethign similar in the past.  There may be a much better way, and
if so I would also like to know how to deal with it.

Regards,

Jim Langston

Hector Sanchez wrote:

> I have an RPG Report that at times prints passed the perforation instead of 
>printing the headings first.  This report has multiple detail lines.  Would 
>Setting the OF Output Indicators on resolve this problem?  Or do I need to 
>Fetch Overflow when printing Detail Lines?
>
> Hector Sanchez
> Driscoll Childrens Hospital

+---
| 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
+---