RE: SNDEMAIL not working

Has anything changed on the development box since it was last working?
What OS version is the development machine running? This is might be
unrelated because my problem was a result of a new OS install (V5R3) but
it might be helpful. 

http://www-912.ibm.com/supporthome.nsf/document/10000035 
Look or search for number II13869. It states the following.

Abstract
TCPIP-SMTP-MSGTCP5104-T/QTMMCUTL 

Error Description
**Last updated 05/18/04 **                                      
5722SS100 5722TC100 r530                                        
V5R3 has a new IFS directory attribute "Restricted rename and   
unlink". If this is set to *YES QMSF can fail with TCP5104      
Integrated File System file unlink failed" for /tmp/... on      
QtmmSendMail users.                                             
The default value for the new attribute is *NO on the CRTDIR    
(MD) command. However, we set the attribute for *YES when we    
have to create it, such as on scratch installs or some other    
instance where the directory has been deleted. Slip installs    
should not be affected, provided slipping the GA resave. Once   
the attribute is set, it will remain set. This is compatible    
with UNIX implementations and is documented in the Memo-To-Users
If the attribute is set to *YES and is causing QMSF to fail,    
change it to *NO using the CHGATR command:                      
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)                  
May see msgTCP5101 TCP5101 in job log.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Tuesday, December 20, 2005 1:49 PM
To: Midrange Systems Technical Discussion
Subject: RE: SNDEMAIL not working

I forgot to mention that I did a *clear on the STRMSF already.  That was
one of the first things I tried.  In fact I've probably done it about a
dozen times in futility. 

Michael Smith
iSeries.mySeries.


-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@xxxxxxxxxxxxxxx] 
Sent: Tuesday, December 20, 2005 2:44 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SNDEMAIL not working


If you don't mind losing all the emails that you've been trying to send,
you might use the *CLEAR option on the STRMSF command.  This will purge
out all the messages that gum up the works...  Once cleared, perhaps
your sndemail will work again.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Smith, Mike
Sent: Tuesday, December 20, 2005 1:37 PM
To: midrange-l@xxxxxxxxxxxx
Subject: SNDEMAIL not working


I'm about at wits end.  
We have 2 Iseries.  1 production, 1 development. 
SNDEMAIL works just dandy on the production machine.  SNDEMAIL does not
work on the development machine(although it used to.  Not sure when it
quit)

I have had my network guy look and he hasn't been able to figure out the
problem yet.  
I have stopped, started MSF, SMTP.  
I can find nothing to indicate any problems, yet it still doesn't work.


I tried to do an TRCTCPAPP APP(*SMTPCLT) SET(*ON) HOST(RGT), but I
couldn't figure out how to get any results.  When I did a SET(*CHK) it
told me Data capture not begun for *SMTPCLT.  

Not sure how relevent this is, but the network guy was able to Telnet to
the mail server from the development machine and hand key an email that
was delivered.  

I have turned on SMTP journaling and tried to send an email.  I have
been reviewing the journal entries, but I don't see anything in there to
indicate a problem.  Although I could easily be missing something.  

So my initial question is, that since I know it works on Production.  Is
there any easy way to compare relevent Settings on the 2 machines to see
if I can identify anything out of wack.  

Secondly, anything else you can think of I can check.  

I'm pretty sure this is where the problem is, I just haven't been able
to track it down yet.  

Incidentally SNDDST doesn't seem to work either.  

Michael Smith
iSeries.mySeries.