|
Hello Mike, - As Martin mentions in his reply, reading the history log files directly is much faster than using the spooled file/PF-method. If you're interested I can email you an example of how to read and extract the information from the history log files. Best regards, Carsten Flensburg ----- Original Message ----- From: "Mike Berman" <mikeba777@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, April 22, 2004 6:44 PM Subject: Checking the History log 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, ########################################### This message has been scanned by F-Secure Anti-Virus for Internet Mail. For more information, connect to http://www.F-Secure.com/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.