540 in 6 minutes, in and out the door, I presume ... I was just using a slow, mostly overloaded mainframe, that didn't have much CPU available ... all emails were forwarded to a mail gateway server that handled distribution to corporate or external mail servers. Taking the huge spool file apart into individual emails and creating 2 * 3000 disk datasets took most of the time. Under normal circumstances (1 email per spool file), I managed to turn around about 8 - 10 emails per minute.
Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gray, Larry - Larry A Sent: Friday, November 30, 2007 13:46 To: [email protected] Subject: Re: Send email from MVS cobol For your 3000 emails, were you sending directly to the endpoint? We processed a batch of 540 this morning in six minutes. But, I send emails to a gateway. I do not send directly to the recipient. Still using the old method of IP Mailer Address with no DNS server available. That way my email admins have to worry about all of the security problems related to email, not me. Larry Gray Large Systems Engineering Lowe's Companies 336-658-7944 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ulrich Krueger Sent: Friday, November 30, 2007 2:54 PM To: [email protected] Subject: Re: Send email from MVS cobol Larry, If email sent from the mainframe is not time-critical (i.e., users don't expect to receive their email within a couple of minutes from the time the mainframe job created it), then you don't have to do anything. However, ... At my last shop, the mainframe was used to send email for just about everything: Job completion / abend notification (time-critical, high priority emails). Production report or data file distribution to individuals or small groups of people. Mass emails (emails generated with customized info to hundreds of individuals, not time critical) (snip) The long and the short of this story is: The mainframe SMTP server can handle multiple email messages in one spool file. But if mail turnaround time is important to your shop, use only 1 mail message per spool file. You need to keep the SMTP server task turn mail messages around and not let it get bogged down doing one thing, while other activities pile up. If you have mail messages that are deemed more important than other traffic, use spool queue priorities. Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gray, Larry - Larry A Sent: Friday, November 30, 2007 10:17 To: [email protected] Subject: Re: Send email from MVS cobol We only send email from our mainframe. We do not receive. Also, only batch jobs use the SMTP process, so it does not hurt in our instance. I wrote the program (written in COBOL) we use to format the emails. When I first wrote it, it was only called from JCL for a single email, so I required people to code the DD statement. Somewhere along the way, someone found out it could be called from a COBOL program. Then someone wanted to send multiple emails per step. All of this happened without the program being changed. It's a little late now to make that change. Larry Gray ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
