Re: Ignoring a Spool File

["Scott Lindstrom" <SLindstrom@xxxxxxxxxx>]

You may also want to specify HOLD(*YES) just in case the OUTQ it lands in
happens to have a writer associated with it.  Otherwise it may start
printing before you can delete it.

Scott Lindstrom



                      "Wayne Johnson"
                      <wjohnson@ddc.com>        To:       
<midrange-l@midrange.com>
                      Sent by:                  cc:       (bcc: Scott 
Lindstrom/PDC/Pactiv)
                      midrange-l-admin@m        Subject:  Re: Ignoring a Spool 
File
                      idrange.com


                      11/20/02 05:11 PM
                      Please respond to
                      midrange-l






If you're going to use an OVRPRTF to hold the spooled file, you could
follow
the call to the program with a DLTSPLF *LAST.
It would still produce the report, but it would delete the spool file right
away.

-Wayne

----- Original Message -----
From: "Bob Randall" <BLR@Airxcel.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, November 20, 2002 3:19 PM
Subject: Ignoring a Spool File


> This seems very simple, but obviously I don't know how to do it. I would
> like to simply ignore a print file from a program. I want the program to
> run, and I don't have the source. I was thinking of using an OVRPRTF to
> not print the file. Currently we are sending it to a queue and delete it
> manually, or we use the cleanup process once a day. But I thought it
> would be nice to not produce the silly report if we could avoid it.
>
> Ideas?
>
> Thanks,
> Bob Randall
>
>