leveraging PFDSK

Bob Stockler bob at trebor.iglou.com
Tue Sep 7 17:16:16 PDT 2004


On Tue, Sep 07, 2004 at 03:44:56PM -0500, Jeremy Anderson wrote:
| 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.
| 
| 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?
| 
| 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.

Ignoring what you've said, this is how I believe PFDATA, 
PFDIR, and - especially - PFDSK, work . . .

You want to have:

  1 - PFDATA and PFDIR set to a system-wide consistent value.

  2 - PFDSK set to point to both of the filesystems.

PFDSK is meant to hold the mount-points of the filesystems you
are mounting and using.

PFDATA and PFDIR should be the same system wide.

Example:

   I have PFDATA=/u and PFDIR=/appl

   I have PFDSK=/u:/u3

I have filePro Programs (map, processing tables, selection sets,
screens, output formats, etc.) in /u/appl/filepro and other stuff
(key, data, and indexes) indiscrimately located in either of
/u/appl/filepro or /u3/appl/filepro, and it works.

I _think_ filePro looks in $PFDATA$PFDIR/filepro for filePro Files'
major constituents, but then looks in other directories pointed to
by PFDSK - substituting elements of it for $PFDATA - to find other
parts of the whole scheme.

Bob [1]

[1] - Who split things up this way when on filePro Plus 1.2 on
      Tandy 6000 Xenix, when putting stuff on different 80 Mb
      hard disks speeded things up significantly (as I recall
      I then had maps, programs, etc., on one filesystem, key
      files on another, and indexes on a third).  If I'd used
      my 4th hard disk to split up the automatic indexes it
      might have made it even swifter, but I was satisfied and
      quit there.

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).


More information about the Filepro-list mailing list