DataStage scheduling issues

venugopal81 · Post by **venugopal81** » Fri Oct 21, 2005 1:27 am

Hi All,

We have scheduled our datastage jobs with EVERY/DAILY option. All Jobs got hanged. But when we have schedule with TODAY option all jobs got success. This problem occurs only for BW Load Packs not for other jobs.
We have observed with Different scheduling options. But jobs are working under TODAY scheduled option. How can i resolve this issue.

Please suggest me.

Thanks&regards,
venu

ArndW · Post by **ArndW** » Fri Oct 21, 2005 1:39 am

Venu,

when you say your jobs "hang", do you mean that they start and have a status of "running" in the DataStage Director? I can see no reason why a job would behave differently because of the time it was scheduled.

On UNIX when you schedule jobs to run from the Director they will be put into the default scheduling tool's list - this would be 'cron' and 'crontabs'. If you look at the entries in there for both jobs scheduled for today and for future dates, do you see any differences?

ray.wurlod · Post by **ray.wurlod** » Fri Oct 21, 2005 2:24 am

EVERY uses cron, but TODAY uses at - maybe you don't have some required permission to use cron?

By "hang" do you mean "don't advance to a status of running" or "reach a status of running but never reach a status of finished".

ArndW · Post by **ArndW** » Fri Oct 21, 2005 2:34 am

Ray,

I didn't know that - I am assuming that you mean the Windows AT command running from the client's system? That would also explain the different behaviour in this case.

ray.wurlod · Post by **ray.wurlod** » Fri Oct 21, 2005 3:22 am

No, I mean the UNIX at command. Where use of cron is governed by the cron.allow file, the at command is governed by the at.allow file.

Not all variants of UNIX support an at command but most seem to.

chulett · Post by **chulett** » Fri Oct 21, 2005 7:22 am

But if the scheduling user is not in the appropriate 'allow' file then the scheduling attempt will fail, not the running of same. Need a better explanation of what 'hang' means.

venugopal81 · Post by **venugopal81** » Wed Oct 26, 2005 8:00 am

Hi ray,

The issue seems to be permissions to cron, the datastageadmin id which owns the rfc server process doesn't have permission to the Unix Scheduler.

EVERY uses cron , but TODAY uses at - maybe you don't have some required permission to use cron ?

Now this problem solved.

Thanks Arndw, Ray and chulett .

DSXchange

DataStage scheduling issues

DataStage scheduling issues

Scheduling issue solved