I’m trying to use SMTP to send emails using IBM JCL (IEBGENER). This is the JCL I’m using.I’m getting INVALID COMMAND errors on the. The data termination in SMTP step is period “.”. So keep on repeating these and you can create multiple emails. //IEBGENER JOB ACCT,’DATA. I suspect that your SMTP service was upgraded and may have become more sensitive to errors in setting up messages — your example has a few.
|Published (Last):||22 January 2018|
|PDF File Size:||12.67 Mb|
|ePub File Size:||4.54 Mb|
|Price:||Free* [*Free Regsitration Required]|
My bad, you’re right.
Raja Reddy 8 18 Also, the last boundary delimiter, the one that terminates the last part of the message should have two hyphens appended to it. All one physical line, just as shown.
IBM MAINFRAME & MVS FORUM
Here is the JCL used:. Post as a ibgener Name. I suspect that your SMTP service was upgraded and may have become more sensitive to errors in setting up messages — your example has a few Could someone let me know if it is related to internal support issue or something has been deprecated with SMTP utility. Sign up or log in Sign up using Google.
Sign up using Facebook.
Taking all this into consideration, a conforming message would look more like: Here is the JCL used: The boundary subparameter of the Content-type parameter relates to multipart messages it is the boundary delimiter between message xmtp. Note that the blank lines in the above exampe are significant and that the last boundary delimiter has two trailing hypens. Email Required, but never shown.
Email is sent with no body content via SMTP on Mainframe – Stack Overflow
All of sudden body content of the email is blank and shows no data, Email is being sent but without body content in the email but subject line is apprpriate. Surprisingly, It has worked till couple of days ago. When I execute what you have posted, I receive The rules for the boundary subparameter are defined in RFC under multipart messages. Edited the answer and removed my comment. Unfortunately, I do not have access to the configuration files.
The Content-type of your message is not multipart so I imagine that “support” for the boundary subparameter may have been dropped yielding unpredictable results. Sign up using Email and Password. Still trying, thanks for your time. So it’s hard to pick the pit.