This is generally good and allow to assure that all workload that is in the plan is actually run and not deleted just because the day has gone or a JnextPlan -for 0000 has been run by an admin.
The drawback of this behavior is that if end users are not really interested about that workload, they may leave in the plan forever the jobs that has ended in error, causing the Symphony and the Pre-Production plan (LTP) to grow without control, and then impacting the overall performances.
So admins have to cleanup the plan for jobs that are not really required, starting with IBM Workload Scheduler 9.3 there is a new option that can make this cleanup easier.
Of course, in any release, it's possible to define an until on every job stream to assure that they are removed from the plan after some days, but that requires to set each job stream individually, without a way to enforce it.
Most of the admins are periodically monitoring the First Not Completed Job Stream Instance running planman showinfo. This helps to detect that some garbage has been left in the plan before it's too late, but still require a manual intervention.
Starting with IWS 9.3 there is a simple new option that can help a lot admins in this work. This option is called untilDays and is available in optman and by default it's disabled. This option can be set to a number of days that is used to calculate a default until time for every job stream added to the plan. Job Stream that already using an until time are not affected by this option, while the other ones will get an until set automatically when the job stream is planned or submitted, the until time is calculated as untilDays days after the scheduled time of the job stream with onuntil set to SUPPRESS.
E.g. If untilDays is set to 10 days, if a job stream is not completed within 10 days from its scheduled time, it's automatically stopped and removed from the plan at the next FINAL.
Specific users that have the need to run a job stream longer than the untilDays value, can simply explicitly set an until for their job stream and a choose the number of days they need.
If you like this article and you find it useful, please share it on social media so other people may take advantage of it.
Wow...its really great information with specifics and laymen terms...Good One and keep it up!
ReplyDeleteThanks for the post and all the articles. This blog help me a lot to understand TWS.
ReplyDeleteGreat article!
ReplyDeleteCool feature.
ReplyDeleteHi Franco!
ReplyDeleteI have a job defined in schedule with opens dependency running every one Hour, so if I place the file after 3hours all the previous job instances too are running, is there any other way to make the job run only once when I place the file after 3hours...