Attachment in email - for LRECL >= 200

vasanthz · Posted: Thu Nov 05, 2009 5:13 am

Hi,

We have a requirement to generate a CSV PS FB file and email it as an attachment.
There were no problems generating the CSV PS FB file and emailing initially (LRECL = 100).

Emailing was done using IEBGENER coping to SYSOUT=(B,SMTP).

The requirements changed and I had to increase the LRECL of the PS FB dataset to 200.

Now the IEBGENER job runs fine, but I don't get the email anymore

If we reduce the LRECL it works fine.

The reason for LRECL = 200 is cos the CSV file has to contain data like,
AAAA,BBBB,CCCC,FFFF, ... in a single line.

Is it some restriction of mainframe SMTP thing that it can handle only certain LRECL max or My outlook client is unable to decipher some data

Can you please share ur thoughts on overcoming this problem pls.

Regards,

Robert Sample · Posted: Thu Nov 05, 2009 6:19 am

1000 bytes is the absolute limit for an SMTP email. I've sent and received emails with 1000 byte lines with no problems. RFC 2821 and 2822 are the guiding documents and can be found via Google.

Usually, the IEBGENER input is concatenated -- often header, body of the email, and the trailer (a single period on a line by itself). If your job has such a structure, you must update all of the concatenated data sets to use the same LRECL or the email won't go. If your changes removed the trailer, SMTP will not send the email -- the period on a line by itself to end the body is not optional.

vasanthz · Posted: Thu Nov 05, 2009 1:04 pm

Hi Robert,
Thanks for your time.

Robert Sample · Posted: Thu Nov 05, 2009 5:40 pm

The RFC standard mandates a period on a line by itself at the end of the email. Lacking that, the email is not valid for SMTP and goes nowhere.

vasanthz · Posted: Fri Nov 06, 2009 5:49 pm

Yaaay!!

"." really did the trick. Ty Robert.

Regards,

Robert Sample · Posted: Fri Nov 06, 2009 6:03 pm

Glad to hear it worked!