Re: Problem with V5R3 - /tmp directory & qtmmSendMail

[rob@xxxxxxxxx]

I had that same issue.  Remember when I submitted an email to this list 
about how to change the temporary directory used by SNDEMAIL?  That is 
exactly why.
Oh, by the way, that attribute you changed - it gets reset back everytime 
you IPL.  Unless you have a certain PTF on.  I forget what it was.  I 
think it made it into GA.

I agree, it's not backward compatible.  But, at least they covered it in 
the "Memo to Users" and they ptf'ed that stupid IPL change.  So I am 
willing to let that one go.

Others, you do NEED to read the Memo to Users.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Kevin Wright <Kevin.Wright@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/10/2004 05:27 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Problem with V5R3 - /tmp directory & qtmmSendMail






Hi all,

We too develop a software product and are enjoying V5R3. 

We use the qtmmSendMail API to send email from the iSeries. We create a
temporary stream file in /tmp directory and supply the full path of the
stream file to the API. This has been working since we switched to using
this API mid way through 2000. When we tested sending an email under the
V5R3M0 version of the OS, we found that we could send one email then no
more. The QMSF job joblog showed that it was unsuccessful in unlinking the
temporary stream file in /tmp directory. When we ended MSF and started MSF
with the clear option we could again send one email then no more with the
QMSF job again showing the inability to unlink the temporary file.

We believe that this is occurring because the /tmp directory is defaulted 
to
have the new Restricted rename and unlink attribute set to YES and that as 
a
result the IBM-supplied QMSF user profile can no longer unlink the 
temporary
stream file after it has processed it as it could prior to V5R3M0. This
change to the /tmp directory is of course documented in the Memo to Users.

We then changed the Restricted rename and unlink attribute for /tmp to NO
and were then successfully able to send as many emails as we wished. This
workaround is fine for us, but may not be for our customers.

We feel that this change is not backwards compatible. Either the new
attribute on /tmp should have defaulted to NO or the QMSF user profile
and/or job should somehow be allowed to unlink the temporary stream files
after it has processed them no matter where they are located.

We have reported this to IBM Support.

Regards,

Kevin Wright
_______________________________________________
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.