No, definitely not the case. We have 5.6 but still haven't finished testing/updating our processing on our test box.<br><br><div class="gmail_quote">On Mon, Feb 1, 2010 at 1:02 PM, John Esak <span dir="ltr"><<a href="mailto:john@valar.com">john@valar.com</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;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Any chance you are working with 5.6 filePro and once accessed
a non-locked file with a pre-5.6 version of one of the runtimes?
This would create a lockfile problem for 5.6. They do not commingle
backwards.</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font face="Arial" size="2">John</font></span></div>
<div dir="ltr" align="left"><span></span> </div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b>
filepro-list-bounces+john=<a href="http://valar.com" target="_blank">valar.com</a>@<a href="http://lists.celestial.com" target="_blank">lists.celestial.com</a>
[mailto:<a href="mailto:filepro-list-bounces%2Bjohn" target="_blank">filepro-list-bounces+john</a>=<a href="http://valar.com" target="_blank">valar.com</a>@<a href="http://lists.celestial.com" target="_blank">lists.celestial.com</a>] <b>On Behalf
Of </b>Tyler<br><b>Sent:</b> Monday, February 01, 2010 1:48 PM<br><b>To:</b>
<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br><b>Subject:</b> rreport gagging on
lockfile<br></font><br></div><div><div></div><div class="h5">
<div></div>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.<br><br>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.<br><br>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.<br><br>Anyone have any ideas on why this would have happened, and how
we might avoid it in the future? Thanks for any
input!<br><br>Tyler<br></div></div></blockquote></div>
</blockquote></div><br>