RE: IFS File CHGAUT Oddity

Exactly.  We do the same thing. 

If a process creates a new file we do a CHGAUT before the document gets 
processed by anything else. 

The reason we ran into a problem is the customer is creating the files 
before they get to our process so they have a different object owner.

Fortunately when we wrote our code originally we added a data area in our 
software to disable the use of CHGAUT, however we leave it on by default. 

I just wanted to know I wasn't going crazy.  Or at least crazier than I 
already am :-)

Thanks for the $.02 :-)

Regards,
Richard Schoen
RJS Software Systems Inc. 
"Providing Your....iNFORMATION NOW!"
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 898-3038
Fax: (952) 898-1781
Toll Free: (888) RJSSOFT
------------------------------

message: 3
date: Fri, 5 Jan 2007 13:36:42 -0800
from: "Holder, Ken" <kkh@xxxxxxxxxxxxx>
subject: RE: IFS File CHGAUT Oddity


That is true but I have found it has the same restrictions for the Unix 
part of the IFS.  My work around has been to have the job creating the 
object do a CHGAUT for *PUBLIC to add or remove authority as needed.  This 
gets makes sure the object is correctly for the IFS and gets past the 
error if another user (not the owner or *ALLOBJ) tries to alter *PUBLIC 
authority.. 

Otherwise for the QSYS.LIB file system RVKOBJAUT or GRTOBJAUT might be a 
better choices.

$.02 worth