HP3000-L Archives

March 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Tue, 6 Mar 2001 11:39:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
On Mon, 5 Mar 2001 16:49:39 -0800, Russ Smith <[log in to unmask]> wrote:

>Prior to 6.0, (i.e. CSTM), we could use SYSDIAG\LOGTOOL to extract a
virtual
>console log (anything written to the console), and then use an editor or
>MPEX %PRINT/SEARCH to find specific text.
>
>Since we no longer have access to SYSDIAG, we no longer have LOGTOOL.  I
>know discussions have been held on this, but I don't remember any good
>resolutions.

LOGTOOL is still available. But on 6.5 you run it from the CI prompt.

>Does anyone have a solution to this problem?  Is there a simple way to
>interrogate and extract (in printable form) the data in the system log
>files?

There have been many programs written over the years to format system logs.
Most of them are MUCH better than LOGTOOL. However, most of them will only
format console logs.

We have a freeware program at http://www.beechglen.com named CLUE3000 that
formats console logs, optionally selecting console messages that contain a
specified string, and it runs on 6.5.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

ATOM RSS1 RSS2