I agree with everything you just said. :) I also don’t personally care for the fact that JES2 has to rely on a function of z/OSMF for this feature. Give me the option to either leverage zOSMF, or a more generic option to write the notifications to a site specified JES NODE/output class that happens to have a SMTP/CSSMTP server listening on it.
I'm confident that we'll eventually "get there" with zOSMF. I just don’t have the cycles right now to plow through the security requirements for user access. That part just needs to be easier. I'd love to see something (and I'm over simplifying here), almost like the old days of omegamon where you just permitted certain prebuilt "levels" of access. The fact we are TopSecret shop doesn’t make it any easier, and I know there are cook books to assist. Oh well, I'll quit complaining. _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Brian Westerman Sent: Friday, November 8, 2019 1:37 AM To: [email protected] Subject: Re: JES NOTIFY EMAIL= One of the reasons, several years ago, that we decided not to do automated email the way IBM has implemented theirs was because the setup that we would have had to force on the client site was extremely difficult and there are several moving parts that have to all be in sync. It took me almost an entire day just to get IBM's JES NOTIFY working correctly and when I finished I was not impressed with the results. It's actually far less than I expected, but the good news is that it's not going to be any competition for SyzMFF/z or SyzEMAIl/z any time soon, if ever. :) I think IBM was trying to make it so that you can take advantage of the /* JECL and some of the job accounting fields, without resorting to exits, (which is what I did for the Syzygy Suite), but I think they ended up taking the long way around to get there, or maybe they wanted to make sure that they could support Jes2 and Jes3 (even though now they have decided to ditch JES3) with the same code layer, but I think basing anything on z/OSMF is a bad idea. Not may sites have seen any benefit that outweighs the effort and some sites don't have the extra CPU cycles to spend on it. Possibly someday z/OSMF will be better but it appears to be a slow process that part of IBM is embracing and part isn't. Also unfortunate is the amount of new stuff that is now z/OSMF only. Probably thinking sites will be forced to use it anyway, but all it really seems to be doing is turning them off. At least that's my take on what I have been hearing from our customers. Personally I like a lot of things about z/OSMF, but I think the approach IBM is taking with it is a bad idea. Brian Westerman Syzygy Incorporated www.SyzygyInc.com This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
