Re: CPYTOSTMF authority question

What is your target directory?
Without looking at the authority on the directory let's look at the
attributes of the directory. For example, by default, DSPATR '/tmp' will
show that directory with
Restricted rename and unlink . . . . . : Yes.
As that is kind of a poor man's way of implementing how other open systems
deal with that directory.
Most people change it to No. Otherwise email deletions do not happen
because when one job under one user, passes it off to the email job under a
different user, the other user cannot delete it, even with *ALLOBJ
authority.

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


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Gerald Magnuson
Sent: Friday, September 20, 2019 2:36 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: CPYTOSTMF authority question

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


I have found in tracing audit log problems, that we have been leaving
behind stream files that become email attachments....
CPYTOSTMF FROMMBR('/qsys.lib/qtemp.lib/mimeout.file/m+
imeout.mbr') TOSTMF(&STFILE) +
STMFOPT(*REPLACE) STMFCODPAG(*PCASCII)

this creates the stream file with the authority of DATA(*RWX) NO OBJECT
AUTHORTIES for the user that ran the job.... we then perform a CHGAUT
OBJ(&STFILE)
USER(*PUBLIC) DTAAUT(*RWX) OBJAUT(*ALL) and then pass that stream file
onto MMAIL....

but at the bottom of the program, when we try to RMVLNK, it fails on
CPFA09C, not authorized...

I don't know for sure why we do the CHGAUT, but my guess was it allowed
the mmail command to process...

1) would a different value than "DFT on the AUT parm of the CPYTOSTMF
command fix this?
2) the original MIMEOUT file's authority a problem?
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com