...
The caldb problem above is actually more pervasive. commonUtilities routines need to be enhanced for support of installations with a supersede directory. Proposed actions: Rework
commonUtilities with as little impact on clients as possible. Unfortunately it's likely that client code will also need to be changed if it is to work properly in all situationsResolution: facilities-02-18-13 has a smarter commonUtilities which handles almost everything properly in case there is a supersede directory. The one exception is getPfilesPath. The interface needs to be changed so it can return a list. But it looks like no one actually uses this routine so it hardly matters how it's handled.
Wrong python in path
At run time python was resolving to default installation rather than "our" python. Jim tracked this down to unfriendly behavior of one of the set-up files asp_setup.sh calls: it resets PATH.
Resolution: Split asp_setup.sh into two pieces, one run before invoking _setup.sh and the other after. Committed to CVSTagged in SConsFiles-00-02-01.
Over-resolution of nfs path
...
Resolution: Use utility supplied by Jim to translate back to /nfs... path. Committed to CVS.Tagged in SConsFiles-00-02-01
PFILES behavior
ASP jobs may run without an afs token in which case they can't write to $HOME. Old PFILES-handling code would make a pfiles subdirectory in $HOME if it didn't already exist. It's bad form for programs run in batch to access $HOME anyway, so Jim proposed eliminating all PFILES handling in _setup.sh for batch processes.
Resolution: Compromised by getting rid of references to $HOME for batch jobs. The PFILES path in this case will include pfiles directory of base installation, pfiles directory of supersede area (if there is one), prepended with process's original value of PFILES (if any). Soon to be committed to CVSTagged in SConsFiles-00-02-01, except for one last fix for .csh only which is committed but not yet tagged.