Record Is Being Updated - Access Denied

[Boaz Bezborodko]

> Date: Thu, 13 Jun 2013 14:26:15 -0400 From: Kenneth Brody 
> <kenbrody at spamcop.net> Subject: Re: Record Is Being Updated - Access 
> Denied To: Dennis Malen <dmalen at malen.com> Cc: 
> filepro-list at lists.celestial.com Message-ID: 
> <51BA0EC7.7080208 at spamcop.net> Content-Type: text/plain; 
> charset=ISO-8859-1; format=flowed On 6/13/2013 2:07 PM, Dennis Malen 
> wrote:
>> Ken,
>>
>> The following are comments concerning your three suggestions in your email
>> below:
>>
>> (1) explicitly unlocking the file.  KEN, DO YOU MEAN TO ACCESS "? - filePro
>> Directory" AND UNLOCK THE FILE? This does not work for me.
> No.  I mean to have the process that put a lock on the record to remove that
> lock.
>
>> (2), closing the file, which removes all locks - KEN, HOW DO YOU CLOSE THE
>> FILE? I KNOW HOW TO DO SO WITH A PROCESSING COMMAND. IS THAT WHAT YOU ARE
>> REFERRING TO?
> I was talking in general terms, not in filePro-specific terms.  If a process
> has a lock on a file, and closes that file, the locks are cleared.  In terms
> of filePro, if the locked record is in a lookup file, then "CLOSE
> lookupname" will have that effect.  However, since we don't know what
> process has the record locked, I can't give anything more specific.
>
>> (3) exiting (or being killed) which closes all open files - KEN, DO YOU MEAN
>> FOR EACH USER TO EXIT THE FILE. IF SO, THAT IS MY PROBLEM AS EVERYONE IS
>> LOGGED OFF WHICH IS CONFIORMED BY THE "WHO" COMMAND AND THE RECORD IS STILL
>> LOCKED.
> No, I mean for the process that has the record locked to exit.  However, we
> still don't know what process has the lock.
>
> Just because every is logged off (which isn't exactly true, since you're
> logged in) doesn't mean that every filePro process has exited.  It could be
> a process run via "cron".  It could be a background process run with
> "nohup".  It could be some "hung" process left after the user's computer
> crashed and didn't end the processes that were running on that tty.  It
> could be any number of things.  Until you run "showlock" and find the
> process, we can't give anything more specific.
>
> [...]
>
> -- Kenneth Brody

I've had situations on Windows FP (pretty rare) where a computer crash 
left the user logged into the Samba share that hosts the FP files.  The 
system showed that they were logged in twice and there was no way to 
access the previous login in order to logoff.

The only way to close the file was to kill that user connection using 
SWAT (Samba Web Admin Tool).  This also closed the file and the record 
was now accessible.

I don't know how this compares with AIX, but I offer it as a means of 
understanding what might be happening.