Fine tuning access to LongReach user files and folders

Use this Forum to post your “How to …” questions about your use of LongReach. This is not a technical support forum. Both the LongReach Support Team at LANSA and other LongReach customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.
Post Reply
alick
Posts: 67
Joined: Fri Dec 09, 2011 7:52 am

Fine tuning access to LongReach user files and folders

Post by alick » Mon May 28, 2012 11:18 am

File and folder authorities is always a tricky issue.

An initial broad brush approach is to allow *PUBLIC access to the '/longreachdata' folder.

CHGAUT OBJ('/longreachdata') USER(*PUBLIC) DTAAUT(*RWX) OBJAUT(*NONE)
CHGAUT OBJ('/longreachdata/shared') USER(*PUBLIC) DTAAUT(*RWX) OBJAUT(*NONE)
CHGAUT OBJ('/longreachdata/user') USER(*PUBLIC) DTAAUT(*RWX) OBJAUT(*NONE)

For the LongReach App user to create a profile subfolder in the '/longreachdata/user' folder, there needs to be either a *PUBLIC authority of *RWX or a suitable data authority for that user to create the subfolder.

New files and folders will inherit authorities from the parent folder.
Being the file or folder owner, the user gets all data and object authorities to that file or folder.

WRKAUT OBJ('/longreachdata/user/FRED')

Object . . . . . . . . . . . . : /longreachdata/user/FRED
Owner . . . . . . . . . . . . : FRED

*PUBLIC *RWX
FRED *RWX X X X X
LONGREACH *RWX X X X X

You will need to play around with group profiles and add/remove or modify *PUBLIC and user authorities to suit your needs.

Post Reply