Ah, OK. So I get some PUA0: errors ticking up every
so often, most
of which are right after the system has had some "hiccup" of non-
interactivity for several minutes. Some initial research indicates
that the PU device is the UDA controller, which is what I believe
the CQD-220 masquerades as (more or less). Right now, after three
hours of sitting basically idle, it's logged 26 errors.
So I'll have to check that out. It could be something as simple as
balky SCSI termination, since I do have 4 devices in the chain and
the terminator is a Jaz drive using internal termination. I'll
play with it some. Hopefully it's not the hard drive going bad,
since my supply of SCSI drives is essentially dry. It's a bit
worrisome that it's the PU device going bad rather than the DU
device, but I'm not 100% sure how VMS logs the errors, so it could
be what I suspect.
VMS has a process called ERRFMT which logs errors in a binary file called
sys$errorlog:errlog.sys - the way to get a detailed human readable report of
the contents of that file used to be ANALYZE /ERROR but I don't think that
works any more. Maybe someone else can chime in and suggest what the current
way is.
Keep an eye out also for operator messages relating to the PU and DU devices
after doing a REPLY /ENABLE, SET TERMINAL, SET BROADCAST etc.
Regards,
Peter Coghlan.