You can also create your own job description that sets the output queue, and attach that to your profile. Then it’s automatic every time you sign on.

Also create a CL that will set up your environment as you would choose it to be and make that your initial program.

Lots of options, these are only two, and others have provided good suggestions.

That said, I’d stay away from the diskette reader (QDKT), who knows how long that will be around and it might create some interesting results if someone starts that device.. (although support for diskette readers has been long gone)




--
Jim Oberholtzer
Agile Technology Architects




On Jan 29, 2026, at 12:58 PM, stefan@xxxxxxxxxx wrote:

Unless I'm on the same system you will likely be the only one using outq QDKT 🙂so change your userprofile to QDKT.
But no - this is not fully foolproof.


Best regards



Stefan



--

No trees were killed in the sending of this message, but a large number of electrons were terribly upset.



Stefan Tageson

+46 732 369934

stefan@xxxxxxxxxx<mailto:stefan@xxxxxxxxxx>



________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of James H. H. Lampert via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Thursday, January 29, 2026 18:38
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
--
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.

--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.