<div class="gmail_quote"><div class="gmail_quote">On Mon, Feb 1, 2010 at 1:13 PM, <a href="mailto:Rkreiss@verizon.net" target="_blank">Rkreiss@verizon.net</a>] <span dir="ltr"><<a href="mailto:rkreiss@verizon.net" target="_blank">rkreiss@verizon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Is your processing using one record? Is so, could that record be locked?<br>
<br>
Richard Kreiss<br></blockquote><div><br>Yes, it's using one record, but that is definitely not the problem - we've been doing it this way for years. <br>
<br>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. <br>
<br>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.<br><br>Tyler<br><br><br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><div></div><div><br>
-----Original Message-----<br>
From: Tyler <<a href="mailto:tyler.style@gmail.com" target="_blank">tyler.style@gmail.com</a>><br>
Sent: Monday, February 01, 2010 1:47 PM<br>
To: <a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
Subject: rreport gagging on lockfile<br>
<br>
We suddenly started having a problem a week ago with a piece of logging<br>
software that has run perfectly for years. Every time a script or<br>
processing ran that used it, it would bomb out with a message that the file<br>
was locked by output processing.<br>
<br>
After some hemming and hawing, it was determined that the lockfile status<br>
wasn't being read correctly. rreport was hung on the lockfile message, and<br>
trying to access it via rclerk kicked you immediately with the same<br>
message. However, the lockfile script showed that the file wasn't actually<br>
locked.<br>
<br>
We manually deleted the lockfile and re-ran a report that had been<br>
previously gagging so that filepro (v5.0.1.14 on SCO Openserver 6) could<br>
recreate it. Suddenly everything is fine.<br>
<br>
Anyone have any ideas on why this would have happened, and how we might<br>
avoid it in the future? Thanks for any input!<br>
<br>
Tyler<br>
<br>
</div></div></blockquote></div><br>
</div><br>