<!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=640093822-01022010><FONT color=#0000ff
size=2 face=Arial>1. Okay, be more specific. You say you are using the lockinfo
script. So, you can see exactly which record is being locked by exactly
which binary. What does it show? Record 1 by dclerk, or record 1 by
dreport.... exactly what does lockinfo show.... by any chance are you locking
record 0? Not something you could do specificially, but filePro does this
from time to time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010> </SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT color=#0000ff
size=2 face=Arial>2. It's always easier when people say this has worked for
years. So, it must be something new added to the soup. Have you
removed an index, grown a field and not changed the size an index pointing to
it. Gone past some imposed time barrier? Used up too many licenses?
Exceeded some quota in some parameter? Added groups or changed
permissions? Run a fixmog (fix permissions)? Has a binary failed
like dclerk and you've replaced it with a different copy? Has the -u
flag any immpact on your scenario? I'm assuming a lot because you haven't
specifically shown how you are doing things? Is this happening from a
system call?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2 face=Arial>I
agree that the code would not seem to be importatn since it has worked...
before, so again, it seems like the environment has changed somehow. Maybe
if we saw the whole setup, relevant code and all we could give more
suggestions. Oh, I just thought of one... is it possible you are looking
up to a particular record, say record 1... and that record is not there
anymore?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2 face=Arial>I
don't know, I'm shooting in the dark without the specifics.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=640093822-01022010><FONT size=2
face=Arial>John</FONT></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 3:18 PM<BR><B>To:</B>
filepro-list@lists.celestial.com<BR><B>Subject:</B> re: rreport gagging on
lockfile<BR></FONT><BR></DIV>
<DIV></DIV>
<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
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>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
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote><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></BLOCKQUOTE></BODY></HTML>