|
Back several releases ago IBM changed an attribute on the /tmp directory.
This subsequently broke numerous things, including sending email from your
IBM i. The answer is to simply change the attribute. That same release
IBM had an IPL program that always changed it back. After they were
mercilessly beat into submission they removed that.
http://lmgtfy.com/?q=CPFA0B1
<snip>
Message CPFA0B1 occurs when you create a directory in the Integrated File
System (CRTDIR) with parameter RSTDRNMUNL set to (*YES)
</snip>
So the answer is to change RSTDRNMUNL to *NO
It was a poor attempt to imitate QTEMP.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: mlazarus <mlazarus@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/12/2016 10:00 PM
Subject: Delete authority for IFS file
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
If *PUBLIC has *RWX on a file in the IFS (/root file system) and its
containing folder, is there any reason a user, who is NOT the owner of
the file, should not be able to delete it via DEL or RMVLNK?
RMVLNK OBJLNK('/TMP/MYFILE.PDF')
CPFA0B1 Escape 40 01/12/16 16:00:00.603913
QP0LCCFN QSYS
From module . . . . . . . . : QP0LCEXH
From procedure . . . . . . : qgc_sendpm__Fv
Statement . . . . . . . . . : 17
Message . . . . : Requested operation not allowed. Access problem.
Cause . . . . . : An operation was requested on an object, but the
operation is not allowed in the context of the request. Appropriate
privileges may be required or the file system may not allow an operation
to the selected object.
Recovery . . . : Check the name of the object to make sure it is
correct. Correct the name and retry the operation. If trying to remove
a directory, use the RMVDIR command. If trying to link directories,
specify *SYMBOLIC for the LNKTYPE parameter of the ADDLNK command.
-mark
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx 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.