I know this has been discussed before, but I don't seem able to find the thread.
We have a folder on the IFS that we want all users to be able to read from and write to.
We want any new file that gets placed in this folder to have *public *rwx
The folder is set up *public *rwx, new data authorities are *rwx and new object authorities are *rwx
A third party i5 app drops a new .txt file on the folder and the user who ran the app has *rwx, but public has *none.
I don't know how this fits in but some users can run //iseriesname/foldername and are directly mapped to the folder without being prompted to enter their user id and password (everyone's windows user id and password is the same as their i user id and password). These people can read the file they just created. Other people, and we can't tell what is different for them, are prompted to enter a user id and password. These people cannot read the file even though they have *rwx for it.
Can someone point me to a resource for this sort of thing?
Thanks for any help you can give,
Lance
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.