That user has to be in a group by itself and that group needs read only access. This user cannot be in another group with write access.
The &PH& works the same as RT_* files. This gets written to at run time. By the way DS_JOBS makes no difference at run time.
Read only access to Project
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
Just ensure the folder has read only permissions defined for the "other" group and have a UID created that is not the "owner" or does not belong to the "group" definition assigned to the folder. This will give the UID only read permission of "other" to the folder.
Ex:
drwxrwxr-- 2 dsadm dstage 256 Jun 03 2008 DS_JOBS
the owner is dsadm and has permissions rwx
the group is dstage and has permissions rwx
the other has permissions r--
does that help?
In my test with IS v8.0.1 on AIX 5.3 the DS_JOBS required execute permissions for the job to start from the client or director. My UID security is from the OS not LDAP or the repository, not sure if that would make a difference.
Ex:
drwxrwxr-- 2 dsadm dstage 256 Jun 03 2008 DS_JOBS
the owner is dsadm and has permissions rwx
the group is dstage and has permissions rwx
the other has permissions r--
does that help?
In my test with IS v8.0.1 on AIX 5.3 the DS_JOBS required execute permissions for the job to start from the client or director. My UID security is from the OS not LDAP or the repository, not sure if that would make a difference.
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am