On Thu, Feb 27, 2014 at 4:38 PM, Ed Gould <[email protected]> wrote:
> Don: > > Great pointer, thanks. > > John M: I am not clear as to why you need this. I do not think that a > system resource should be used for sending reports to . Seems dubious at > best. > There are products like RMDS (and others) that would seem more apropos. > Ed > > I wasn't thinking of using this for reports. It was more as an alternative to doing a WTO ROUTCDE=11 for "status type messages", such as MSG0001I STCNAME USER BUBBA LOGGED ON FROM IP 127.0.0.1 ... MSG0002I STCNAME USER BABBA LOGGED OFF FROM IP 127.0.0.1 Just as an example. Like IEF403I and IEF404I messages go to SYSLOG for job started / job ended. Now, the question you might have is "why would anybody want to do THAT?". One reason is that the UNIX syslog messages can be easily archived or simply removed. They are just UNIX files in a directory. But one thing different is that the z/OS SYSLOG daemon can "relay" messages to another SYSLOG daemon. And then that SYSLOG daemon could write the message to a "master consolidated SYSLOG file". Or, at least in the case of "syslog-ng" on Linux, can be piped to UNIX command for processing. I don't really know exactly what I might do with this information. I have some weird ideas on many occasions. Perhaps these messages would be easily accessible via the Internet, without the need to have z/OS accessible to the outside world. Or implement some sort of RSS-like feed so that a person at home could have a "reader" up which would display messages of interest. There may be other, easier ways to do this that I am simply not aware of. But imagine scripting this type of feed so that your computer would play some recording when it receives particular status messages. Wouldn't it be nice for a product control person to have his PC be able to say "Production Job ... has just abended" when it get a particular message? Rather than them having their TSO session disrupted by an automated SEND command. In our shop, we don't have sufficient people to monitor the system 24x7. But we run 24x7. So it would be very nice if the "on call" person could have something running on their home PC which could "log on" to a secure, Internet accessible, server and then be able to alert them with a voice message when something vital occurs. This way they could "monitor" the system off hours while still being away from the PC. Just one of my weird thoughts. In any case, I was just curious if anyone else was interested. I do come up with "technically interesting", but useless ideas. -- Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
