Hi Gurus,
we want to schedule a job to run every 2 hours during business hours over the weekdays using datastage scheduler.I know we can't run using datastage scheduler.
we don't have third party tools like autosys here.
Is there any alternatives......
Thanks in advance.
Reddy
Datastage scheduler for business week days
Moderators: chulett, rschirm, roy
There is no DataStage scheduler, it uses the default Windows scheduler (AT). I don't know why you can't run the DataStage scheduler, unless you haven't installed it on your server. The free UNIX utilities such as mks-toolkit or the Microsoft one (I can't recall the name) have versions of the UNIX cron which will let you do more complicated scheduling.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
You can schedule the job to run Mondays through Fridays at the specified intervals; but the AT scheduler doesn't know anything about the calendar and it's relation to holidays. If you need a job to specifically not run on weekdays that are holidays in the place where the server resides you will need to put in some more logic or script, which is why I suggested you look into the UNIX cron; which does offer support for holidays in the crontab settings.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Alternatively, you could write a job sequencer which could be scheduled to run every 2 hours. The sequencer would first call a routine which would check the day and, if required, read a file containing holidays and do whatever other checks you require. The return value of the routine could then be used to trigger the actual job.
Jim Paradies
Jim,
that's a good approach; since there are any number of UNIX utilities available to return you the holiday status and it's easy to parse the result of an external command from a DS Basic program. Keeps the scheduler simple and the overhead of calling up a sequencer or job is not that high if it immediately decides to stop.
that's a good approach; since there are any number of UNIX utilities available to return you the holiday status and it's easy to parse the result of an external command from a DS Basic program. Keeps the scheduler simple and the overhead of calling up a sequencer or job is not that high if it immediately decides to stop.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Ultimately the best solution for this kind of problem is table-driven, so that you can take into account public and business holidays - Mondays through Fridays that are not business days.
You can readily implement this via a job sequence that is scheduled to run every day, prior to the first required start time. This can determine whether today is a business day and, only if so, initiate a StartLoop .. EndLoop to run your job at the requisite interval.
Make sure your job finishes well under the interval, or include check whether the job status is currently "running" before attempting to start it.
StartLoop and EndLoop activities only became available in version 7.5.
You can readily implement this via a job sequence that is scheduled to run every day, prior to the first required start time. This can determine whether today is a business day and, only if so, initiate a StartLoop .. EndLoop to run your job at the requisite interval.
Make sure your job finishes well under the interval, or include check whether the job status is currently "running" before attempting to start it.
StartLoop and EndLoop activities only became available in version 7.5.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.