Re: Giving read access to a spool file -- MIDRANGE-L

Subject: Re: Giving read access to a spool file
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 24 Nov 2008 09:23:39 -0800
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/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

John Earl wrote:

It depends - are they concentrated in a single Outq, or are they spread
across OUTQ's?
If they are in a single (or few) OUTQ's, are there other entries in
that/those OUTQ's that need to be protected?

In all likelyhood, all will be in the same OUTQ as the present one, or maybe QEZDEBUG or QEZJOBLOG.

Or if moving spool files to an artificial OUTQ that the other user would "have the run of" would work, I could do that.

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.