Very Computer

Hello, all...

I'm trying to develop and debug a subset control program for use with
the Tru64 'setld' installation utility.  The problem is, the large
"case" statement within the SCP doesn't get handled correctly.  The
actual text of the error when installing the subset is:

"/var/tmp/stltmp23623/STMAPI620.scp: syntax error at line 393: `end of
file' unexpected"

By using "set -x" and "set -v" commands within the SCP, I can see that
setld is actually reading until the very end of the SCP file, even past
the ";;" and "esac" lines.  I suppose there is a syntax error or script
formatting error somewhere, but the shell isn't too forgiving or
helpful.

Are there any special handling or formatting considerations of which I
should be aware? I've reviewed several of the Tru64 system SCP scripts,
but haven't spotted any glaring errors, by comparison.  OTOH, I've seen
extra blank lines and ";;" lines at the bottom of some system scripts.

Thanks in advance for any assistance,

Keith Benoit
C*te, NC

Quote:>"/var/tmp/stltmp23623/STMAPI620.scp: syntax error at line 393: `end of
>file' unexpected"

This is typically what happens when a shell script contains a construct
that is opened but not closed (eg, a missing quotation mark, an if
statement without a matching "fi", a for loop or while loop without a
matching "done", etc.).

That doesn't mean it will be easy to find, but that's what I'd suggest
looking for.

     - Steven
________________________________________________________________________
Steven Winikoff                |
Concordia University           |
Montreal, QC, Canada           |   There's an exception to every rule,

http://alcor.concordia.ca/~smw |

Steven,

Thanks for your suggestion. I had already carefully (no, really! :-)
inspected my script for mismatched quotes, if/fi do/done case/esac
pairs, missing syntax, etc.  My request for help was to see if anyone
knew of problems peculiar (and most likely undocumented) to the 'setld'
installation utility.

As it turns out, the problem was solved when I cut out each section of
the case statement to a separate file, and then copied/pasted the parts
back into the main script.  Apparently, there was an escape sequence or
control character embedded in the body of the script, somewhere.  It's
running fine, now.

Thanks again,

Keith