agree !
I really thought JES2 Email Delivery was gonna be straight forward, easy
to setup, I"m not sure why z/osmf needed to be the vehicle for email
delivery, I agree, why more overhead, why Java?
I wanted to use the notification facility on z/osmf with the workflows,
but apparently this didn't work as I expected when trying to assign
workflow tasks to other users.
most of my users will continue to use JES2MAIL or some other tool, and
I'm ok with that, I don't want to get called in the middle of the night
because suddenly JES2EDS is not able to send out notifications via email.
Carmen
On 1/19/2022 2:49 PM, Brian Westerman wrote:
You're correct, that you need to code that card and use JESEDS, and that was my
point. None of that was really necessary, which is why we developed
SyzMail/z. Actually we developed it several years before IBM, and I still
wonder why IBM came up with such a convoluted way to send email when it could
have been done without any JCL or the overhead of z/OSMF at all. It's almost
like they had z/OSMF in their back pocket and were trying to think of something
to make people want to use it.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
--
/I am not bound to win, but I am bound to be true. I am not bound to
succeed, but I am bound to live by the light that I have. I must stand
with anybody that stands right, and stand with him while he is right,
and part with him when he goes wrong. *Abraham Lincoln*/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
