rreport gagging on lockfile

[Richard Kreiss]

One thought, is it possible that for some reason *report is hitting the
record you are standing on?

 

This is like trying to run an output using a system call from @key on the
record you are looking at.  You can't do this as @key locks the record and
even with -u as part of the system command, a locked messages occurs.

 

 

Richard Kreiss
GCC Consulting

rkreiss at gccconsulting.net
  

 

 

 

From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
Behalf Of John Esak
Sent: Wednesday, February 03, 2010 9:08 PM
To: 'Tyler'
Cc: filepro-list at lists.celestial.com
Subject: RE: rreport gagging on lockfile

 

Just a stupid question, why is /hdi repeated in the error message... Is
there really an /hd1 under a root /hd1?

 

John

 

  _____  

From: Tyler [mailto:tyler.style at gmail.com] 
Sent: Wednesday, February 03, 2010 6:27 PM
To: john at valar.com
Cc: filepro-list at lists.celestial.com
Subject: Re: rreport gagging on lockfile

Well, spoke too soon.  The problem recurred just now.  Here is the error
message:



*** A filePro Error Has Occurred ***

On File: /hd1/hd1/appl/filepro/log_operations/lockfile

Request Output with Processing Function Running On This File

File not available.
Somebody else is modifying the file;  try again later.



Deleting the lockfile allowed things to go forward smoothly.  Does this
provide anyone with any fresh insights?

Tyler

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20100203/8e3e22a7/attachment.html