Hi Bruce,

I am glad PINFO was able to provide some useful data.  MI is our Measurement Interface and you'd need to enable it for those items in question to work. To find out what a process is actually doing I'd first use debug, if you have PM capability. Enter the PIN in decimal, e.g. #915 and then do the trace command, "TR,d,i".  Using PINFO I'd probably use the WaitReason, BoostReason, ProcState items.

Hope this helps,
 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.

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