 | |||
|
|
||
| |||
| |||
| |
|
Home > AS/400 Tips > iSeries security tips > Proper IFS security setting |
| |
|
|
|
| iSeries 400 Tips: |
|
|
|
|
|
|
|
|
|||||
|
ISERIES SECURITY TIPS Proper IFS security settingCarol Woodbury 04.05.2005 Rating: -3.18- (out of 5)
|
[IMAGE] | |||||
The solution:
Carol Woodbury, president, CEO of SkyView Partners, says, "To create an object into a directory, you need *W, so try giving the clerks DTAAUT(*W) and OBJAUT(*NONE) to the directory into which th
Digg This!
 StumbleUpon
 Del.icio.us
|
 |
 |
| |
RELATED GLOSSARY TERMS
|
||||
|
|
| |
RELATED RESOURCES
|
e files are being created.
"To read a file, the manager will need at least *X to the directory and *RX to the file itself. So the manager will need these authorities.
"The problem is the clerk is going to own the file. Even if you specify to have the group own newly created objects, objects created into the IFS ignore this user profile setting and the user creating the object owns it. So you will need some process to sweep the directory and change the ownership of these objects.
"If you are running V5R3, you may be able to take advantage of one of the new file system exit points that allows you to have a program called when objects are created into a directory. You may be able to use this program to immediately change the ownership. Otherwise, you will have to have a process that runs hourly or nightly."
|
DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk. |
|
|||
