Kevin, >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. The thing is that whatever issues the messages is sensitive to the underlying operating system (or not, as the case my be). We started to discover messages going to the netlog (networks netview, as opposed to aoflog - automation netview) when we migrated to SA/390 V3.1 (from 2.3). z/OS was 1.6, NetView was 5.1. My networks colleage grumbled, but it didn't have impact (other than the same messages appearing in every last one of his EMCS consoles). Now we are forced to use automation subplexing (which according to IBM we implemented correctly), but Automation messages (most notably aof100i, issued every ten minutes, but others, too) not only appears in netlog, it also appears in the aoflog of the other subplex, where it might have quite a lot of undesired results. These are only messages issued by automation on the z/OS 1.6 system, when the notify operator was not logged on or deleted. Last week we had that system upgraded to z/OS 1.8, too, to make an all-1.8 sysplex. No notify op logged on. In that case, the message appeared where it should, and only there - in the correct automation netview and in syslog of that system. While SYSOPS ctracing this message, I also discovered the DIDOCS EMCS console. Once a notify op is logged on (under z/OS 1.6), the message is NOT issued via WTO at all! (It is issued via WTO under z/OS 1.8, regardless of the notify op being logged on or off). But when under 1.6 no notify op is logged on, it is basically broadcast (the broadcast and info flags were on in the WQE) to all active EMCS consoles that have these attributes (I believe that includes all SDSF default consoles and also many automation/netview consoles). And I am making no progress whatsoever to get IBM to see that (and I think the ETR has already more than 72 pages) and take action against it. Regards, Barbara -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ---------------------------------------------------------------------- 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
