The system logfiles don't provide all messages. Even CONMSG doesn't provide
every boot message. The best examples are the transaction manager recovery
messages. The recovery can fail, (the volume set is read only), and the
only indication is a console message that rolls off and is not logged.
 
I highly suggest having a printer slaved to the console for boot up
processing. Many system hangs and aborts result from disc related problems.
The worst indication usually comes at boot time when a volume is
unavailable for mounting. In the old days the "mount correct volumes or
reload" message usually meant a disc had crashed. Today you could loose a
disc and not be aware of it until much later.
 
btw
 
Does anyone know how to configure ldev 10 (the streams device) so that it
does not show up as unavailable?
 
 
 
---- End of forwarded message ----