|
Hi Wayne, Without looking at the code for the Mmail utility I can only guess. If it is using the QtmmSendMail API then it needs to create a MIME-encoded file somewhere in the IFS. When the API returns control, it has not really sent the email, it has queued it for processing and unlinking (don't ask about this in /tmp!) somewhat asynchronously by the MSF subsystem. If the same IFS file name is used each time, then the 5 second delay is there to (hopefully) allow the MSF subsystem to actually send the email and unlink the stream file. Where I have coded using QtmmSendMail, I have attempted to use a unique file name for each MIME-encoded IFS file to take into account the asynchronous implementation of the email processing kicked off by the QtmmSendMail API. Regards, Kevin Wright. > -----Original Message----- > From: wache [mailto:wache@xxxxxxxxxxx] > Sent: Tuesday, 14 March 2006 8:58 AM > To: Midrange Systems Technical Discussion > Subject: Mmail Utility > > > Fyi and help. Is anyone out there using Mmail Utility to send > batches of Emails out. I tried this for the first time today. > To my surprise it took the As/400 (Mmail) > 4 hours to send approximately 2750 Emails that used an html > variable template. That part was neither here nor there. I > was watching the job run and noticed a dly 5 > As the process that was running most of the time. I realized > the utility was doing a dlyjob for 5 seconds somewhere. It > seems I found it in the procedure XXXmailsnd the doumentation > in the source says the delay job prevents SMF from getting > confused during a mass mailing is SMF really MSF I don't > know. Either way is the delay of 5 seconds really necessary. > It makes using this utility prohibitive on large scale > mailings from the As400. Thanks in advance for anyone that can help. > > Wayne Achenbaum > Slomin's Inc.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.