|
This is interesting... So *RSTDRNMUNL only applies to directories.
My issue is that an IFS filename may be "reused" or "overwritten" by more
than one user. So today, the owner might be JOHNNY but tomorrow the owner
might be JANE.
Within the same job, I will often run "cleanup" program for a subdirectory
that deletes all files older than 60 days.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Monday, March 20, 2023 12:46 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: IFS Directory Authority
You mean something like this?
CHGATR OBJ('/mydir') ATR(*RSTDRNMUNL) VALUE(*YES)
IBM used to change '/tmp' at each IPL to this until we stormed the gates.
The reason that stank was the user app would write a file to it for use by
IBM's email APIs. Then it would pass control over to the other programs
like QMSF and the smtp jobs and they could not delete the file since they
were not the owner and didn't have *ALLOBJ.
Just make sure you won't run into similar issues.
On Fri, Mar 17, 2023 at 3:23 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I would like to set the authority on a directory so that no one can move,list
delete, or rename the directory itself (except owner and QSECOFR).
However, all users need to be able to run programs that read, write
(create), and delete objects INSIDE the directory.
My programs use this directory for storing temporary files (XML, JSON,
TXT, etc.) while consuming web services, downloading files, etc.
One of those directories "went missing" earlier this week - someone
accidentally deleted it or otherwise moved it.
I looked through the archives, but didn't really find much...
TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
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.