-------------------------------------<snip>--------------------------------
As part of the Console Restructure, we enhanced the handling of MONITOR
messages so that automation programs could receive the messages without
the messages having to be written to the SYSLOG or OPERLOG.
Unfortunately, it appears that if you create an entry in MPFLSTxx for a
MONITOR message (say IEF403I) and MONITOR processing has requested that
the message be issued no hardcopy, MPF will override the no hardcopy and
force the message to be hardcopied.
To make a long story short: we are proposing to change MPF processing so
that it no longer forces matching messages to hardcopy. If a message is
issued requesting that the message be hardcopied (the default), MPF will
honor it; if the message is issued requesting that the message not be
hardcopied, MPF will no longer override the request (forcing the message
to be hardcopied).
-----------------------------------<unsnip>------------------------------------
I would have a problem with this. My management looks upon SYSLOG as the
"Holy of Holies" as far as message/commands are concerned. If I can't
force ALL messages to SYSLOG, my management will go absolutely
BALLISTIC. I don't mind using a little BAL code to set bits, but make
sure that I'll be able to force all messages to SYSLOG.
Rick
----------------------------------------------------------------------
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
