rreport gagging on lockfile

[Tyler]

On Mon, Feb 1, 2010 at 1:13 PM, Rkreiss at verizon.net] <rkreiss at verizon.net>wrote:

> Is your processing using one record?  Is so, could that record be locked?
>
> Richard Kreiss
>

Yes, it's using one record, but that is definitely not the problem - we've
been doing it this way for years.

And as I stated in my original email, the file/record isn't actually locked
if you look at the lockfile itself or use the lockinfo script - filePro just
seems to think it is regardless.

Also, if that was the case then after deleting the lockfile and re-running
the processing we should be getting the same lock error message; we are not.

Tyler






>
>
> -----Original Message-----
> From: Tyler <tyler.style at gmail.com>
> Sent: Monday, February 01, 2010 1:47 PM
> To: filepro-list at lists.celestial.com
> Subject: rreport gagging on lockfile
>
> We suddenly started having a problem a week ago with a piece of logging
> software that has run perfectly for years.  Every time a script or
> processing ran that used it, it would bomb out with a message that the file
> was locked by output processing.
>
> After some hemming and hawing, it was determined that the lockfile status
> wasn't being read correctly. rreport was hung on the lockfile message, and
> trying to access it via rclerk kicked you immediately with the same
> message.  However, the lockfile script showed that the file wasn't actually
> locked.
>
> We manually deleted the lockfile and re-ran a report that had been
> previously gagging so that filepro (v5.0.1.14 on SCO Openserver 6) could
> recreate it.  Suddenly everything is fine.
>
> Anyone have any ideas on why this would have happened, and how we might
> avoid it in the future?  Thanks for any input!
>
> Tyler
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20100201/639bddab/attachment.html