Lookup across drives

[John Esak]

I hope your in depth explanation helps, too.  When I tried to clarify I
muddied up the whole point. I meant that there could not be two "differeing"
files with the same name in different PFDIRS. I am well aware that parts of
the filePro file structure can be placed in differing PFDIRS. I only wanted
to alert anyone to the idea that they can not have different PFDIRS with
files that have the same name but contain differing data. Ain't going to
happen. I re-read the original post, and it is clear he just wanted to do
alookup across PFDIRS, which of course, is possible. In trying to explain
more than what he asked, I complicated things. :-( 

John


> -----Original Message-----
> From: Nancy Palmquist [mailto:nlp at vss3.com]
> Sent: Wednesday, October 10, 2007 1:26 PM
> To: john at valar.com
> Cc: Filepro-List at Lists. Celestial. Com
> Subject: Re: Lookup across drives
> 
> John Esak wrote:
> >> Robert,
> >> I don't think that is correct. PFDSK can not be set in a way that will
> let
> >> you do lookups across differeing PFDIRS.
> >>
> >> Too bad...
> >>
> >> John
> >
> > Let me clarify that... I didn't mean that PFDSK can't be set to multiple
> > drives. Yes, you can set PFDSK to multiple drives, but the PFDIR and
> PFDATA
> > variables would have to match exactly and there would have to be no
> > duplications of filePro filenames to do this successfully.
> >
> > John
> 
> 
> John,
> 
> I hate to say this but this is a bit incorrect.  Filenames can be
> duplicated if you need to have some stuff here and some stuff there.
> 
> If I set up like this:
> 
> c:\filepro\customers\map
> c:\filepro\customers\screen.0
> c:\filerpo\customers\input.prc
> 
> 
> M:\filepro\customers\key
> M:\filepro\customers\data
> M:\filepro\customers\index.A
> 
> 
> with PFDSK=CM
> PFDATA=C:
> PFPROG=c:\fp
> 
> This would work great.  I have tested this with Unix and Windows and the
> primary location will require the map.
> 
> If the M: drive is also seen by UNIX with samba or something similar,
> the Unix version of file would have its own folder with the map and
> processes and would have the key stuff on its second location.
> 
> /appl/filepro/customers/map
> /appl/filepro/customers/screen.0
> /appl/filepro/customers/prc.input
> 
> 
> /u/appl/filepro/customers/key
> /u/appl/filepro/customers/data
> /u/appl/filepro/customers/index.A
> 
> PFDSK=/;/u
> PFDATA=/appl
> 
> If the M: the windows computer sees is the /u/appl folder on the unix
> system this will work and both systems will lock records correctly.
> 
> Both systems will update the files and indexes correctly.
> 
> I recall that the lockfile was always placed on the first drive so they
> would not be able to see each others files for that.  A small issues.
> 
> I also do not remember what happened when I rebuilt the indexes.  I
> think it put them back on the C: or the /appl mount, depending on which
> system did it, but I do not recall for certain.  I do KNOW that if it is
> put on the shared drive it will update correctly.
> 
> This requires a filesystem that works with samba or facetwin or
> something similar.
> 
> I have this type of system in place to allow 3 unix servers to share a
> few setup files.  Also, these 3 unix servers can see data that can also
> be seen from a windows server behind a firewall.  I throw data into a
> file and the windows side can get it out of the file.
> 
> Hope this helps.
> 
> Nancy
> 
> 
> 
> 
> --
> Nancy Palmquist 		MOS & filePro Training Available
> Virtual Software Systems	Web Based Training and Consulting
> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com