Re: Checking the History log

Hi Mike,

In order to trap system critical messages and have these report to
certain people or services, check out CHGSRVA (change service
attributes) and the creating of QSYSMSG. The service attributes go
hand-in-hand with QSYSMSG. You can monitor QSYSMSG as that traps most
system-critical messages.

Cheers,

Jan.

On Thu, 2004-04-22 at 18:44, Mike Berman wrote:
> 
> 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,
> 
> Thanks,
> 
> Mike
>