rreport gagging on lockfile

[Kenneth Brody]

On 2/1/2010 11:23 PM, Tyler Style wrote:
[...]
> While I have the error message from rreport on one terminal and the same
> error message from rclerk on another, lockinfo will produce "There are
> NO locks on the "log_operations" key file."

All that means is that no one is updating a record.  Remember -- lockfiles 
have no correlation (none, nada, zip, zilch, zero, etc.) to record locking. 
  And, conversely, showlock/lockinfo have nothing to do with the lockfile.

Once again, however, you still haven't told us what the exact error message is.

> While every call to rreport starts off with -sr 1, there is a lookup -
> in the processing that moves it to a random record (between 1 and 180)
> as the first command to keep it from hogging the file.  Records 1-180
> all exist.

Again, this would only be an issue if the (still unspecified) error message 
were related to a locked record, and not lockfiles.

[...]

-- 
Kenneth Brody