RE: System library list -- MIDRANGE-L

Subject: RE: System library list
From: <phil.seay@xxxxxxx>
Date: Fri, 18 Nov 2011 13:15:36 -0500
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>

Hi Richard,

If you use object level authority to secure your applications, you'll have your application libraries defined as USER(*PUBLIC) AUT(*EXCLUDE). If you put a library defined like that into the system part of the library list, jobs running under user profiles without either *USE private authority to that library or *ALLOBJ special authority will not be able to start. I tested this and found that a whole bunch of QUSRWRK and QSERVER prestart jobs wouldn't start.

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.