dsjob

dannywcw · Post by **dannywcw** » Thu Jul 12, 2007 12:01 am

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

kumar_s · Post by **kumar_s** » Thu Jul 12, 2007 12:08 am

Where are you running this command from? And what is the content of the Script?
What is "12 14 * * * " used for?

dannywcw · Post by **dannywcw** » Thu Jul 12, 2007 12:13 am

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

kumar_s · Post by **kumar_s** » Thu Jul 12, 2007 12:26 am

Alright, does your sript calls the job, if it is called from command line. (Not thought Cron). Doesn't it require any input argument as parameter during the call? Do you get any error message?

dannywcw · Post by **dannywcw** » Thu Jul 12, 2007 12:49 am

Yes this command will call logica_inp_inss job.
Parameter is included in the command.
No error message.

kumar_s · Post by **kumar_s** » Thu Jul 12, 2007 12:53 am

Check whether your user id has access and an entry to cron.alow file.
Also try to schedule the same job for Today at some futher time.

chulett · Post by **chulett** » Thu Jul 12, 2007 7:16 am

kumar_s wrote:Check whether your user id has access and an entry to cron.alow file.

It wouldn't already be in cron if that wasn't setup already, Kumar.

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.

kumar_s · Post by **kumar_s** » Thu Jul 12, 2007 11:20 pm

chulett wrote: It wouldn't already be in cron if that wasn't setup already, Kumar.

Correct point, though.
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.