Re: Spool file security -- MIDRANGE-L

Subject: Re: Spool file security
From: Jim Franz <franz9000@xxxxxxxxx>
Date: Thu, 26 Feb 2026 09:55:01 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

But by having the spooled file created/owned by another profile (like a
service account) , the orig user of the orig job should not be able to see
it or delete it (outside of things like *SPLCTLor group profile).
Jim Franz

On Thu, Feb 26, 2026 at 9:37 AM Rich Loeber <rich@xxxxxxxxx> wrote:

There is also a spool file security exit point that can be customized for
specific needs. I think this was IBM's response to this issue.

Rich Loeber
Kisco Systems LLC
https://www.kisco.com

As an Amazon Associate we earn from qualifying purchases.

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.