leveraging PFDSK

[John Esak]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of Jeremy
> Anderson
> Sent: Tuesday, September 07, 2004 4:45 PM
> To: filePro mailing list
> Subject: leveraging PFDSK
>
>
> On my filepro 4.5 system, several files are broken across partitions.
> That is to say, /appl/filepro/SpecInv holds all the processing tables,
> and the map, and everything EXCEPT the actual key file.
> /appl2/filepro/SpecInv holds the key file.
>
> I'm trying to duplicate this using filepro 5.0.13 on linux, where my
> directory structure is slightly different.
> On that machine, I have two directories:  /appl/test and /appl/test2.
> Within each is a filepro directory, mirrored from the 4.5 machine's
> /appl and /appl2 .
>
> I am trying to repair a script which automatically rebuilds demand
> indexes.  At some point in the past, it worked.  Before I was employed
> here, it stopped working.
>
> This is the script:
> #!/bin/bash
> export TERM=vt100
> /appl/fp/dxmaint serArch -O1 -S index1 -R -E
> /appl/fp/dxmaint acctsrec -O0 -S index0 -R -E
> /appl/fp/dxmaint SpecInv -O1 -S index1 -R -E
>
> I need the system to search through both /appl/test/filepro/serArch and
> /appl/test2/filepro/serArch for the map and keyfile.
> On the old system, this was apparently accomplished through the PFDSK
> environment variable.

No, it is accomplished through a more internal search mechanism which uses
the mount table and similar basic paths. Note your first two paths on the
working machine and how they are different from the ones you want to use.
They are:

   /appl/....
   /appl2/....

By changing to the way you have it you lose the mechnism filePro is actually
using which is to search the mount table, and run any filePro files found in
absolutely similar paths starting *after* the original mount name... in your
case /appl and /appl2 both have filepro/filename/... after them and that is
why they are found.
>
> In my script, I have tried setting PFDSK to be "/appl/test:/appl/test2",
> but this does not work in the way which I expected.
> Is what I'm trying to do possible?
> If so, what is the best way to go about what I'm trying to do?

The PFDSK variable really means what it says... DSK or DISK... or volume...
or mounted filesytem... like D:, E:, F: and /appl, /u/appl, /hd2, etc.


I'm not sure what you want to do is possible. I think not. Maybe others can
find a way...

>
> Eventually, I plan to archive data out of some of the files, and
> re-merge the portions of the file, but this (like everything else) is on
> the back burner.
>

	I think you can still do this sort of thing without having to split up
everything so much. Is this a very crowded (not much disk space)system??



> I appreciate any help you can offer.
>
> Jeremy
>
> --
> Jeremy Anderson			      jeremy (at) plunketts.net
> IT Manager, Plunkett's Pest Control   Author, Multitool Linux
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list