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?

[EMAIL PROTECTED] wrote:
According to manual (MVS Programming: Authorized Assembler Services Reference, Volume 4 (SETFRR-WTOR) SA22-7612-04), if you are in supervisor state, use MCSFLAG=NOCPY.

Else you have no resort.  HDRCPY is the SDSF LOG.

----- Todd Burch <[EMAIL PROTECTED]> on 07/14/2005 02:35 PM -----

Hello esteemed sysprog gurus,

How do I issue a WTO and have the output NOT go to the console? (When I say
console, I'm referring to SDSF's "log" command)

I do want the WTO output in my joblog, but I would prefer to keep the
console clutter to a minimum.

Currently, I'm using DESC=(6) and ROUTCDE=(11).   I've tried
MCSFLAG=(HDRCPY) and (NOCOPY) but neither cut the mustard.


-----------------------------------------
The information contained in this communication (including any attachments
hereto) is confidential and is intended solely for the personal and
confidential use of the individual or entity to whom it is addressed.  The
information may also constitute a legally privileged confidential
communication.  If the reader of this message is not the intended recipient
or an agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this communication in error and
that any review, dissemination, copying, or unauthorized use of this
information, or the taking of any action in reliance on the contents of
this information is strictly prohibited.  If you have received this
communication in error, please notify us immediately by e-mail, and delete
the original message.  Thank you

----------------------------------------------------------------------
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


----------------------------------------------------------------------
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

Reply via email to