RE: Simple Console

["Shaw, David" <dshaw@xxxxxxxxxxx>]

-----Original Message-----
>From: John P. Walsh [mailto:john_walsh@icdc.com]
>
>I have to wonder if putting QSYSOPR in break mode will defeat the purpose.
>There are a lot of messages generated there and for the most part they can
>be ignored.  It seems to me that you would like to made aware of only those
>messages that need a reply.

Typically when putting QSYSOPR in break mode, one sets the severity code level
at a reasonable level so that informational messages don't break.  The default
when QSYSOPR signs on is 40, I believe, but I think that inquiry messages are
normally 70 or higher, so one could go that high if desired.  Of course, only
one workstation can have QSYSOPR in break mode at a time.  Typically people who
need more than that use break-handling or pager programs to forward desired
messages to the appropriate folks.  We use Bytware's MessengerPlus pager
software for that, and it works very well.

>Just today my IBM CE installed Service Directore functions that will
>generate messages to four usernames upon certain events happening.  It also
>sends a message to Rochester concerning the system event.  In theory they
>will then contact me.  Unfortunately, the internal messages are not sent in
>break mode as I would like.
>
>Does anyone know of a way to have these Service Directore generated messages
>sent in break mode?

Put the message queues that they're sent to into break mode.

Dave Shaw
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---