On Mon, 23 Jul 2007 14:27:56 +0200, Barbara Nitz <[EMAIL PROTECTED]> wrote:
>There appears to be a strong connection to Notify operators within Netview/Automation. We have two operators defined that on the 'issuing' system aren't necessarily logged on. Whenever they are logged on, the message is delivered there and doesn't even make it into MVS! When they are not logged on or when they are set to not receive notify messages, then the message is issued by automation netview as a normal wto and then basically braodcast all around all active consoles that get info and broadcast messages (which is just about every SDSF console). >So now to get netview support to fix this stupid behaviour before we have to connect two sysplexes with each their own automation that may or may not react to messages issued on the wrong system. Life would be a lot simpler if products running on z/OS all issued messages through the operating system message service, but many -- especially NetView (and exploited by the applications riding on top of NetView) -- have their own, subject to their own rules, as you have discovered. Notify operators have been in NetView for a very long time, so I suspect you will have very little chance of changing their behavior. A better strategy might be to persuade System Automation to issue the message as an operating system WTO rather than using the NetView service. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
