×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
*ALLOBJ doesn't trump *READONLY (see below), and I'm not concerned about an
*ALLOBJ user removing the *READONLY.
5250:
MD DIR('/tmp/test_readonly') -> Directory created.
CHGATR OBJ('/tmp/test_readonly') ATR(*READONLY) VALUE(*YES) -> Attributes
changed for 1 objects. 0 objects not changed.
RMVLNK OBJLNK('/tmp/test_readonly') -> Requested operation not allowed.
Access problem.
ACS IFS:
Delete -> 0 object links removed. 1 object links not removed.
SSH:
rm -rf /tmp/test_readonly -> rm: cannot remove '/tmp/test_readonly': Error
3500 occurred.
date: Wed, 3 Apr 2024 21:07:45 +0000 (UTC)
from: Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
subject: Re: Read-only dir & files within?
Justin,
Any user with *ALLOBJ can always delete your precious directory, no matter
what you do.? ?
"*ALLOBJ" means "all objects" -- including IFS (*STMFs and directories).
This is why it is important to limit the number of user profiles with
*ALLOBJ.
Just saying.
Mark S. Waterbury
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.