QPRINT is a Printer File and you can Hold it or reassign it a Printer Device or an Output Queue, but you want to copy QPRINT then you'll have to change your program anyway as many suggested for the OVRPRTF.
If you don't want to change any program, then you have to change the user profile to reassign the Output Queue "NOPRINT" or set a dummy printer device per default:
CHGUSRPRF USRPRF(YOURUSER) PRTDEV(DUMMYPRT)
-or-
CHGUSRPRF USRPRF(YOURUSER) OUTQ(NOPRINT)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, August 24, 2010 11:06 AM
To: Midrange Systems Technical Discussion
Subject: Re: Problems with spool files
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
If your software has it's own library I would create an outq there and use
it for this. Most companies are hesitant to change objects in a software
library.
And what about creating my own private *OUTQ, and my own private copy of
QPRINT (maybe called "NOPRINT," to indicate its purpose) pointing to it,
and then change the RPG program so it prints to NOPRINT instead of QPRINT.
That would avoid the need for overrides, and any possibility of my
interfering with something that IS supposed to be printed, but does
anything else have to be done to guarantee that nothing sent to NOPRINT
ever reaches a printer without being explicitly sent to one?
(At this point, the jury is still out on whether the spool file is in
fact being sent to a printer.)
--
JHHL
midrange.com
