HP3000-L Archives

July 1999, Week 1

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:
Re: Impeded processes due to file locking
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 7 Jul 1999 16:32:43 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (80 lines) 
Wim asks:

> So now and then we have a problem with many processes stalled (status
> IMP in Glance). After checking we notice that one of many used KSAM
> files stays locked. With LISTF lockedfile,8 we can see a total of locks
...

> on the file (total of actual and requested locks).
> BUT what we cannot see is which process is actually locking the file.
> All the applications are build in good old COBOL!
>
> Sometimes, after waiting a few minutes, the problem disapeares by
> itself. If not, we start abortjob'ing all the impeded sessions until the
> lock is released. Not the best of solutions!
>
> Does anybody know how we can identify the locking process?? Maybe then
> we can findout where and in which application the lock isn't released.

/listf foo,8
********************
FILE: FOO.SOURCE.SIELER
2 Accessors(O:2,P:2,L:2,W:2,R:2),Share
#S131   EM,STAN.SIELER             P:1,L:1,W:1,R:1      REM : 198.102.6.11
#S122   EM,STAN.SIELER             P:1,L:1,W:1,R:1      REM : 198.102.6.11

/listf foo,9
********************
FILE: FOO.SOURCE.SIELER
2 Accessors(O:2,P:2,L:2,W:2,R:2),Share
#S131   EM,STAN.SIELER             P:1,L:1,W:1,R:1      REM : 198.102.6.11
 #P80    (FSYS.PUB.SIELER)
   ACCESS: R,W-excl          REC#: 0                    FNUM: 11
    LOCKS--Owner--   --Waiter--
                     FLOCK

#S122   EM,STAN.SIELER             P:1,L:1,W:1,R:1      REM : 198.102.6.11
 #P71    (FSYS.PUB.SIELER)
   ACCESS: R,W-excl          REC#: 0                    FNUM: 11
    LOCKS--Owner--   --Waiter--
         FLOCK

So, the above shows that process 71 has the file FLOCK'd, and process 80 is
waiting for it.

Another alternative:

<plug>

:shot
SHOT [2.22] - LPS Toolbox [A.04c]           (c) 1995 Lund Performance Solutions

For Help at the SHOT prompt enter   ?                             My PIN is 109
For NEWS, enter: HELP NEWS

MPE/iX 6.0; System started @ 12:31 on 1999-06-24
Highest PIN in use = 110, max pin possible = 8190, highest ever used = 192

...
SHOT: adm + waitsempin
SHOT: set wait CNTL_BLOCK_WAIT
(WAIT filter = CNTL_BLOCK_WAIT)
ok
SHOT: ALL
SHOT @ WED, JUL  7, 1999,  4:22 PM

? PIN  CPU   Process Name      Pri Q Delta  %  Ic  sPIN Wait State
- --- ------ ----------------- --- - ----- --- --  ---- ---------------------
   80    299 FSYS.PUB.SIELER   152 C           Nn    71 LONG: CNTL_BLOCK_WAIT
...

The above shows that my FSYS program, PIN 80, is waiting on a lock held by
process 71 (the "sPIN" column).

</plug>


--
Stan Sieler                                          [log in to unmask]
                                         http://www.allegro.com/sieler/

ATOM RSS1 RSS2