Re: DSPAUT OBJ('/QSYS.LIB') versus DSPOBJAUT OBJ(QSYS) TYPE(*LIB)

On Feb 7, 2011, at 2:37 PM, CRPence wrote:

A SWAG... is that POSIX standards are the
fault for the difference in requirements. IIRC the object [operational]
authority *OBJOPR enables viewing\accessing the data rights [data
authority] to the object natively, which is the first requirement of
*USE since that object right must exist to even know\test of any data
rights. The object [management] authority *OBJMGT as a requirement for
displaying authority via an IFS [non-native naming] API is presumably an
attempt to mimic similar limitations that would be imposed on a *nix
system.?

This SWAG matches my experience - and kind of tracks with the way a CRTDUPOBJ command works. You'll notice that you can CPYF a file with just *USE, but you must have *USE + *OBJMGT in order to CRTDUPOBJ. This is (at least in part) because CRTDUPOBJ must access the security authorization description part of the file in order to completely duplicate the object and a CPYF does not (because it does not duplicate the authorities to the new file).

jte

--
John Earl
President and CEO,
Townsend Security
360-359-4418
townsendsecurity.com
The Encryption Company