rreport gagging on lockfile

[Kenneth Brody]

On 2/3/2010 10:49 PM, Richard Kreiss wrote:
> One thought, is it possible that for some reason *report is hitting the
> record you are standing on?

Once again:

     Lockfile != record locking.

> This is like trying to run an output using a system call from @key on the
> record you are looking at.  You can't do this as @key locks the record and
> even with -u as part of the system command, a locked messages occurs.

This is a lockfile issue, where the lockfile says another *report is 
running.  This has nothing to do with record locking.

You are correct that the "-u" flag will have no affect on record locking, as 
the "-u" flag only affects how the lockfile is treated.

[...]
> *** A filePro Error Has Occurred ***
>
> On File: /hd1/hd1/appl/filepro/log_operations/lockfile
>
> Request Output with Processing Function Running On This File
>
> File not available.
> Somebody else is modifying the file;  try again later.
[...]