Record locking

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Tuesday, May 03, 2011 5:05 PM
> To: Richard Kreiss
> Cc: Filepro 2 List
> Subject: Re: Record locking
> 
> On 5/3/2011 4:45 PM, Richard Kreiss wrote:
> > I have an output process that batch processes credit card
> > transactions.  The process posts back into the current record the
> > resulting reply after the transaction has been processed.
> >
> > The output is run with the -u option.  Could running a report on the
> > same set of records at the same time create a problem?  The report is
> > strictly an output.
> 
> Whether or not running two concurrent reports on the same records at the
> same time will cause problems, we have no way of knowing, because we
> have no idea what your processing does.

Process 1 is a credit card approval process creating an xml file,
transmitting the file, and then processing the return xml and creating a
detail record in another file.

The report process runs against the same records selected above and prints
out a list of unprocessed transactions for the date selected.  This is just
a printed report which does not manipulate anything. There is no processing
table associated with this report.

Richard


> 
> However, I can tell you that the "-u" flag has zero effect on record
locking.
> 
> --
> Kenneth Brody