There are also some start options in VTAM. These options can also be specifed as operator commands. Look in the VTAM Operations and Resource Definition Reference manuals for the syntax of these options. Some of them are ASIRFMSG, DSIRFMSG, ESIRFMSG, FSIRFMSG, LSIRFMSG, RSIRFMSG, SIRFMSG.
Usually I issue the commands to supress them after VTAM has fully started up. This way I know about problems during the initialization phase. Of course I have been bitten by problems which did not show themselves because the messages were suppressed. <g> On Wed, 30 Jan 2008 17:43:28 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >>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?! > >There is/was an option, under NETVIEW (I believe), that would supress messages in SYSLOG. >I believe it was: >SYSLOG(y/n) -- with Y as the default. > >I don't think it was/is supported by MPF. > >I think, from an audit perspective, this is not a good idea to use. >I caught a SYSPROG doing this, almost 20 years ago, when controls weren't as tight. >Almost everything he did was never journaled to SYSLOG (or the CONSOLE). >That's how I caught him. >He did something, that I knew about, and I happened to be looking at the SYSLOG under SDSF and noticed none of the messages, regarding what he did, showed up. > >- >Too busy driving to stop for gas! > ---------------------------------------------------------------------- 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
