[daip] Re: UPDUPDATE problem for ARCH=SUL

[Eric Greisen]

Andrzej Marecki writes:
 > Dear Eric,
 > 
 > During the last run of MNJ at my site, when a "jumbo" patch introducing
 > three new header parameters to tell the type of imaging was applied,
 > everything went fine except the following message from cron:
 > 
 > ./UPDUPDATE: [[: not found
 > using default settings with ARCH =  SUL
 > 
 > Is that a serious problem?
 > 
 > Cheers, Andrzej

Curious - our SUL MNJ issued this message

UPDUPDATE - there are SYSLOCAL changes to process
***** Do not over-write FDEFAULT.SH ******
***** You might want to compare with SYSSUL ******

Yours seems to have deleted $SYSLOCAL/FDEFAULT.SH and left you with
only the unusable one in $SYSUNIX.  This is a serious error.

Copy $SYSSUL/FDEFAULT.SH to $SYSLOCAL and make sure it reflects what
you actually want.  Then go to $TST/SUL/UPDATE and edit all LAST*DAT
files to have a date of a few days ago.  Then run the MNJ by hand.

I have no idea what went wrong on your MNJ that worked fine on ours.
The error message seems to appear before any other message and so
should have occurred before the rm command if it was wrongly taking
that branch in the if statement.  Maybe our systems person will have
an idea.  "[[" is part of the if clause and is required in the shell,
maybe it does not work on your system - is yours an very old or very
new one?

Thanks for reporting this.

Eric Greisen