RE: IFS File permissions

Yes looking it has all authority (*RWX) for two users: *public and the user that created it.

i.e.:
Obj auth on both users is exist, mgt, alter and ref . for both . Data auth is objopr, read, add, update, delete, execute

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, May 01, 2014 6:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: IFS File permissions


S-1-5-32-544 is a Windows sid, the IFS would have no concept of that.
Can you tell us what the authorities are that you specified on the
open() API, and what the actual IFS authorities (not this windows stuff) are for this file and it's directory?

One easy way to do that is to use WRKLNK from a green-screen session.
iNav would be another way.


On 5/1/2014 6:15 PM, David Baugh wrote:

Hi,



I created a file in the IFS as part of a job running an RPG/free program, using an 'open' API from the RPG program.



When I try to manually delete that file in Windows, I get 'permission denied' if logged in as the user that ran the job. If I'm logged in as an administrator, I can delete it.



The error states that I need permission from the owner, which is S-1-5-32-544 (i.e. the Windows built-in Administrator).



It seems that when the file was created, the owner was assigned as the Windows built-in user 'Administrator', so any Windows-user trying to delete it must have admin privileges.



Anyone have experience with similar issues?



I'm wondering if there's any way to tell the RPG program to create the file with the default built-in 'users' group (s-1-5-32-545) instead of 'Administrator', which appears to be the root of the issue.



Thanks,



David

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.