Re: Keeping spool files from being sent to a printer -- can somebody refresh my memory?

Thanks.  And, perhaps add SECURE(*YES) also ... :-)

On Monday, May 23, 2022, 03:54:31 PM EDT, x y <xy6581@xxxxxxxxx> wrote:

What Mark said and add OVRSCOPE(*JOB).

On Mon, May 23, 2022 at 10:41 AM Mark Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

When you first sign-on, issue:

    OVRPRTF FILE(*PRTF) TOFILE(*FILE) HOLD(*YES)

That should do it ...

On Monday, May 23, 2022, 01:32:15 PM EDT, James H. H. Lampert via

MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I vaguely remember dealing with this before, but it's been a long time.

We've just been given access to a customer box, and I've discovered that
if I try to compile something, the compilation listing is sent to a
started printer.

If I look at the user profile, I see PRTDEV(*WRKSTN) and OUTQ(*WRKSTN),
and if I do a DSPJOB  on my terminal session, I see that I'm going to
PRT01, which is a real printer with a writer job.

Is there any trick to making sure my spool files never go to a started
printer, without having to find out whether there's a "guaranteed never
to be started" printer device on the system?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com