No Dave, that isn't the point. That "was" the point. But if you look at John's last sentence. <snip> But adopted authority has a serious shortcoming that limits it's usefulness in the file systems that the majority of new applications would use. </snip> If I do a MD DIR('/scratch') CHGAUT OBJ('/scratch') USER(*PUBLIC) DTAAUT(*EXCLUDE) OBJAUT(*NONE) CHGOWN OBJ('/scratch') NEWOWN(BUBBA) A program that adopts the authority of BUBBA will still not have authority to data in this directory. You need to do profile switching to get access. See the profile handle api's at http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/sec1.htm An example of profile handling is if you use any netserver drives on your i5, or if you use WDSC or any other such client server application. Then you could do a WRKOBJLCK OBJ(MYID) OBJTYPE(*USRPRF) In there you will find jobs that are running under one user id, but "servicing" another. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.