[Info-vax] Error logging on VMS

[Stephen Hoffman]

On 2021-08-23 17:49:04 +0000, Simon Clubley said:

> I needed to spend some time in the error logging system this weekend 
> and I now have some questions and comments.
> ...
> Should VMS be altered (if possible) to copy those error counters 
> somewhere permanent so they always show up in "show error" until the 
> counters are manually reset by the system manager ?

The drivers request error logging, and there's a bit that can be set to 
copy a buffer into the error logs.

Many of the existing device drivers don't implement or don't request 
much in the way of error logging. (Doc here is murky at best too, 
having just looked at it again.)

Among those drivers that do log, formatting the logged errors has been 
an ongoing problem as differing formats and firmware and contents and 
the rest of the morass all stop by for a visit.

For tooling, early on was SYE, and then a couple of different add-on 
error-related products became available and later faded, so OpenVMS 
added the ELV tool to translate errors from core parts.

DIAGNOSE and WEBES / SEA were two of the tools here, SNMP and MIBs 
touch on this area, and there were and are other tools in this same 
area.

HP and HPE have gone toward RedFish/DMTF more recently, which touches 
on these same error-logging and hardware configuration areas.

This, startup and shutdown, IP integration (SNMP, IPMI, DMTF, etc), and 
other server management-related areas—not the least of which are 
operator comms—all need some work.

As has been discussed in various threads.

But... After the port.

Once VSI figures out what they're going to work on next, post-port.

If not the Arm port. 🤷🏼


-- 
Pure Personal Opinion | HoffmanLabs LLC