|
There are a few ways to do that.
The first one I can think of is sending your spooled files to an output
queue that is not connected to any printer. If your users have spool
control special authorization, they can then resend their outputs to their
printer devices. This is not so elegant, because it requires precisely,
users to know how to manage out queues, or even have an operator do that
for them.
The other one, a little more costly, is to change your programs to always
override the printed output to be held in the out queue. When you need any
spooled file to be printed on your computer, you simply release it. Again,
this may require users to manage out queues.
The third one, is to redirect spooled files to PDF stream files on the IFS,
say, /home/johndoe, and so on for each user. Then, map a drive on their
computers to get access to their PDF outputs, and then just open and print
them. I like this one most because you dismiss the users to manage
commands and out queues. The cost is change programs to
OVRPRTF's that send the output to a stream file.
HTH
JS
El mar, 30 jul 2024 a las 13:20, Ken Meade via MIDRANGE-L (<
midrange-l@xxxxxxxxxxxxxxxxxx>) escribió:
All,list
Like a lot of companies we are looking at minimizing the number of
printers we have, but one of our concerns is that print jobs will pile up
at the printer.
I know that I can set up a driver configuration on my local Windows
machine to do a HOLD at the printer and I enter a code at the printer to
get my jobs when I'm ready for them.
In fact that is what we plan on doing for all users as we set up their
local machines and primary printers.
We'd like to replicate this same thing for jobs that come from our i, is
this even possible?
Thanks,
Ken
Ken Meade | Director of Information Technology and Infrastructure
kmeade@xxxxxxxxxxxxxxxxx <mailto:kmeade@xxxxxxxxxxxxxxxxx> | (603)
444-3570
[cid:image001.png@01DAE293.F2FEB6A0]
Littleton Coin Company, Inc.
1309 Mt Eustis Rd, Littleton NH 03561
www.littletoncoin.com<http://www.littletoncoin.com/>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 mailing list archive is Copyright 1997-2024 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.