On Tue 05-May-2011 11:21 , Ryan Hunt wrote:
Because of environment refreshes, I need to be able to recreate a
very specific set of user/table permissions after copying a large
library. Right now I either use iSeries Nav or green screen to add
users to files and then specify specific Add/Delete/Update
permissions for the user to the file.

I really need to automate this. Does anyone know what the related
CL commands are for this?


CHGOBJOWN, RVKOBJAUT, GRTOBJAUT /* REFOBJ() */, unlikely GRTUSRAUT

How is the "copying a large library" being accomplished?

CRTDUPOBJ effectively maintains authority, and CPYLIB uses CRTDUPOBJ for the objects in the copied library; although the authority for the created *LIB object is not similarly maintained. Performed by a user known not to have, or better a user which is known should not ever have, any private or group authorities, those duplication activities could be followed by CHGOBJOWN CUROWNAUT(*REVOKE) to reset objects to have the correct owner[ship].

SAVLIB enables since some v5 release [v5r4?] the ability to save [PVTAUT() parameter] and then restore the private authorities to the objects using RSTLIB.

When practical I would prefer to effect the creates, ownership and authority assignments, and then copy of the data, all using a script. Works best when the original library setup has the scripted creates and the ownership and authority setup, or otherwise is under change control for which the automated creation and change activity are generated from rules and\or more scripts as part of a CMS; the data-copy activity could be performed on a second pass since that would likely not be a feature available from most CMS.

Regards, Chuck

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].