ignoring a and b drives

[Kenneth Brody]

"Jay R. Ashworth" wrote:
[...]
> > > > And your question forgets that, while PFDSK is a list, PFDATA and PFDIR
> > > > are not.
> > >
> > > Doesn't matter.  If PFDSK is a list, then the programs either iteratte
> > > over all elements of it, or they don't.  If they do, and your replies
> > > imply that they do, then my question is valid, and as yet unanswered.
> >
> > Which part of your question do you feel remains unanswered?
> 
> Well, "Only if they are both in the "/u1:/u2/appl/filepro" directory."
> certainly doesn't answer anything.  ;-)

Sure it does -- it answers the question as you asked it.

Your question was (paraphrasing) "would filePro see both files if PFDATA
is '/u1:/u2'" and the answer is "filePro uses $PFDATA$PFDIR/filepro, so
it would see both files if both were in the '/u1:/u2/appl/filepro'
directory (assuming that PFDIR is the typical '/appl' value)".

> If PFDATA on a Unix machine contains /u1:/u2, and /u1/$PFDIR/filepro
> and /u2/$PFDIR/filepro both contain fully populated filePro database
> directories with disjoint names, will the file list presented by
> dclerk, et al, contain all the files names from both directories?

Again, PFDATA is not a list.  (PFDSK is a list.)  Since everything
except key, data, and index files must be in $PFDATA$PFDIR/filepro,
and assuming you really mean that PFDSK is set to "/u1:/u2", the
setting of PFDSK is irrelevent to where filePro looks for the main
file directories.

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+