Re: Pathname for SPERFORM

In article <dennisp.777654982@infmx> dennisp@informix.com (Dennis Pimple) writes: > >Just to clarify a bit: sperform and sacego will look in current >directory first, then in each directory of DBPATH for the appropriate >.frm/.arc file. I just verified that this is indeed the case under ISQL 4.11.UC1 and SE 5.01.UC1. I'm usually pretty good about reading all documentation, but I confess that I missed this point. I guess I assumed that since the environment variable was named *PATH, it would act like the shell's PATH. What's the rationale behind initially ignoring DBPATH? Am I correct in assuming that if I inadvertently cd to the parent directory of my production database, I will be working against it even though DBPATH contains only the absolute pathname(s) of my test directory structure? I suggest that a better approach would be to use the current directory if DBPATH is not set, or use *only* DBPATH exactly as set if it is non-null. Is anyone making specific use of the fact that the current directory is always checked regardless of DBPATH's value? Thanks, Walt. -- Walt Hultgren Internet: walt@rmy.emory.edu (IP 128.140.8.1) Emory University UUCP: {...,gatech,rutgers,uunet}!emory!rmy!walt 954 Gatewood Road, NE BITNET: walt@EMORY Atlanta, GA 30329 USA Voice: +1 404 727 0648