From:	CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 14-FEB-1989 19:01
To:	MRGATE::"ARISIA::EVERHART"
Subj:	VAX 8800 console log file


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 13 FEB 89 18:51:55 PDT
Received: from gold.bacs.indiana.edu by KL.SRI.COM with TCP; Mon, 13 Feb 89 18:34:40 PST
Date: 13 Feb 89 21:25:00 EST
From: "IVAX::IJAH400" <ijah400%ivax.decnet@gold.bacs.indiana.edu>
Subject: VAX 8800 console log file
To: "info-vax" <info-vax@kl.sri.com>

[]

Hello.  I am writing a utility for an 8800 to read or extract portions of
the operator console log from VMS (if you've ever had to wade through a
week's worth of console output by using the cursor and function keys after
getting into SHOW LOGFILE on the console, you'd understand why :-).  For
example, on our system, we mount the console hard disk under VMS as CSA3:
(writelocked with the volume name PROVOLUME).  The console log is a file,
CSA3:[CONSOLE]LOGFILE.DAT, 6001 blocks long with fixed-length 512 byte
records.  The first block appears to be a header of some sort.  Most of
the rest of the file appears to be the log data as straight ASCII text
carriage-return/line feed sequences at the end of each line of console
output.  What I have found out so far is that the first 6 16-bit words
of the first block appear to be something like this:

struct log_header {
    short int start;		/* starting block (1 to size) of log data */
    short int size;		/* total size of log file in blocks */
    short int eof_block;	/* block number of last block of log data */
    short int unused_1;		/* ?? don't know what this is */
    short int unused_2;		/* ?? nor this */
    short int eof_byte;		/* current eof byte number in eof block */
};

For FORTRANers, imagine a STRUCTURE with the short ints being INTEGER*2s
and you get the idea.  What I was wondering is if anyone else has hacked
out the format of this file, or knows what happens when the console log
"wraps" around to the beginning of the file again?  Also, some wierd
characters get stuck into this file, e.g., CTRL/Ps for some messages from
the console software, or a CTRL/Z before an OPCOM message.  A NULL seems
to always appear after an OPCOM message.  Anyone know what these mean?

     Thanks in advance,

     - Jim Harvey, IUPUI Computing Services (Indiana University)
     Internet: ijah400%ivax.decnet@gold.bacs.indiana.edu
     BITNET:   ijah400@indyvax

P.S.:  I have heard the newer 8820 machines have commands built into the
console to extract portions of the console log, or print it.  How nice of
Digital to think of that!!  Is this in fact true?  Anyone know how 63xx
machines handle the console log?

[]