AW: AW: Rename streamfile in IFS

["Werner Noll" <werner.noll@xxxxxxxxx>]

Hi Rob,

That was a great advice!
Many, many thanks.
I didn't that change mention before.

Kind regards,
Werner Noll
Gesellschaft für Individual-Software mbH
Ludwigstrasse 9
D-63739 Aschaffenburg
Phone: +49-6021-299880
Fax: +49-6021-299882
e-mail: Werner.Noll@xxxxxxxxx
 

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von rob@xxxxxxxxx
Gesendet: Dienstag, 2. August 2005 18:40
An: Midrange Systems Technical Discussion
Betreff: Re: AW: Rename streamfile in IFS

Oh!  /tmp!  That's a horse of a different color.

There was a change in V5R3 that causes /tmp to act differently.  There is a
directory property that says do not allow a user that does not own the
object to delete or rename a file, "Restrict rename and unlink".  Seems that
unix has a property like this as a poor implementation of an IFS version of
QTEMP library.  You can use iSeries Navigator to turn that attribute off.
File systems, integrated file system, /root, /tmp, right click, properties,
security tab, "restrict rename and unlink", turn off.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Werner Noll" <werner.noll@xxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/02/2005 11:26 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
AW: Rename streamfile in IFS






Hi Scott,

reffering to my example I can't follow your statement "Anyone with
appropriate ..".

This is my file in /tmp:

                             Work with Authority 
Object . . . . . . . . . . . . :   /tmp/pnctest.csv
Owner  . . . . . . . . . . . . :   NOLL 
*PUBLIC     *RWX         X     X     X     X 
NOLL        *RWX         X     X     X     X 

Directory /tmp is owned by QSYS and *PUBLIC has all authority.

User DUELL (programmer!) tried to rename with
REN OBJ('/tmp/pnctest.csv') NEWOBJ(pnctest.sav) 
and receives error message "CPFA0B1 Requested operation not allowed. 
Access
problem."
That's why I assumed that only the owner may rename the file.

The other option, which was also suggested by other group members, is the
use of QSYGETPH & QWTSETP. O.k., if there is no other way I'll have to go
this though one.

Kind regards and many thanks.
Werner Noll
Gesellschaft für Individual-Software mbH
Ludwigstrasse 9
D-63739 Aschaffenburg
Phone: +49-6021-299880
Fax: +49-6021-299882
e-mail: Werner.Noll@xxxxxxxxx
 

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Scott Klement
Gesendet: Dienstag, 2. August 2005 17:58
An: Midrange Systems Technical Discussion
Betreff: Re: Rename streamfile in IFS


> For renaming we decided the API "Qp0lRenameKeep". But this API  (as 
> well as other rename procedures) does not  support "adopted 
> authority". Therefore only the file owner can rename the file.

Anyone with appropriate authority can rename the file -- it doesn't have 
to
be the file's owner.  Nothing in the IFS supports adopted authority, so if
you really need to adopt, you'll have to use a profile swapping technique.

> Is there a work arround or any other suggestion to solve this problem.
> Many thanks in advance.

In my opinion, the best solution is to set the directory up so that the 
user
who needs to execute the API has appropriate authority to do so.  If 
that's
absolutely not an option, then swap to the new profile, make the change, 
and
swap back.  (You can use adopted authority to provide access to the 
profile
handles)
--
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.