Re: OVRDBF FILE(QSYSPRT) Returning Error

[Jason Abreu <jason.abreu@xxxxxxxxxxxxxxxxxxxx>]

Makes perfect sense.

Thanks for the explanation!  I was hoping to avoid creating a spooled 
file, all together, but it doesn't look possible.  I will modify my test 
to use the example you provided.

The process is meant to be used by end-users and I do not want to 
confuse them by creating unnecessary spooled file output in their queue. 
 I'll just have to add some logic to delete the spooled file after the 
copy is performed.

Thanks again!

Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/

On 12/13/2010 11:16 AM, Dennis Lovelady wrote:
> Redirection of panel group output to a database file is not intended to be
> successful.  The printed output is not conducive to a structured file, so
> IBM prevents this as a one step operation.  (The same is true of commands
> like WRKACTJOB, which writes to an externally-described printer file.  Same
> issue, different jacket.)
>
> To do what it appears you are trying to do:
>
> OVRPRTF QSYSPRT HOLD(*YES)
> WRKJOBSCDE OUTPUT(*PRINT)
> DLTOVR QSYSPRT
> CPYSPLF QSYSPRT SPLNBR(*LAST) TOFILE(QTEMP/...)
>
> Dennis Lovelady
> http://www.linkedin.com/in/dennislovelady
> --
> Very funny, Scotty.  Now beam my clothes down too.
>
>
> > My test code is as follows:
> > PGM
> >              CRTPF      FILE(QTEMP/TESTOVR) RCDLEN(132)
> >              OVRDBF     FILE(QSYSPRT) TOFILE(QTEMP/TESTOVR)
> >              WRKJOBSCDE OUTPUT(*PRINT)
> > ENDPGM
> >
> > However, the job fails with:
> > CPF9850 - Override of printer file QSYSPRT not allowed.
> >
> > Any ideas why this simple override is not working?
> >
> > --
> > Jason Abreu
> > Abreu Innovations, Inc.
> > jason.abreu@xxxxxxxxxxxxxxxxxxxx
> > http://www.abreuinnovations.com/
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.