On Jan 30, 2008, at 10:15 AM, Mark H. Young wrote:
On Tue, 29 Jan 2008 22:17:09 -0600, Rick Fochtman <[EMAIL PROTECTED]>
I always left everything in the SYSLOG and only suppressed some
messages
from the actual consoles.
I thought the whole idea of SUPPRESS was to keep them from running
across
an operator's console with all that *other* clutter, but they were
KEPT in the
SYSLOG, no?! Even with an MPFList? Not sure about what can be
accomplished with an MPF exit?
Another suggestion: If you have CA's OPSMVS product, use that.
Both suggestions are good. MPFLST is my preferred methodology for
doing so. Why, because its in *ONE* place if there is an issue you do
not have to go through 2 or 3 or more programs to find out "who".
Nothing against CA OPMVS but I always like to keep things simple. Yes
CA OPSMVS has some slick facilities but simpler things can be done
with ISPF edit of a syslog dataset. You could probably even write a
generic macro to do it.
One thing I do like about say MPFLST it forces you to go through
change control and everybody gets to see exactly what is being done.
They cannot come back at you later and bitch. It also shows your boss
that you are doing productive work. Just my opinion.
Ed
----------------------------------------------------------------------
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
