I'm having a weird behavior from Ocean. I do have a small script (250 lines) that I run in batch from a Shell script with an output log, invoking the following command :
ocean < my_script.ocn > ./my_log.log
In my script, I have several printf that informs me of the script actions.
Fact is, using this shell command to invoke OCEAN gives me no error and none of my printf in the log file (despite I can see all the OCEAN loading etc. ) and no output file for results.
If I comment, let's say, half of my script, everything is working fine.
At the beginning, I just thought my script was failing at some point... but then I loaded my script in the OCEAN environment, and it works !
Also, Andrew post on GoogleGroup that the following command allows to invoke Ocean from Unix shell
ocean -restore oceanScript.ocn
It opens OCEAN in the shell and load the script automatically like in an interactive mode. And this works !
So, why my shell script invoking OCEAN with the following command :
just fails at some point without even the first printf in the log which is right after openResults() and selectResults() ?
(like if the script itself was too big to be run ?!? )
Program: awd.exe version 5.1.0
Sub version: sub-version 5.10.41_USR5.90.69 (32-bit addresses)
Thanks for your help :)
It's hard to tell - because the output would be buffered, the log file may not necessarily reflect the point that it really got up to (you could just run "ocean < my_script.ocn" without redirecting the output to see if that helps.
However, I'd always recommend using -restore over redirecting the standard input to the "ocean" command.
In reply to Andrew Beckett:
Thanks a lot for your quick response.
Well, I now use the "ocean -restore" command with an "exit" statement at the end of my Ocean script and it works like a charm with the rest of the shell script !