Dear Team,

I am new to unix and have written some script which is not formatted because i want a free download tool to format the below code by window xp OS to save time

Problem is that if i execute the script manually it works but when i ccron it it dont work with expected results. My cron is working because i get mail.
---------------------
crontab -l
* * * * * /bdrhomtt01/projets/BDR/bdrhom02/bin/mah_trf.ksh
---------------------
Script:
more mah_trf.ksh

Code:

cd /bdrhomtt01/projets/BDR/bdrhom02/log
for i in `ls /bdrhomtt01/projets/BDR/bdrhom02/log/test* | xargs -n1 basename`;
do
if [[ $i != "test1.txt" ]]
then
echo $i;
ftp -niv PARNAS04 << EOF
user TRANSBDR xxxxxx
cd BDRDoc/Extractions_Output_Files
put $i
bye
EOF
mv $i /bdrhomtt01/projets/BDR/bdrhom02/RC/
else
echo "No new files found to tarnsfer";
fi
done
cd /bdrhomtt01/projets/BDR/bdrhom02/bin/
cat m.txt | mailx -s "Files moved to PARNA04" mahendra.singh@gmail.com

You said the results aren't expected, but what are they? What is it doing?

Remember the cron has a very restricted PATH. Commands like mv, cd, ls, etc. should all work fine, but ftp might not, and your "mailx" routine might not. It's good practice to hardcode the full path to these commands if the script will be called from cron.

I am trying to compare a hardcoded filename with similar filenames in log dir. if it dont match than transfer to FTP server else say no files found

I know what the script is supposed to do, I'm asking what it's actually doing when you run it in the cron, since you say it doesn't give you your expected results. What DOES it give you? What does it do? Where does it fail? What is the output? Do you get any emails from the cron with error information?

I get a mail with message written in m.txt

but when i go and check the files in the log dir. still exists which shouldn't be the case and also it has not transferred the files to PARNAS04 server

Generally a script that will run OK manually but not from cron is due to environment settings. Something that is set in your interactive shell is not being set by cron. It could be as simple as a difference in the PATH variable (it is very generic in cron). Normally any output that is not redirected from a cron jobs is sent to the owner of the crontab. Check your local system email for any messages. You'll probably find many unread messages.

Try redirecting STDOUT and STDERR to a file to see if there are any messages. Do this on your crontab line:

(Set the filename and path as you want.)

You should also explisitly set the command interpreter and turn on command expansion by entering this on the first line of your script:

This is the same as invoking the script as ksh -x script.ksh. The -x turns on command expansion which displays the command with all variables expanded to their set value. This ensures your script is being called by the intended interpreter (ksh in this case). The default shell on most most modern Linux systems I've used is bash. There are differences between bash and ksh executuon. Remove the -x after you get it working to quiet the output.

If it is still not working put an "env" command (without quotes) near the top of the script (after the shell line above but before your cd command. Then compare the output from env of a manual job ans a cron job.

Dear finally the issue got resolved bu putting #!/bin/ksh -x

Thank you all Guys fro your prompt response