<!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=515560821-03022010><FONT color=#0000ff
size=2 face=Arial>No problem, sometimes insights turn into fixes... other times
not.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT color=#0000ff
size=2 face=Arial>About the syntax ...</FONT></SPAN><SPAN
class=515560821-03022010><FONT color=#0000ff size=2 face=Arial>Yes, sorry, on my
system, for whatever reason I "saw" only one set of quotes after the -r... now I
can tell there is an apostrophe first and then the quotes. My mail showed
this to me with straight up and down quote/apostrophe marks (i.e., not "smart"
curly quotes). Jim Asman told me his system showed him the apostrophe clearly
curling to the left and then the quotes. Either way, I have my screen
reader set to ignore most punctuation, so it was up to me to try and "see" it...
and like I say, even at 30 times magnification, the apostrophe and quotes next
to each other are almost impossible to discern. It's either apostrophe quote or
quote apostrophe, and it would be anyone's guess. Maybe I'll turn on the
smart quoting again. I forget why I turned that stupid feature off in the
first place.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2 face=Arial>I
vote with your colleague </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial>rm -f ${PFDIR}/filepro/filename/lockf*</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial>at the head of your script and you will never see this problem
again. On to more agonizing problems.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial>John</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=515560821-03022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT size=2 face=Tahoma><B>From:</B> Tyler
[mailto:tyler.style@gmail.com] <BR><B>Sent:</B> Wednesday, February 03, 2010
12:54 PM<BR><B>To:</B> john@valar.com<BR><B>Cc:</B>
filepro-list@lists.celestial.com<BR><B>Subject:</B> Re: rreport gagging on
lockfile<BR></FONT><BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=gmail_quote>On Wed, Feb 3, 2010 at 10:44 AM, John Esak <SPAN
dir=ltr><<A href="mailto:john@valar.com">john@valar.com</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>
<DIV>
<DIV dir=ltr align=left><SPAN><FONT size=2 face=Arial>Omly have a minute...
noticed this..</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT size=2 face=Arial></FONT></SPAN></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(0,0,255) 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr><FONT size=2 face=Arial></FONT>
<DIV>system "/appl/fp/rreport log_operations -fp log_it -sr 1 -r
'"{m{"'"<BR><SPAN><FONT size=2
face=Arial>
^</FONT></SPAN></DIV>
<DIV><SPAN></SPAN><SPAN><FONT size=2 face=Arial>this needs to be a < or
an & if there is a space before the
quotes.</FONT></SPAN></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE>
<DIV>No, it's just hard to see what's going on there. There isn't a
space needed there - there's a single quote in front of the double quotes
after -r and a single quote between those doublequotes at the end, for
generating a string for the command line. (eg) "-r '"{m{"'" ====> -r
'file=invhead2...etc'
<DIV></DIV><BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(0,0,255) 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV><SPAN></SPAN><SPAN></SPAN></DIV>
<DIV><SPAN><FONT size=2 face=Arial>Lastly, did you happen to get a look at
the size of the lockfile before I suggested removing it? If it was
64, then perhaps it was corrupted in some strange way. If it was the
larger new size, than this goes back to the mismatch betwee 5.6 and
previous versions... but as you said there is no 5.6 on this system in
question. For the 64 bit lockfile to be corrupted... I don't really
know what I'm suggesting. Meaning if it were corrupted in some way,
it wouldn't allow you access with anything, clerk, report, dxmaint, and so
on. It sounds like you were having trouble with just this one
routine. </FONT></SPAN></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE>
<DIV>No, I didn't see the size. My coworker says she noticed nothing odd
about it. And it was indeed with just this one routine, but that's not
surprising - it's the only processing for the file at all anywhere. <BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(0,0,255) 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV><SPAN></SPAN><SPAN><FONT size=2 face=Arial>I kind of hate just having
things fix thmeselves without ever knowing what was wrong or what fixed
it... so, if the problem rears its ugly head again, bring it up. We
know what made the problem go away in this case, that is not the same as
what "fixed" it. :-( Of course, if you really want a headache free
runtime of this routine, just put a hard-coded "rm" of the lockf* files in
the culprit directory and it seems you'll be fine. Still, a tiny
nagging would bother me forever about having to do this.
:-)</FONT></SPAN></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE>
<DIV>I agree 100% That's why I still posted even after deleting the
lockfile worked out; I'd much rather fix the actual problem than band aid and
forget it!!! My coworker wants to go the rm route, but I am trying to
beat that out of her head :) <BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(0,0,255) 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV><SPAN><FONT size=2 face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN><FONT size=2 face=Arial>John</FONT></SPAN></DIV>
<DIV><SPAN><FONT size=2 face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN><FONT size=2 face=Arial>P.S. I didn't look through the whole
launching stuff... ut it's good you got it together, maybe it will become
useful if the problem crops up
again.</FONT></SPAN><BR></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV>I'm
certain that the code has no bearing on the problem - it has to be
environmental. But it's there for those who care :)<BR><BR>Thanks for
the insights, John.<BR><BR>Tyler<BR></BLOCKQUOTE></BODY></HTML>