Fwd: Re: locked file(2)

[Kenneth Brody]

On 10/8/2010 2:00 PM, Richard Kreiss wrote:
[...]
> I then accessed the file with the debugger on to see where in the auto processing the program was hanging.  It hung as the point where a lookup is done to a file called cstrack.
>
> When I tried to access this file from anywhere in filePro, it hung before any filePro prompts came up.  When I tried to delete the indexes from the command prompt, the message file being accessed by another process appeared.
>
> After their IT guys closed all the filePro associated programs that were running on the server, the indexes still had the same problem.
>
> I had them reboot the server and everything cleared up. (this was my first choice but they didn’t want to stop working for the 5 minutes the reboot takes).

Some process still had something locked.  Since you rebooted, it's too late
to determine what.  If it ever happens again, use showlock to see who has
what locked.

> Now to my question:
>
> Would this work under these circumstances?
>
> 241  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>         ◄ If:
>         Then: lookup cst = cstrack  k=16   i=K -Npxw
> 242  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>         ◄ If:         locked(cst)
>         Then:         GOTO do_end

Since the system has been rebooted, we can't tell what the actual problem
was, but I would say that no, the above would still lock if given the same
scenario.  (If it were a simple "something has a record locked", then
nothing in filePro, other than a protected, non-"-w" lookup, would block.)