HP3000-L Archives

January 2001, Week 4

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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 24 Jan 2001 12:24:59 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Re:
> Can anyone tell me what CONTROL BLOCK WAIT means?

Basically, someone is trying to procure (obtain) a lock
that is already locked.  MPE/iX relies heavily on
a data structure called variously a semaphore or control
block.

<plug>
SHOT, from Lund Performance Solutions, can show you what process owns a
lock that another process is waiting on:

:shot
SHOT: adm +waitsempin
SHOT: all
? PIN  CPU   Process Name            Pri Q Delta  %  Ic  sPIN Wait State
- --- ------ ----------------------- --- - ----- --- -- ----- ----------------
    1 s   13 PROGEN.PUB.SYS           13 A           Nn       PROGEN_GLOBAL_PORT
...
  110    341 JSMAIN.PUB.SYS          152 B           Nn       MsgPort#-32803
  111     33 AIFUTIL.PUB.SIELER      152 C           Nn   127 LONG: CNTL_BLOCK_WAIT
  112    321 CI.PUB.SYS              152 C           Nn       TERMINAL_READ_WAIT

In the above, we see that pin 111 is waiting on a control block owned by process
127.
</plug>





Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2