X-no-Archive:yes

Greetings from SE Pennsylvania!

I have a real problem on our HP-3000 (aren't Mondays great for having
problems?). ;<)

Consider the following scenario which is currently happening.  A session was
performing a :VSTORE which had a bad NM :STORE label on it.  I hit BREAK,
followed by :ABORT and then things really got out of hand.  I am unable to
:ABORTIO on the tape drive (NO I/O TO ABORT); of course, I cannot :ABORTJOB on
the session; NSCONTROL KILLSESS= doesn't do a darn thing.  Here is the current
status of things:

[MANAGER.SYS]/SYS/PUB> showjob #s237

JOBNUM  STATE IPRI JIN  JLIST    INTRODUCED  JOB NAME 

#S237   EXEC        52  52       MON  9:22A  TMADIGAN,MANAGER.SYS 

JOBFENCE= 0; JLIMIT= 20; SLIMIT= 100

[MANAGER.SYS]/SYS/PUB> showproc job=#s237
No processes matched any specification. (CIERR 11504)
[mommy] [MANAGER.SYS]/SYS/PUB> showdev 7
 LDEV     AVAIL         OWNERSHIP         VOLID         DEN   ASSOCIATION

    7     UNAVAIL       #S237: 1 FILES    (Nolabel)     1600
[MANAGER.SYS]/SYS/PUB> 

The session doesn't have any processes associated with it; yet, it "owns" LDEV
7.  GLANCE/iX shows a process 362 associated with the session which is eating
the CPU alive unless I move it to a priority of 255.  Something inconsistent
is happening with the system (:SHOWPROC tells me that there are no processes;
however, GLANCE/iX does show one process which I wish the hell I could get rid
of).

I called 9-1-1 (HPRC) and was given the famous corporate line:  reboot the
system.

<boiling rage mode>

When is HP going to get off its backside and provide system managers with a
way to get rid of A SINGLE SESSION without killing the whole system???  I'm
sure that, by reading recent posts to this group, I'm not the only person
having this particular problem.  <shouting> I EXPECT BETTER FROM AN HP-3000!!!
</shouting>  If I want practice in rebooting a computer, I'll go out and buy
an el-cheapo PC, load it with any version of Windows and reboot 'til my
heart's content.  We use an HP-3000 because it is SUPPOSED to be a
transaction-processing, PRODUCTION system.  Implied with a "PRODUCTION" status
is that the system should not go down except for the most catastrophic reasons
(e.g. a disk drive went South; the processor blew up, etc.).  A single hung
session IMHO does not qualify as a catastrophic reason.  When is HP going to
recognize the following very simple equations:

     reboot <> production
     reboot = lost time, lost production, etc.

</boiling rage mode>

Thanks to everyone in this community for allowing me, once again, to get this
off my chest.  Any suggestions, short of rebooting the system, for solving
this problem would be most appreciated!!

Tom Madigan
SE Pennsylvania

"My opinions are strictly my own.  Who else would want 'em?"

____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.