Re: WORKING_SET.COM gives all COM states when run at high priority

_at_SendSpamHere.ORG
Date: 06/30/05 

Date: Thu, 30 Jun 2005 14:05:35 GMT

In article <42C36821.2070605@bigpond.com>, David B Sneddon - bigpond <dbsneddon@bigpond.com> writes:
>AEF mentioned in passing:
>>
>> Jeff Chimene wrote:
>>
>>>AEF wrote:
>>>
>>>>Hello,
>>>>
>>>>WORKING_SET.COM, which is in SYS$EXAMPLES, lists all processes and
>>>>various working set statistics for each. I recently found out that when
>>>>you run it at high priority, most or all of the states show up as COM.
>>>>The state is determined by the function
>>>>
>>>> f$getjpi("","STATE")
>>>>
>>>>The higher the priority, the higher the percentage of states which are
>>>>reported as COM.
>>>>
>>>>Why should the result of this function be dependent on the priority at
>>>>which it is run?
>>>
>>>Because your process running working_set.com is using all the CPU? All
>>>other processes are forced to non-CUR states, e.g. COM
>>>
>>>For extra credit, code up a real-time CPU-burner that also
>>>allocates/frees a few mebibytes of VM. Fire off a few of those and watch
>>>with working_set.com
>>>
>>>Cheers,
>>>jec
>>
>>
>> Thanks for your rapid response! But some of my processes are idle
>> terminal sessions. Why are they waiting for the CPU?
>
>Does $GETJPI not operate within the context of the process
>you want the information about? In which case that process
>would need to "run" to return the information...

It depends upon the information that you want to gather. Some of
what $GETJPI gathers can be obtained from JIB, PCB or PHD. If it
is something in the process context, that needs to be gethered via
an AST and that would require that the process becomes computable. 

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM
           
  "Well my son, life is like a beanstalk, isn't it?"

Relevant Pages