<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18876"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=140010120-01022010><FONT color=#0000ff
size=2 face=Arial>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 class=140010120-01022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=140010120-01022010><FONT size=2
face=Arial>John</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=140010120-01022010></SPAN> </DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B>
filepro-list-bounces+john=valar.com@lists.celestial.com
[mailto:filepro-list-bounces+john=valar.com@lists.celestial.com] <B>On Behalf
Of </B>Tyler<BR><B>Sent:</B> Monday, February 01, 2010 1:48 PM<BR><B>To:</B>
filepro-list@lists.celestial.com<BR><B>Subject:</B> rreport gagging on
lockfile<BR></FONT><BR></DIV>
<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></BLOCKQUOTE></BODY></HTML>