|
Carel,From my experience this changed after V5R1. I had a CL in R1 that copied a native file to an IFS directory and then renamed it. Worked.
That was one of the few things that blew up when we went to V5R3 (skipped R2). Users could no longer rename the file once it got to the IFS, even though they owned the file. Had to rename it while it was still in the QSYS library set.
* Jerry C. Adams *iSeries/i5 Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.893.8633x152 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Carel Teijgeler wrote:
Greg, You may be surprised there, too. At least, this is my experience. Perhaps others can contrasdict this.I use the UNIX service programme from the iSeries Toolkit.When creating an IFS file I see that users with a certain level of authority (not *ALLOBJ) are the owners of the file, but have *RX rights, not *RWX. I had to change authority to givve them all rights (*RWX) to write to the file on the IFS they own (sic!).Users with *ALLOBJ do not suffer this problem. If I create a file in the IFS (being in the user class *SECOFR) I have all rights and ownership (of course) to that file.I do not know what the line between full rights and limited rights for the IFS is (even with ownership in hand). After the file has been created I give *PUBLIC *RWX rights, so others can copy it from the IFS to their local drives or use it in their favourite Office applications. Regards,Carel Teijgeler*********** REPLY SEPARATOR *********** On 17-11-05 at 11:02 Fleming, Greg \(ED\) wrote:That'll work for me. One day soon, I'll dig in and learn to write directly to the IFS from myRPG programs like the big boys do. Then I'll have full command of the authorities, and will be able to leverage that power into vast wealth or maybe world domination. Huhahahahahah.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.