- Autosys gives u various options, like JOB_ON_ICE, JOB_ON_HOLD
- Scheduling is pretty simple, if u hav a job that u want to schedule every one hr. Then through Datastage you have to schedule it 24 times, which would create 24 processes(Distinct PID). whereas in autosys you dont have to take so much pain.
- if u want to run a job on first monday of every month, u just have to set a Calender in autosys, in datastage couldn’t think of.
- if u want to run a job on first business day(a business day for a client may vary) of every month, u just have to set a Calender in autosys, in datastage couldn’t think of.
- In short I would say, it would give various scheduling options, with less effort. Reusability and maintenance is also a factor.
how will u connect datastage job with autosys
Irrespective of the scheduler you use (AutoSys, SeeBeyond, ControlM, at, cron, to name a few) use the command line interface dsjob to specify what you want DataStage to do.
you will have to write a Wrapper shell scripts, in which you need use Datastage CLI(Command level interface). After creation of the wrapper shell script, you need to just execute that shell script through autosys.
Other Scheduler posts