Avoiding lock files

[Kenneth Brody]

On 10/31/2016 3:54 PM, Rami Mantoura via Filepro-list wrote:
> the -u flag does not work. That will still sit on a record that someone is
> updating until they exit out.

That's a record lock, and the lockfile has absolutely nothing to do with 
record locks.

If you aren't modifying the file in any way, I believe the "-ro" flag you 
previously mentioned doesn't need to wait for locks, since it's running in 
read-only mode.

Another option is using PFSKIPLOCKED.  Of course, that means the records 
that were locked will be skipped.  Not usually an option you want, but it is 
available.

Other than that, you can't update a record that someone else is updating, so 
you can't "avoid" the record lock.

> I am not doing the @rn "1" for this process.
>
> On Mon, Oct 31, 2016 at 3:32 PM, Jose Lerebours via Filepro-list <
> filepro-list at lists.celestial.com> wrote:
>
>> -u flag may be what you are looking for.
>>
>> Of course, seeing the entire syntax of your command would help since some
>> reports run while sitting on a record (@rn "1" - bad practice) ...
>>
>>
>>
>>
>> On 10/31/2016 03:29 PM, Rami Mantoura via Filepro-list wrote:
>>
>>> Hi All,
>>>
>>> I am sure others have ran into this issue. I have reports that I want to
>>> run, but I always get stuck on lock files. These reports do not do any
>>> updating. I think I have tried using the "-ro" flag for read only, but I
>>> remember running into systems issues.
>>>
>>> Does anyone have suggestions or is there something I am missing.
>>>
>>> I am running Ubuntu Linux Fp ver 5.7.

-- 
Kenneth Brody