The reason for
SCRIPTS=/ontw/bin/app: is not an identifier is that (as others said) you are executing the script under the Bourne shell. You might say, "what about the #!/bin/ksh?", well that is ignored as a comment with the "dot" command. You might also reasonably say, "why is the export failing, when that is a POSIX complient command?". Unfortunately many commercial Bourne shells are still not POSIX complient.
Although even if it did not give the error you still cannot execute the korn shell language from the Perl language.
I suggest you do the following: have a shell script wrapper which executes the required preamble, and then calls the "real" script. The name of that script can be passed as a command-line argument from perl to the wrapper.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.