If you use multiple allruns directories (maybe to keep SP8
and SP9 production seperate or to keep the validation runs
apart from production runs), be careful with setting a
default ALLRUNS in your login scripts.

When a SP job is submitted, your spsub interface to the
batch should transmit all environment variables to the
batch job, including ALLRUNS. But the SP jobs will start
a new shell, so if you always set a default in your login
scripts, that default will override whatever ALLRUNS was
set for the shell calling spsub. For the Moose part of
the SP job that doesn't matter since for Moose everything
is fixed in the config files. But Job.bash checks the Moose
output with spcheck and with the wrong ALLRUNS spcheck won't
find the run. The result is that the run is stuck in a
'done' state and never marked as 'good'. Only 'good' runs
are picked up by spmerge.

The problem can be fixed by checking in your login scripts
if ALLRUNS is already set before setting it to the default
value. Something like this (for csh) :

if (! $?ALLRUNS) then
  setenv ALLRUNS /somedir/allruns
endif