thanks for your insight Brian, I'll have to check my security once, more, I would hope IBM support would have seen the security issues back in August when I opened the PMR and received the first trace as I said before they assured my my security was setup correctly
Carmen Vitullo ----- Original Message ----- From: "Brian Westerman" <[email protected]> To: [email protected] Sent: Saturday, November 9, 2019 4:27:48 PM Subject: Re: JES NOTIFY EMAIL= On Fri, 8 Nov 2019 09:35:43 -0600, Carmen Vitullo <[email protected]> wrote: >David I feel your pain, we are also a TSS shop, CA (BROADCOM) has some good >doc on converting RACF to TSS, if you need I'll see if I can get the link to >you. > >my previous reply to Brian never was posted, > >agree, and what I do not understand, is the freebee software like JES2MAIL and >other paid products work well, access our SMTP passthru server with no issues, >this is not just a JES2EDS issue, but a normal notification issue from z/OSMF, >I can sent email's from OPS, from JCL batch, no issues, using the same >configuration, I'm trying to get ahead of the game and setup all the parts >pieces for z/OSMF, I suspect the notification, once we're are forced to us >this POC, will be very important. >another trace yesterday sent to level 2, SEV2 ticket still open since Aug 27th >:( > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN Yes, the problem with the new JES mail option isn't getting CSSMTP to work with it, you will likely find that you missed one of the install steps or misinterpreted the results like I did (3 times). I ended up going through the entire install 4 times before I got it "right" thinking that everything was fine each time and it turned out that while the steps all seemed to have worked, checking the content of the issued messages themselves pointed to the problem I had with the izudflt.zosmf.notification.notify part. It turned out that no one (except zosmf itself) was authorized to send the email. :( But even when it was done and completely implemented, it wasn't even as nice as the stuff you can get off the freeware tapes. It is a particular pain to have to actually add the notify card to the jobs. I think there are several better ways that it could have been handled and it could have been much more comprehensively implemented. While it doesn't "suck" per se, it's not really worth the enormous effort for such a small "feature". If you already are running z/OSMF, then adding it is not going to really be a big deal, but I don't see any part of it which is worth the effort to implement (and actually run since z/OSMF is installed for you at serverpak now), all of z/OSMF just to get the notify part. I just keep falling back to the fact that if you don't make something simple and easy to use, that most people just won't bother to use it, at least not when it counts. We made SyzMPF/z and SyzMAIL/z so that normal installation is on the order of 10 minutes or less. I can't imagine what they were thinking when they decided to design the notify feature of z/OSMF but I'm thinking that it wasn't ease of implementation or use. :) Brian Westerman Syzygy Incorporated www.SyzygyInc.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
