CRON doesn't execute your .profile before executing the command.
If your command needs specific environment initialisation (variables, path...) it may work incorrectly.
In that case try that :

36 10 * * * . ~/.profile ; /bscsprod/bscs/prod/WORK/XREF/teh -t -f MPPROFIL >> /bscsprod/bscs/prod/WORK/XREF/tehcron.log 2>&1

yea i agree with aigles since if the script depend on environment variable it wont work , so using the above will work

Thanks guys! My entry is now working!

1 more question, what does . ~/.profile ; and 2>&1 do?

Thanks!

. ~/.profile ;
. Execute file in current environment
~ Home directory of current user.
; command separator

2>&1
File descriptor 2 (stderr) is to be opened for writing as a duplicate of file descriptor 1 (stdout)
The stderr displays are written in the same file as stdout.


Jean-Pierre.

Adding . $HOME/.profile entry to the cron is not a fair idea
Instead provide the script to be executed via cron the needed environment variables.

With inclusion of .$HOME/.profile all that is not needed by the script is set to the environment.

THANKS!