Re: Intermitant SMTP

Carl,

Yes, here's a section from a document I wrote for Net400 a while ago on
the SMTP flight recorders. Note that you usually need to create the data
area and view the files that get created. Some will be empty, but two or
three may have useful entries. I'll send you the entire document
separately.

Patrick
========>
If your SMTP message is getting in the QSMTPQ distribution queue but is
not getting delivered, you should check the SMTP flight recorder. There
can sometimes be helpful information in this area. The flight recorder
is a set of entries that the IBM SMTP mail system places in a user
queue. You have to dump the user queue and print the dump to read the
entries. This queue automatically wraps, so you will also need to check
this when you can be sure that there is not much activity in the SMTP
mail system. Send the message and then use these commands:

        dmpobj obj(qusrsys/qtmsflrcq1) objtype(*usrq)
        dmpobj obj(qusrsys/qtmsflrcq2) objtype(*usrq)
        dmpobj obj(qusrsys/qtmsflrcq3) objtype(*usrq)
        Dmpobj obj(qusrsys/qtmsflrcq4) objtype(*usrq)

Review the output to determine the cause of the problem.

If the above information is inadequate to solve the problem you can get
a more detailed trace by creating the QTMSTRCNTL data area. When this
data area exists the SMTP support will write detailed trace information
to trace files. Use this command to create the data area:

        Crtdtaara dtaara(qusrsys/qtmstrcntl) type(*char) len(8)
value('11111100') Text('SMTP trace')

Stop the SMTP server, wait a few minutes, and then start it again. You
can use the STRTCPSRV command to do this. After the SMTP server is
started send the message. Wait a few minutes to be sure the message has
been processed by AS/400 SMTP support. Then stop the SMTP server again.
View the trace detail with these commands:

        dsppfm file(qusrsys/qtmsflrcf1)
        dsppfm file(qusrsys/qtmsflrcf2)
        dsppfm file(qusrsys/qtmsflrcf3)
        dsppfm file(qusrsys/qtmsflrcf4)



Carl Galgano wrote:
> 
> Patrick:
> Thanks for the insight as usual.  I actually looked at the API but decided
> against it and used the SNDDST command as the heart of the product.  I am
> addressing the SMTP address at V3R7 by using something called context
> addressing that I found in one of the Redbooks.  Basically you code the SMTP
> addresses in the subject line and send the message to a user called INTERNET
> USERS that points to the external SMTP server name.  When it works it works
> great, but when it doesn't it is very difficult to find where the failure
> is.  Do you know how to turn on the "flight recorders" for SMTP?
> CJG
> Carl Galgano
> EDI Consulting Services, Inc.
> 540 Powder Springs Street
> Suite C19
> Marietta, GA  30064
> 770-422-2995
> mailto: cgalgano@ediconsulting.com
> http://www.ediconsulting.com
> EDI, Communications and AS400 Technical Consulting
> 
> -----Original Message-----
> From: Patrick Townsend <townsend@patownsend.com>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: Tuesday, August 03, 1999 8:03 PM
> Subject: Re: Intermitant SMTP
> 
> >Carl,
> >
> >Here are lots of PTFs for SMTP. You will want to be sure to put on the
> >latest cum tape and the latest database group PTF if one is available
> >for V3R7.
> >
> >I assume that when you mention the SMTP client that you are talking
> >about the QtmmSendMail API? This has to be one of the worst APIs IBM has
> >ever released. If you pass it a bad address it will fall over dead. If
> >there are delivery errors you may not get a response. I've had a long
> >conversation with IBM about the API. They have promised that it is
> >better in V4R4, but it still is a bad design. You need to be extra
> >careful to pass it email addresses that you have verified are valid.
> >
> >hth,
> >Patrick
> >
> >Carl Galgano wrote:
> >>
> >> I am having a problem with one of my clients AS400 at V3R7 concerning
> >> sending messages from the AS400 via the SMTP client.  Sometimes it works
> and
> >> sometimes it does not.  No consistency to it.  Any ideas as to perhaps we
> >> are missing a PTF?
> >> Carl
> >> Carl Galgano
> >> EDI Consulting Services, Inc.
> >> 540 Powder Springs Street
> >> Suite C19
> >> Marietta, GA  30064
> >> 770-422-2995
> >> mailto: cgalgano@ediconsulting.com
> >> http://www.ediconsulting.com
> >> EDI, Communications and AS400 Technical Consulting
> >>
> >> +---
> >> | This is the Midrange System Mailing List!
> >> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> >> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> >> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> >> | Questions should be directed to the list owner/operator:
> david@midrange.com
> >> +---
> >
> >--
> >IBM AS/400 communications, FTP automation, and network security
> >software and consulting services.
> >
> >http://www.patownsend.com
> >+---
> >| This is the Midrange System Mailing List!
> >| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> >| To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> >| Questions should be directed to the list owner/operator:
> david@midrange.com
> >+---
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

-- 
IBM AS/400 communications, FTP automation, and network security
software and consulting services.

http://www.patownsend.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---