Hi All,
I have one shell script through which I am executing some datastage and quality jobs(these are ETL Jobs), when I run the script through unix prompt then the script is executing fine and getting desired results.
But when I schedule the same script in crontab then in the middle of the script it is exiting with exit status code of 134.

Could any one guide me how to overcome this issue. Thanks in advance

Thanks & Regards
Vijay Kumar

Not too much to go on here... But if you don't have an explicit exit statement to set the return code, most shells effectively do a:
return $?
which is to say that the return the exit code of the last command that they ran. So your script probably ran one or more programs. And the last one exited with 134. So you need to look at the docs for that program.

Another thing to look at is your environment. cron doesn't neccessarily pick up some environmental parameters set by your interactive shell. If, when you log on interactively, you have, say a bunch of Oracle parameters set by .profile, you aren't neccessarily going to have those when cron launches your script. This link has covered this.

Thomas

Thankyou verymuch

I have edited my .profile to export the environment variable settings that my script uses and it is working.

Thanks & Regards
Vijay Kumar