Can I force all printouts from a library to go an outq in that library? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Can I force all printouts from a library to go an outq in that library?
From: "Booth Martin" <Booth@xxxxxxxxxxxx>
Date: Sun, 8 Sep 2002 10:13:12 -0400 (Eastern Daylight Time)
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

--
--
[ Picked text/plain from multipart/alternative ]

I am trying to figure out a way to create an application that is
self-contained and can only be accessed by members of the group.  So far
everything seems to work ok except printing output.

Is there a way that any printed output from any job in that library can be
forced to an outq for that library?  This would need to include printed
query output.

Thank you.

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------
--
[ Content of type image/gif deleted ]
--

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Can I force all printouts from a library to go an outq in that library? , Vernon Hamberg

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.