PFSKIPLOCKED variable

[John Esak]

Or, I think Bruce has it almost right... you may be setting the variable
*after* you've done the lookup on that table. Be sure the PUTENV happens
*before* you do the lookup.  Otherwise, unless there is some strangeness
about lookups and locking... It think this should be possible.

John

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On
> Behalf Of Bruce Easton
> Sent: Friday, April 27, 2007 12:03 PM
> To: filepro-list at lists.celestial.com
> Subject: RE: PFSKIPLOCKED variable
>
>
> Don Coleman wrote Friday, April 27, 2007 11:16 AM:
> [..]
> > I have a *report function which updates imported records every
> 5 minutes.
> > There should be no harm in having it periodically skip a locked record
> > because it will run again shortly.
> > The manual seems to indicate the following syntax:
> >
> > Putenv "PFSKIPLOCKED","5"
> > To skip if locked after 5 seconds.
> >
> > However it is not skipping those records after 5 seconds.
> [..]
>
> Don - sounds like you might be setting the env var inside the
> program where it needs to be seen.  If this is true, try setting
> PFSKIPLOCKED prior to calling your report request - in the shell/prog
> that calls rreport (and exporting it, if necessary).
>
> Bruce
>
> Bruce Easton
> STN, Inc.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list