Re: Multi Printer files in a program

[Buck <kc2hiz@xxxxxxxxx>]

> So the other way is to have different
> Printer files. The problem is that in the
> sequence of the data, there could be one 
> problem listed, lets say on Printer_file_1,
> then the next problem would belong to
> Printer_file_2, then 3, then back to 2.

Is this a problem for the presentation?  I mean, is it bad that the same 
problem is spread across several reports?  Or is it just hard to keep 
track of in your program?

> All the while, I have to keep track of 
> when to effect the page headings.

This is the beauty of RPG!  Let the compiler do that for you.  Assuming 
you are using exception time output, use fetch overflow and the compiler 
does all the work.

There is an alternative that you may want to consider: scratch/work 
files.  Create a work file for each problem type in QTEMP and have your 
'problem finder' program dump records into each file as appropriate. 
Then use a simple tool like Query or RUNSQLSTM to print a separate 
report for each problem type.
  --buck