Problem with V5R3 - /tmp directory & qtmmSendMail

[Kevin Wright <Kevin.Wright@xxxxxxxxxxxx>]

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