Responding to the FLT B800 you are getting on your S959/200:

You are right.  These types of failures are known as "monitor halts" and
are trapped by hardware (as opposed to a system abort which is trapped in
software).

Usually when I trouble-shoot a monitor halt I try to get the PIM area as
the source of the greatest amount of information.  We used to be able to
find it in a memory dump but now, several hundred (it seems) processors
later, no one knows where the PIM area is located.  It is much easier to
obtain the PIM area while the system is down immediately after you have had
a monitor halt.

To dump the PIM area on a S9x9:

Reboot your system from the "CM>" with a "TC".

When you get to the "menu", select the "Service" option and go to the
service menu.

From the service menu, select the PIM option to dump the PIM area.

The PIM area for S9x9's is pretty lengthy so it would be a good idea if you
could get a screen print of it. Another alternative is to call the Response
Center and have us dial in on REMOTE CONSOLE so that we can list it and
print it.  If you can't do any of that, write down what you can and
concentrate on the 10 or 15 lines which are labeled IIA SPACE through PATH
INFO.

Once you have the PIM area dumped, it gets more difficult from here because
all of this convenient information is bit and byte hardware information
which relates directly to boards in your CPU and busses and memory and CPU
cards. If you get this error when accessing a tape drive, it is likely that
the SCSI bus where the drive is plugged into or even the drive itself is at
fault.

All that beting said, it is still possible that this is a software problem
but give the RC a call with this information and we'll be able to get a
better idea of the problem.

Bob Denham, Atlanta Response Center, System Interrupt Team
[log in to unmask]