HP3000-L Archives

April 2004, Week 2

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:
Bruce Collins <[log in to unmask]>
Reply To:
Bruce Collins <[log in to unmask]>
Date:
Tue, 13 Apr 2004 12:22:28 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Hi Jeff,

Yesterday, we had a job that couldn't be aborted so I tried some of the
PINFO calls that you suggested to get some more information and sure enough,
CriticalDepth and SystemDepth were = 2.

According to the PINFO HELP, CriticalDepth > 0 means that the process is
critical and cannot be aborted, and SystemDepth > 0 means in system code. Is
there anywhere where we can get more information about what the PIN is
doing? We eventually got the job to abort by aborting some of the other
executing jobs but we don't really which one was causing the problem.

In the process of investigating the problem, I put some of these PINFO calls
into a command file. I haven't been able to get FmtWaitMilliSec to work. It
always seems to return 00:00.000. The documentation for WaitMilliSec says
"need MI". I also notices that for WaitReason, the first 7 require MI.

What is MI? It doesn't seem to be a capability and I can't find any other
reference to in the documentation.

----------------------------------------------------------------------------
-------
Bruce Collins                        <[log in to unmask]>
Technical Specialist             Phone : (514) 273-0008
Lee Merrick & Assoc.          Fax      : (514) 273-0199
----------------------------------------------------------------------------
-------



----------------------
Jeff Vance wrote:

The new PINFO CI function, in release 7.0 Exp 1, shows many properties of a
process.
See
http://jazz.external.hp.com/papers/Communicator/7.0/exp1/ci_enhancements.html
for more info.

You might try:
  calc pinfo(915,"CriticalDepth")
       pinfo(915,"ExecState")
       pinfo(915,"HasSIR")
       pinfo(915,"MPEPri")
       pinfo(915,"NumOpenFiles")
       pinfo(915,"PendingIOCount")
       pinfo(915,"ProcState")
       pinfo(915,"SystemDepth")
       pinfo(915,"WaitReason")

Hope this helps,
 Jeff Vance, vCSY

Scott writes:
> I have a job that's STUCK doing a large Quiz extract and  will not
> abort with ABORTJOB  I've used glance to get the PIN and tried
> ABORTPROC on it also, I get:
>
> ABORTPROC PIN=915
> There is already an ABORT pending for pin "915". (CIWARN 11015)

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

ATOM RSS1 RSS2