Hi all,
Can anyone tell me why is my command is not running the job? please help
12 14 * * * su - dsadmin -c "./dsprod01/LOGICA_TRANS/daily/script.sh" >> /dsprod01/LOGICA_TRANS/daily/aaa.log
dsjob
Moderators: chulett, rschirm, roy
this is a cron command. the 12 14 * * * is the time
the script is used to run datastage job
cron command is
12 14 * * * su - dsadmin -c "./dsprod01/LOGICA_TRANS/daily/script.sh" >> /dsprod01/LOGICA_TRANS/daily/aaa.log
Content of the script is
su - dsadm -c "/ardent/Ascential/DataStage/DSEngine/bin/dsjob -run -mode NORMAL -param FILE_NAME=inp1-${_year}-${_month}-${newday}.unl -param OUTPUT_FILE_NAME=${_year}-${_month}-${newday}-inp.unl LOGICA_TRANS3 logica_inp_inss" >> /dsprod01/LOGICA_TRANS/daily/crn_inp.log
the script is used to run datastage job
cron command is
12 14 * * * su - dsadmin -c "./dsprod01/LOGICA_TRANS/daily/script.sh" >> /dsprod01/LOGICA_TRANS/daily/aaa.log
Content of the script is
su - dsadm -c "/ardent/Ascential/DataStage/DSEngine/bin/dsjob -run -mode NORMAL -param FILE_NAME=inp1-${_year}-${_month}-${newday}.unl -param OUTPUT_FILE_NAME=${_year}-${_month}-${newday}-inp.unl LOGICA_TRANS3 logica_inp_inss" >> /dsprod01/LOGICA_TRANS/daily/crn_inp.log
dwcw
It wouldn't already be in cron if that wasn't setup already, Kumar.kumar_s wrote:Check whether your user id has access and an entry to cron.alow file.
So Danny... you need to tell us - is cron launching the script and the job isn't starting? Or is cron not even launching the script? If you've got a cron problem, work with your SA to resolve it. If the script is being launched, what shows in the redirected log file or the job's log? If nothing, I'd suggest you send everything to your 'aaa.log', specifically including 'standard error' there as well.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Correct point, though.chulett wrote: It wouldn't already be in cron if that wasn't setup already, Kumar.
Some time back I faced similar problem. It would have been scheduled and would able to find the entry in cron as well. But the job wouldn't get triggered. It was some permission related issue, but can't recall what exactly was the change made to over come that.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'