|
I would also like to see this document. TIA. Joe Teff Carl Galgano wrote: > > Again, thanks to Patrick! > > 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 > 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: Tom Hightower/Solutions_Inc <tomh@simas.com> > To: midrange-l@midrange.com <midrange-l@midrange.com> > Date: Thursday, December 30, 1999 10:06 PM > Subject: Re: SMTP, TCP/IP problem > > >Go for it... and what are the "flight recorders"? > > > > > > > > > > > >"Carl Galgano" <cgalgano@ediconsulting.com> on 12/30/99 08:32:49 PM > >To: MIDRANGE-L@midrange.com > >cc: > > > >Subject: Re: SMTP, TCP/IP problem > > > > > > > >You may also wish to turn on the SMTP "flight recorders". I have some info > >that Patrick Townsend graciously shared with me several months ago that I > >could post if you need it. > >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: Tom Hightower/Solutions_Inc <tomh@simas.com> > >To: midrange-l@midrange.com <midrange-l@midrange.com> > >Date: Thursday, December 30, 1999 11:34 AM > >Subject: SMTP, TCP/IP problem > > > > > >>For the past couple of days, our SMTP server has just been quitting, for > >no > >>apparent reason. A look at a QEZJOBLOG listing shows that it was ended by > >>user QTCP because it couldn't communicate with TCP/IP because of a > >protocol > >>problem. We have nothing more to go on than that. It's worked fine for > >>months. The only change we've made is to increase the number of QMSF jobs > >>to 3 > >> > >>We can ENDTCPSVR *SMTP, then STRTCPSVR *SMTP, then hold the QSTMPQ > >>distribution queue, then release the QSMTPQ distribution queue and our > >mail > >>starts routing again - until it just decides to stop (could be minutes, > >>could be several hours). > >> > >>Any clues? > >>+--- > >>| 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 > >+--- > > > > > > > > > >+--- > >| 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 > +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.