|
Thanks Carsten and Rob. But i have use CHGLIB LIB(ROB) CRTAUT(MYAUTL) But if i compile a clp to this lib, the object is still *PUBLIC *CHANGE. My autl is *PUBLIC *EXCLUDE and other user *all So the inherit, do not work. I dod not wan't to use grtobjaut edtobjaut all the time.... Regards Jan Rockstedt Avinova AB nic-hdl: JR1543-RIPE -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Wednesday, April 06, 2005 4:31 PM To: Midrange Systems Technical Discussion Subject: Re: Permissions on *lib See also CHGLIB LIB(ROB) CRTAUT(MYAUTL) Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Carsten Flensburg" <flensburg@xxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/06/2005 08:56 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject Re: Permissions on *lib Hi Jan, One way that I know if, is to specify an authorization list as the library's CRTAUT value: CRTLIB LIB(JANLIB) CRTAUT(JANAUTL) - Now all objects created into the JANLIB library will inherit the JANAUTL authorization list protection - and the object's *PUBLIC authority will be set to *AUTL. Best regards, Carsten Flensburg ----- Original Message ----- From: "Jan Rockstedt" <jan.rockstedt@xxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, April 06, 2005 3:41 PM Subject: Permissions on *lib Hi! How do i setup permission on a *lib and all the object in the lib. So if a new object will be added to this *lib, the object will inherit the permissions from the lib? In now the grtobjaut, but i wan't to inherit the permission automatic. Regards Jan Rockstedt Avinova AB nic-hdl: JR1543-RIPE -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.