My first bit of advice is that next time you should move not move the
console. The console is hardwired to the CPU no network, LAN or other
communication system is between it and the CPU. If there is a problem you
don't want to have to deal with connection problems as well as the original
problem.

I am not sure what you mean by a "dummy ldev" but if you mean an ldev that
did not physically exist then that might be your problem. I am not sure how
console messages would have been handled in that case. I have seen a system
crash because the operator left a LISTF in a pause state (CTRL S.) If the
message file was getting full then it may have taken a while to process the
messages and hence you were hung. After 10 minutes it had processed the
messages and "unhung" itself.

However, my basic premise may be totally incorrect.

-----Original Message-----
From:   HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Chana, Harpreet TCS1C
Sent:   Wednesday, December 20, 2000 2:04 AM
To:     [log in to unmask]
Subject:        [HP3000-L] Moving of CONSOLE

Hi,

I was working in NMMGR on console. so I was getting the console messages in
the screen. So I moved to the console to dummy Ldve. After finishing my work
when I called back to console from that device. Console was hanged. After
pressing the CTRL-B cpu status was normal, I tried to open new session from
an other terminal, that was also hanged. it happened for 10 minutes. After
10 minutes every thing was normal.  ??

Any IDEA about ??

With Warm Regards

Harpreet Singh Chana