Rob,

This sounds like a 'fatal embrace'.  Neither session can obtain the
necessary locks on the files to do its job so they're both waiting.  If
they haven't timed out yes, I would suggest doing a system request and
canceling your WRKOBJLCK command.

Regards,
Andy Nolen-Parkhouse

>
> I have a couple of sessions running.  On one of the sessions the
following
> command has been running for several minutes:
> clrpfm (ROUTINES/AREACDTODO)
>
> On the other session the following command has been running for
several
> minutes:
> wrkobjlck routines/areacdtodo *file
>
> Judging by WRKSYSACT the system is bored and begging for something to
do:
>                           Work with System Activity
> GDISYS
>                                                             01/29/02
> 10:34:07
> Automatic refresh in seconds  . . . . . . . . . . . . . . . . .     5
> Elapsed time . . . . :   00:00:02        Overall CPU util . . :   5.3
> Overall DB CPU util  :   .0



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.