RES: IFS File Authority

Hi,

We had a similar problem with Net.Data, instead of writing a new file over
an older, try to first delete the file, then write a new one.

Regards,

Rubens Lehmann

-----Mensagem original-----
De: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]
Em nome de rob@xxxxxxxxx
Enviada em: quinta-feira, 27 de março de 2014 13:43
Para: Midrange Systems Technical Discussion
Assunto: Re: IFS File Authority

Check also the 'attributes' of the folder. "Restricted rename and unlink".
If USERA creates a file in a directory with this attribute enabled then even
QSECOFR can't get rid of it.
It was something popular with Linux and is the worlds crappiest
implementation of mimicing QTEMP in a stream file environment. Several
releases ago IBM tried setting this attribute on in /tmp. Which broke a lot
of email programs (including IBM's). People would set this off and the next
OS upgrade would turn it back on again. After several attempts at gelding
them with a pair of steel toes they stopped doing this.
But it is something to watch for.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Kurt Braman <kbraman@xxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/27/2014 12:30 PM
Subject: Re: IFS File Authority
Sent by: midrange-l-bounces@xxxxxxxxxxxx



The folder has the following authorities,

Owner - QSYS
Primary Group - *NONE
Authorization List - *NONE

*PUBLIC (data) *RWX - (object) *OBJMGT, *OBJEXIST, *OBJALTER, *OBJREF
QSYS (data) *RWX - (object) *OBJMGT, *OBJEXIST, *OBJALTER, *OBJREF
QDIRSRV (data) *X

Kurt Braman
Programmer/Analyst
Nasco
901 Janesville Ave
Fort Atkinson, WI 53538
(920) 568-5500 ext #1202


On Thu, Mar 27, 2014 at 11:21 AM, Charles Wilt
<charles.wilt@xxxxxxxxx>wrote:

What are the authorities to the IFS directory itself?

Adding/removing files requires authority to the container...not the

file.

Charles


On Thu, Mar 27, 2014 at 12:00 PM, Kurt Braman <kbraman@xxxxxxxxxx>

wrote:

We have a program that creates an xml file on the IFS using CGIDEV2.

When

USERA runs the program it creates the file on the IFS with USERA as

the

owner having *RWX authority and *PUBLIC has *RWX authority. When USERB

runs

the program to create the same file on the IFS, it doesn't replace the
existing file but creates a new file with TEMP(jobnumber) appended to

the

end. When I view the authority on the temp file, USERB is the owner

having

*RWX authority and *PUBIC has *RWX authority. What authority is

missing

that doesn't allow USERB to replace the file created by USERA?


Thanks,
Kurt Braman
Programmer/Analyst
Nasco
901 Janesville Ave
Fort Atkinson, WI 53538
(920) 568-5500 ext #1202

--


This e-mail is the exclusive, private and confidential property of the
sender and the intended recipient. If you are not the intended

recipient

you are hereby advised that any unauthorized disclosure, copying,
distribution or the taking of any action in reliance on the contents

of

this message is strictly prohibited.
--
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.