Gary,
..the folder that the file is in (root\tmp\) has all permissions checked except for exclude and from AUTL (but we don't use AUTL anyway).
but I'm thinking these IFS permissions are independent of what's going on here. Seems to me that the permission issue I'm getting is due to a lack of access rights based on Windows security (because the file is owned by the Windows built-in Administrator) and I'm having an issue either manually deleting it in Windows Explorer using the file share, or in a VBScript that's attempting deletion.
Or am I wrong? It doesn't matter that the share is read/write if the file is owned by an administrator, if the Windows user accessing it has less rights.
Isn't this whole issue based on the file having been created by the 'open' API with the Windows built-in administrator as owner?
________________________________________
From: MIDRANGE-L [midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson [gthompson@xxxxxxxxxxx]
Sent: Friday, May 02, 2014 1:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: IFS File permissions
David,
On our IFS we enable "Existence" on the folder/directory to allow delete of file objects.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Baugh
Sent: Friday, May 02, 2014 2:37 PM
To: Midrange Systems Technical Discussion
Subject: RE: IFS File permissions
Sorry Vernon, my notation was incorrect (i.e non-standard). I apologize if this threw you off.
My intention was to show that the flle is accessible as follows under the IFS in Navigator:
QNTC/a file folder corresponding to the iSeries server name/root/tmp/myfile.txt Or Root/tmp/myfile.txt.
We have a file share specified on root as read/write. I'm trying to delete the file over our network at \\iseries server ip address\root\tmp\myfile.txt
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Friday, May 02, 2014 10:35 AM
To: Midrange Systems Technical Discussion
Subject: Re: IFS File permissions
David
Where do you see it when you come through Root? Your other path, QNTC../../Root, you are NOT in QNTC - just as in Unix or Windows or DOS, those double dots are saying go to the parent directory of what comes before it.
In other words, double dots mean you are going UP, not down the directory tree.
Vern
On 5/2/2014 12:02 PM, David Baugh wrote:
Thanks. Actually, When I look in Navigator under Integrated File System,amongst other entries, I see Root, QNTC and Filesvr.400. Filesvr has not entries, however the file I'm trying to access is in a subdirectory of /Root and I can get to it by expanding either the Root or QNTC../../Root directories under the Integrated File System folder.
Does that help?
________________________________________
From: MIDRANGE-L [midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon
Hamberg [vhamberg@xxxxxxxxxxxxxxx]
Sent: Friday, May 02, 2014 8:44 AM
To: Midrange Systems Technical Discussion
Subject: Re: IFS File permissions
It's QNTC if it's in the IFS under /QNTC - otherwise it isn't.
On 5/2/2014 9:30 AM, David Baugh wrote:
Justin how can I determine that? With limited knowledge there, I'd guess it's via QNTC. It's on a file share in Navigator with read/write access.
________________________________________
From: MIDRANGE-L [midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor [JUSTIN@xxxxxxxxxxxxx]
Sent: Friday, May 02, 2014 6:03 AM
To: Midrange Systems Technical Discussion
Subject: RE: IFS File permissions
Is this file on the root IFS shared via the NetServer, or directly on a Windows share via QNTC?
--
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.
--
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.
--
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.
--
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.
--
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.
midrange.com
