× 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. April 2004

RE: Checking the History log

Yes, you run DSPLOG with a bogus MSGID (###0000 probably works - it's in the CL manual previously mentioned) to force all messages to disk.

Vern

At 04:07 PM 4/22/2004, you wrote:
Mike:

It's been years since I looked at QHST log *msgq details, but I recall something along the lines of a requirement to execute DSPLOG before reading the QHSTxxx physical files. The deal was that messages still on the QHST *msgq were not yet written to the QHSTxxx files and DSPLOG caused a flush of the messages. Might be misremembered and behavior might have changed in later releases.

Regardless, if you're actually interested in items such as drive failures, I'd suggest the QSYSMSG route that was previously mentioned. Monitoring QSYSMSG is bound to be more timely than just about anything you can do with QHSTxxx.

Tom Liotta



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.