Werner

Thanks for your help



Werner Noll wrote:

Rob,

what do you mean by "cannot access"?

my directories do not appear when I display the IFS with OPs Nav although

Root
QOpenSys
QDLS

etc. do appear.

If I type

EDTF /

on a green screen command line, all directories appear.



If you search by GOOGLE with "IFS Authority Considerations" you will get a link to an IBM technical document, which describes the "traps" on IFS

I looked at this but, because I don't set up a new installation very often, I have perhaps forgotten some of the basics and it didn't seem to cover my problem.

It did suggest that "Many operations require *RX authority to the entire path including the root."

However, in V4R5, this does not appear to be a valid option. Mine are all set with *RWS authority.

Many thanks for your suggestion.

I am using Windows XP Pro

I am really stuck and am desperate to solve this problem. I know that many (most??) people have solved this problem so I am probably just being stupid. Has anyone any suggestions?

authority rules.

Regards,
Werner Noll

-----Ursprüngliche Nachricht-----
Von: Rob Dixon [mailto:rob.dixon@xxxxxxxxxxx]
Gesendet: Donnerstag, 25. März 2004 14:14
An: midrange-L@xxxxxxxxxxxx
Betreff: Accessing IFS proglem


I have often read in the pass postings about this problem and thought that I had taken the answers on board, but, I am presently working on a V4R5 system, and I cannot access user directories in the IFS. I have searched the archives and elsewhere but am unable to find the answer.


I am using Ops Nav in V4R5, signed on as QSECOFR. I can see the IFS under File Systems and, within the IFS, the Root directory, QOpenSys, etc. but the user directories do not appear. I can see them using WRKLNK when signed on as QSECOFR using Client Access. I can access their contents with a browser.

Both QSECOFR and *PUBLIC have *RWX authority to the directories.

I am sure the answer is simple, probably on page 1 of lesson 1, but I need help please!








_______________________________________________ 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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.