|
One possible solution is to create an appropriate authorization list and secure the library with that authorization list. Then you could do a CHGLIB LIB(MyLib) CRTAUT(MyAutl) and "most" new objects created in that library will automatically have that authorization list applied. "Most" is used because IBM mixes around the defaults on the CRT... genre of commands to sometimes be AUT(*LIBCRTAUT) and sometimes something else. Another possible solutions is to not grant anyone access to that logical file. Instead have the access be by programs that "adopt" appropriate authority to that file and get the job done. One of the above solutions, and appropriate authority to the physical should be all you need to do RLA using sql indexes. Although I do see that the default authority on the index is handled differently depending on whether or not you are using SQL naming, or system naming, when defining the index. I'd give you a V5R4 link but I think that is being updated as I type. http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/db2/rbafzmstxcindx.htm#wq1152 Rob Berendt
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.