RE: CRTDUPOBJ and OVRPRTF command.

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

On Friday, June 19, 1998 3:33 PM, Rick Baird [SMTP:rbbaird@Premsys.com] 
wrote:
> We are about to go thru a huge battery of tests on a huge number of
> program changes at one of our clients.  Our problem is that during
> these tests, a huge number of reports will be printed, all on
> production printers (because of ovrprtf commands throughout each job).
>
> Since our testing will be done during regular business hours, so all
> these extra reports may confuse the rank and file.
>
> What I thought I could do was to create my own version of OVRPRTF that
> would ignore the "DEV" and "OUTQ" parameters, but process the others,
> and put it above QSYS during testing.

> Does anyone have another suggestion on how to stop the overrides from
> printing?

Rick,
  Why not just put an OVRPRTF *PRTF OUTQ(TESTOUTQ) as the first line in 
your tester's initial program?  I do this all the time at client sites 
from the command line before I call the client's menu program.


Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---