Can be set on any. But, as far as I know, IBM only messed around with
/tmp.
It was IBM's way of trying to make /tmp act like library QTEMP. Lots of
poor compromises were involved.
- Anyone can see other peoples files.
- They didn't automatically clean up at job end.
- If JOBA created a duh.txt and JOBB tried also then they wouldn't be
separate files.
"Restrict rename and unlink" caused much grief when USERA would create a
file and passed if off to a process by USERB and it couldn't rename or
delete regardless of security access. This process was often done by
various email packages - IBM's included.
But, "restrict rename and unlink" was a common technique in the unix/linux
world for /tmp and IBM tried to emulate that.
Rob Berendt
This mailing list archive is Copyright 1997-2025 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.
midrange.com
