Re: [U2] [UV] getting LISTU to show full user names or in raw for mat

[Glenn Herbert]

PORT.STATUS is pretty simple.   The master process basically takes a 
semaphore (which disallows other port.status's from starting) then sends a 
signal to each running universe process one at a time.  Each process then 
interrupts what it is currently doing, and scribbles what it is currently 
doing into the pstatbuf area of the main shared memory segment, then goes 
back to doing whatever was interrupted.  The main process then retrieves 
this info from the pstatbuf area and displays it.  Hence the large overhead 
of PORT.STATUS.

Hope this helps.

At 07:21 PM 5/6/2004, you wrote:
It is a function of the host O/S. PORT.STATUS queries the running 
processes. Those processes then have to interrupt what they are doing and 
report back to the calling process. I would have to look up the details of 
the mechanism, but IBM probably considers that information proprietary 
anyway. Suffice it to say, PORT.STATUS has a lot of overhead because of 
what it needs to do.

A bunch of programmers sitting there running repeated PORT.STATUS queries 
by hitting .X over and over will nail system's performance. So use with care.

--

Regards,

Clif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678    Web: www.oliver.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On May 6, 2004, at 10:52, Troy Buss (Logitek Systems) wrote:

This could work if it was'nt so slow.  Does anyone know why that port.status
command runs so slow?
-------
u2-users mailing list
[EMAIL PROTECTED]
http://www.u2ug.org/listinfo/u2-users
-------
u2-users mailing list
[EMAIL PROTECTED]
http://www.u2ug.org/listinfo/u2-users