RE: Preventing printing of spool files

Not sure why you wouldn't want to create your own outq. I'm sure your client (?) would appreciate not wasting paper.

Short of creating your outq, do a WRKOUTQ OUTQ(*ALL) and find an obscure outq that's not attached to a writer and change your job or user profile to use that outq. Of course, you possibly risk that a writer may eventually be attached to that outq.

Maybe someone else has a better idea.

- Dan Bale

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert via MIDRANGE-L
Sent: Thursday, January 29, 2026 12:38 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Preventing printing of spool files

I've probably asked about this before.

On some customer boxes, I occasionally run into the problem of unintended printing of spool files: it needlessly wastes their paper, and clutters printers that are often over two thousand miles away from me with stuff that's of no conceivable use to them, while denying me access to compilation listings &c.

Is there a simple way, without having to create a dummy queue or device, to guarantee that no spool files created from my user profile are ever routed to an active printer?

--
JHHL

*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***