Authority problem from Windows XP

225 pts.
Tags:
IFS share file authority
OS/400
Windows XP
We have created a Share in the IFS for a client. They have a User profile on the I-series and the Share has been set up using that User profile. A file has been put into the shared folder and given full authority to the object. However when the client opens the file it comes up as Read only. Why?

Software/Hardware used:
iseries os400 windows XP
ASKED: December 3, 2009  2:25 AM
UPDATED: December 6, 2009  9:58 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Confirm that the Windows XP password and profiles match the AS/400.

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    When you attempt to save the file, try using Save as... instead. When the Save as... dialog opens, check the Save in: path. Review the hierarchy of directories that show in that path. Your description implies that the top-level folder in that path is the directory that you created and then shared. Did you create it? Or did the top-level directory in that path already exist and you only changed its "sharing" attribute? If you didn't create it, can you show here the full path to that directory starting with /root? Tom
    125,585 pointsBadges:
    report
  • RobertHart
    The files is being created on the i-series using CPYTOSTMF. The root directory has *Public *ALL authority and the client has *ALL authority to all the sub-directories. The Profile they are using to access the IFS from Windows is different to the Windows profile they use, could this be the answer? They can copy the file and modify the copy but this seems to add extra steps that shouldn't be needed.
    225 pointsBadges:
    report
  • Teandy
    Just because they have authority to the folder does not necessarily mean they have authority to the objects inside the folder. Try this: Give the profile *ALLOBJ and see if it makes a difference. If it does, then you have an authority issue. If not then I would say that the problem is on the PC. Make sure you remove the *ALLOBJ authority after testing.
    5,860 pointsBadges:
    report
  • TomLiotta
    The root directory has *Public *ALL authority... But that doesn't really affect the read-only attribute. Is the share one that you explicitly created as a share or is this merely a subdirectory of /root or some other directory that is being shared? I.e., is the directory a subdirectory in a hierarchy where the real "share" is at the top? If so, then review the NetServer read-only attribute of the shared directory at the top. If this is involved, then it might have nothing to do with authority. It might simply be that NetServer was told that this share is "read-only". If that's not the case, then we can look elsewhere. This is simply an attempt to weed out possible causes. Tom
    125,585 pointsBadges:
    report
  • RobertHart
    Thank you Tom. That was it. I had missed that parameter. I thought I had set it to *RW but it was only *R. Will remember that for the future.
    225 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following