Scheduled job is not running on time.but it is running when executing same command manually.
25 10 * * * /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Manually executing the same
Ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Followed steps
Crontab -e
Added the job to cron tab.
You should consider running your working "manual" command the same in cron.
As a quick cut-and-paste example from your post:
25 10 * * * /bin/ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Please modify for your environment.
But other jobs are running with same command I would like to know why my job is not running.
Other job.
10 8 * * * /code/bin/DAILY_STATS.ksh 1 >/dev/null 2 >&1
I am not using any parameter in my .ksh file.
You would need to provide us copies of all scripts, user ids, file permissions, etc for an answer.
You are asking us to "read the mind" of your computer, which is simply an exercise in playing a guessing game.
If you really want an answer, you must profile details (all details).
cron has minimal environment.
You can simulate it on the command line:
/usr/bin/env -i USER=$USER HOME=$HOME PATH=/bin:/usr/bin /code/bin/ACCOUNT.ksh
env -i clears the environment, then USER and HOME are set from the current env, and PATH is set to the default, then the command is run.
If you do not use parameters 1 and 2 then you should use 1>/dev/null and 2>&1 (no spaces!) to supress eventual output.
But not for the test on the command line - here you want to see something!