I'm happy to provide an explanation for the reason for my question. I work for Allen System Group, in the mainframe group that used to be Landmark. Several of the products we produce use WTOs for trace messages. In a development environment, with multiple products running in diagnostic mode all the time, all producing reams of diagnostic messages via WTO, simply pressing enter in SDSF while browsing syslog can cause you to have to scroll down several hundred lines. It makes finding things of interest (system events not directly related to a product's job log) more difficult.
I have no answer for "is there a reason I want to use WTOs..." other than what Walter Cronkite used to say every evening... that's the way it is. So, for these multitudes trace messages, the intended target is the developer and/or the support organization. Thank you all again. Todd ----- Original Message ----- From: "John S. Giltner, Jr." <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Saturday, July 16, 2005 7:58 AM Subject: Re: Keeping my started task's WTO output off the console? > Based on what I think you want to do, as Sam said, you need a MPF exit. > Even then, I'm not sure you can get it in the joblog and not into > syslog. I never had a reason to have a message in the joblog and not in > syslog, so I have never looked, I have always just assumed that > everthing in the joblog was always written to syslog. > > WTO is Write to Operator. In this case the "operator" is the console > and syslog. The SDSF "log" is syslog. > > Is there a reason that you want to use WTO and NOT have it show up in > the syslog? The whole reason for WTO is to let the operators know what > is going on. If you don't want the message on the console or in syslog, > who is the intended target for the message? > ---------------------------------------------------------------------- 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
