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):||27 May 2017|
|PDF File Size:||11.40 Mb|
|ePub File Size:||17.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
Taking all this into consideration, a conforming message would look more like: Since I receive different results than you, perhaps it is a configuration issue.
Sign up using Email and Password. Also, the last boundary delimiter, the one that terminates the last part of the message should have two hyphens appended to it. Note that the blank lines in the above exampe are significant and that the last boundary delimiter has two trailing hypens.
Using batch SMTP command in TSO utilities
Proper usage of the boundary delimiter in a multipart message generally requires that the boundary delimiter be followed by a blank line. So it’s hard to pick the pit. Here is the JCL used: Post as a guest Name.
Still trying, thanks for your time.
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. Iebgene I execute what you have posted, I receive Raja Reddy 8 18 Email Required, but never shown.
Sign up using Facebook. QUIT Note that the blank lines in the above exampe are significant and that the last boundary delimiter has two trailing hypens. Has been the email server or client dmtp
Sign up or log in Sign up using Google. Edited the answer and removed my comment.
Could someone let me know if it is related to internal support issue or something has been deprecated with SMTP utility. Unfortunately, I do not have access to the configuration files.
The rules for the boundary subparameter are defined in RFC under multipart messages.
MVS Mail page