Re: ** Odd IFS File Authority Issue on V5R3 **

I wonder if you are using the /tmp directory.  Here is a snip from the memo
to users for v5r3:

<snip>

3.14 Creation of /tmp, /var, /QOpenSys/var, and /QOpenSys/var/preserve
directories

In V5R3, the /tmp, /var, /QOpenSys/var, and /QOpenSys/var/preserve
directories are created with the Restricted rename and unlink attribute
set to Yes. (Note: this attribute is equivalent to the S_ISVTX mode bit
for a directory.) As a result, after an IPL of V5R3 (for the /tmp
directory) and after an OS/400 PASE install (for all of the other
directories), you can no longer rename or unlink objects within these
directories unless one of the following is true:

*  You are the owner of the object.
*  You are the owner of the directory.
*  You have all object (*ALLOBJ) special authority.

This attribute (or mode bit) is similar to the other attributes in that
it can be turned on or off. You can do this using the Change Attribute
(CHGATR) CL command or the Qp0lSetAttr or chmod APIs, provided you are
the owner of the object, or you have all object (*ALLOBJ) special
authority.

</snip>



----------------------------
Bryan Dietz
Aktion Associates

midrange-l-bounces@xxxxxxxxxxxx wrote on 09/13/2004 11:33:03 PM:

-> Hello All,
->
-> We are using code that creates work files in the IFS and up until V5R3
-> this has worked perfectly.
->
-> Here's what we are seeing happen on a customer's V5R3 box.  However it
-> works fine on ours.
->
-> When an IFS file gets created by a user, the *PUBLIC user is given *RWX
-> authority with all the object management attributes.
->
-> The user, we'll say JOE in this case has *RWX authority, but none of the

-> object management attributes are set for allowing the user to delete his

-> own file when he's done with it.
->
-> Here's  how the attributes look:
->                    Data     --Object Authorities--
-> Opt  User        Authority  Exist  Mgt  Alter  Ref
->      *PUBLIC     *RWX         X     X     X     X
->      JOE             *RWX
->
-> Here's how the attributes should look.
->
->                    Data     --Object Authorities--
-> Opt  User        Authority  Exist  Mgt  Alter  Ref
->      *PUBLIC     *RWX         X     X     X     X
->      JOE             *RWX         X     X     X     X
->
-> The odd part is that the user can issue a CHGAUT to give themselves full

-> authority and then the file can be deleted. That is our workaround for
-> now.
->
-> Is anybody aware of any outstanding IFS authority PTF's for V5R3 ?
->
-> I didn't see anything relevent on the PTF site.
->
-> Any input is appreciated.
->
-> Regards,
-> Richard Schoen