Re: Modifying spool Files (Was Text on report)

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

Going back through my messages I re-read this message two or three times
until it finally clicked what you were saying.  I don't think this would be 
appropriate
to my situation, but you brought up the fact that spool files can be modified, 
which
has been requested of me quite a few times (somethign new on report, "can't we
just change the spool file?) I never knew how to do.

I understand everything, except for the last step.
3.      Then execute the CPYF cmd to copy the disk file to QSYSPRT.

I see QSYSPRT is a printer file located in my QSYS directory.  At this point in 
the
instructions, my spool file would be on my DASD as a text file (I use CPYSPLF
a lot when transfering data to PCs so understand that).

Are you saying that if I take a text file, and copy it to an existing printer 
file, the file
will be printed out instead of copied?

Regards,

Jim Langston

Peter Connell wrote:

> Jim,
> Here is an idea, but it may not be applicable to your situation.
> It is based on the following steps that can be used to create a copy of an
> existing spool file.
>
> 1.      The spool file is copied to disk via CPYSPLF CTLCHAR(*FCFC).
>         At this point the disk file could in fact be altered in any way
> (especially if it was a         cheque run, if you catch my drift).
> 2.      Then execute the OVRPRTF QSYSPRT CTLCHAR(*FCFC).
>         You can include any other parameters of the OVRPRTF cmd if you
> desire that change the  attributes of the new spool file.
> 3.      Then execute the CPYF cmd to copy the disk file to QSYSPRT.
>         This produces a new spool file which will differ only if you have
> changed the content or  overridden the attributes.

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