× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2003

RE: MONMSG not monitoring

Hi Tom,

>Thanks.  I did not know you could find the 
>monitorable messages on the help, was it 
>recently added?

It's been there for quite a while now; I don't recall when it was added.

>Regarding the problem . . . Given that this is the only thing going on
>on the system after hours the purchase of software to manage QSYSOPR is
>overkill.  Any thoughts regarding the wisdom of adding an entry to the
>SYSRPYL for this message?  At that point the *escape message should get
>back to the program, right?

It doesn't hurt to try to give iSeries software houses a bit of business.
One never knows.  Anyway, I would hesitate to use the SYSRPYL for this
application.  I'm not one to blindly terminate a running process without
having a person look at it first.  As Bob says, a break handling program
seems more the order of the day.
  --buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.