sponsored links

Collapse

Announcement

Collapse
No announcement yet.

Authorization list at root / level

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Authorization list at root / level

    I want to have an account that is limited to just one sub folder on the IFS. What is the best way to do this with authorization lists? For testing purposes I created a list with public *exclude and can't get that to work at the root level but it does work against sub folders.

  • #2
    Authorities on the /Root FS work in the same way as they do for the library FS. The authorisation list is used in conjunction with the object authorities. What does your authorisation list look like? What are the authorities on the directories?
    I would have very serious concerns trying to excluding public from the root directory as I would think this will likely cause system functions to stop working...

    There may be other ways depending on how they are accessing the directory. Is this through a 5250 session via e.g. WRKLNK or QShell or via NetServer or some other means? If by NetServer for instance, you could create a share for them to access.
    Last edited by john.sev99; 3 weeks ago.

    Comment

    sponsored links

    Collapse

    Working...
    X