On Tue, Nov 1, 2016 at 7:40 AM, Hilary Hurwitz <[email protected]> wrote:
> Until now our site's use of email from the mainframe has been very > limited, due to security concerns. > > However I am not to be allowed to use email in a limited way. > s/not/now/ > > The JCL I was told to use was > <snip> > > > But I have a few problems with this. > If the email fails the job ends with a 0, and until a rejection email > arrives back to me, I have no idea of problems. > > I have a feeling we have a hole in the knowledge of our tcp people here. > Is this the way to work ? Surely the job should be able to know if the > email was sent? > As Allan said, this is normal. When you use SMTP, that is an _asynchronous_ process and runs with no connection to your batch job. This is one reason why we do not use SMTP. Instead we use the wonderful XMITIP by Lionel Dyck. This runs sends the email out directly from the job step (instead of IEBGENER), so you get any feedback. Now, in our case, we basically get acknowledgement from our email server (MS Exchange) that the email was accepted. If the email is for an internal (MS Exchange) user, we will get any delivery errors. However, if the email is for any "external" (to MS Exchange) user, we won't. That is why we include a "recept to" in our headers to have MS Exchange send any feedback to a special MS Exchange mailbox to which everyone in the group has access. > > I came from VSE environment where we were given responses. > Is this the best way to send emails ? > > What am I missing ? > > Hilary > > PS the jcl above works with no problems, so don't try and debug it please > ;) > OK, I won't try to debug what doesn't have any bugs. [grin]. But it is WAD, this is "working as designed" and not "working as desired". -- Heisenberg may have been here. Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
