HP3000-L Archives

April 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Breitfelder, Randy" <[log in to unmask]>
Reply To:
Breitfelder, Randy
Date:
Mon, 2 Apr 2001 14:50:42 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Mark,

Did you do a start norecovery or a start recovery?

I had the same thing happen when I did a start recovery after a system
abort/memory dump on a 979/400 without AutoRestart/iX. The response center
suggested that I do a start norecovery after a system abort.

Randy Breitfelder
Nielsen Media Research

-----Original Message-----
From: Mark Bixby [mailto:[log in to unmask]]
Sent: Monday, April 02, 2001 2:29 PM
To: [log in to unmask]
Subject: [HP3000-L] extra CPUs disabled after system abort and
AutoRestart/iX?


Hi HP3000-L,

Due to popular demand, here's an on-topic technical question.  ;-)

A 989/400 that I'm using has AutoRestart/iX and dump-to-disk configured, and
it
recently had a system abort.  The system dumped to disk and restarted
without
intervention (I was watching the console), but when it came back up, the 3
extra CPUs were disabled.

Is this normal behavior for an autorestart, or is there some flag I need to
set
via PDC to tell it to always enable all CPUs?

Thanks!
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...

ATOM RSS1 RSS2