Sylvia,

if you suffered this problem a couple of times already and did
not get a readable memory dump each time, you might want to get
a first rough idea of the problem by using SAT instead of DUMP.
It would at least give you a stack trace and maybe the program
name of the process that called system_abort(). Not as good as
a full memory dump, but better than nothing...

 Ctrl-B> TC
 ISL> SAT
 nmsat> cpu 0
 nmsat> dptree pin
 nmsat> trace,i,d
 nmsat> exit

If you have more than one CPU, repeat the cpu/dptree/trace for
each of them (0,1,2,etc). You don't want to write down the SAT
output (because only selected parts of it are "interesting",
so a console printer is desirable. Or else a PC connected to
the console or remote console port with "log bottom" enabled.

Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *