Hi Phil,
 
two ideas regarding saving of console messages ...
 
#1: hardware idea
 
You might continue using LOG BOTTOM but plug the console printer port
wire into a (yet) unused DTC port and write a small program to read that
LDEV to collect the console message copies. Too much work if just need
to archive the messages for later review but the program might be used
to scan the messages on the fly and trigger immediate actions on certain
ones...
 
Sounds like a "poor man's all-3000-based OpenView", doesn't it?
 
#2: software idea
 
If you enable event 115 in system logging (inside SYSGEN LOG) then your
system logfiles will also record the console messages. You can review
them with LOGTOOL inside SYSDIAG or "export" them to a text file...
 
In LOGTOOL use STATUS DETAIL to get a list of the available logfiles and
the date and time of their first records. Pick the interesing logfiles.
 
Use LIST LOG=mm/nn TYPE=115 OUTFILE=myfile DATE TIME to extract the 115
type events (console messages) from logfiles mm thru nn and redirect the
output to MYFILE.DIAG.SYS instead of terminal. DATE and TIME give you a
prompt to narrow down the interesting range. (See HELP LIST for details)
 
The contents of MYFILE will contain quite a lot of information. I usually
extract the most interesting part (the messages like they once appeared
on the console) with :FCOPY FROM=myfile.DIAG.SYS;TO;SUBSET="(OUTPUT)".
 
The FCOPY;SUBSET is probably the most useful tip of this posting ;-)
 
Cheers, Lars/iX
 
[log in to unmask] -or- [log in to unmask]
 
(All opinions are my own and my DeskLink/3000 trial expires today... sigh)