RE: Checking the History log

[qsrvbas@xxxxxxxxxxxx (Tom Liotta)]

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

midrange-l-request@xxxxxxxxxxxx wrote:

>   1. Checking the History log (Mike Berman)
>
>I would like to monitor the DSPLOG on a daily basis. I would run it to a spool 
>file, change the spool file to a PF, and then read this PF for any problems. 
>Has anyone already done this, or knows which type of error messages to check 
>for? I recall some years ago that when  A DISK failed for example, there had 
>been some warning messages in the DSPLOg, that we had never noticed. I am 
>trying to write something along these lines. IT would also include any failure 
>in the night processing,

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com


__________________________________________________________________
Introducing the New Netscape Internet Service. 
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need. 

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp