TWS / OPC



Ask queries about other IBM Tools like Tivoli, COBTEST, Fault Analyzer, z/OS File Manager, Workload Simulator, APA, SCLM, Merge & Migration Tools etc...

TWS / OPC

Postby bazzigar » Wed Mar 14, 2012 8:30 pm

Hello ,

In OPC / TWS How to add cyclic job to the current plan?
Eg: A job which run every 5 minutes.

Thanks,
bazzigar
 
Posts: 29
Joined: Sat Feb 11, 2012 7:20 am
Has thanked: 0 time
Been thanked: 0 time

Re: TWS / OPC

 

Re: TWS / OPC

Postby dick scherrer » Sun Mar 18, 2012 9:25 am

Hello,

Suggest you ask your scheduling people, look in the documentation, or call the vendor support.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: TWS / OPC

Postby NicC » Mon Mar 19, 2012 6:58 pm

I do believe OPC (now called TWS) is an IBM tool and not a 3rd party tool.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: TWS / OPC

Postby rj86 » Mon Sep 10, 2012 12:12 pm

@bazzigar :

This can be achieved in many ways. I will explain you a general simplified approach as mentioned below :

Since your requirement is with a gap of 5 mins only, first find out how much time the individual job actually takes to complete. If it takes less than or equal to 5 mins only, then you can schedule the jobs as given below (note that here we are ignoring the stringent 5-minute rule. Each job will start as soon as its predecessor completes) :
Create an application. For eg, here let EQU10BXP be the application.
In the application, create a job (lets say EQU10B01) with the required JCL for the job.
If you require the same job to run for say some 15 times, copy the same JCL with different job names like below :
App : EQU10B01P
Jobs :
EQU10B01
EQU10B02 -> predecessor EQU10B01
EQU10B03 -> predecessor EQU10B02
EQU10B04 -> predecessor EQU10B03
...
..
EQU10B15 -> predecessor EQU10B14

Here, make sure you set the previous job as the predecessor of the next job. The first job will be triggered when the application is triggered. The application can either be Time-Triggered, Event-Triggered or triggered as being a successor of some other application.

If you need to enforce the 5-minute timing stringently, then you need to add an additional time-job as the predecessor of each job. Lets say that we need to start the initial run at 9 AM.

App : EQU10B01P ->predecessor U0900B01P
Jobs :
EQU10B01
EQU10B02 -> predecessor EQU10B01 , predecessor TIME0905
EQU10B03 -> predecessor EQU10B02 , predecessor TIME0910
EQU10B04 -> predecessor EQU10B03 , predecessor TIME0915
...
..
EQU10B15 -> predecessor EQU10B14 , predecessor TIME1010

There are additional strategies as how you can accomplish the same task more efficiently, but I assume you are
a beginner in TWS Scheduling, hence, this is the most basic approach I have laid out for you.

In case you are wondering about the console / menu commands to achieve this, enlist the help of your colleagues / TL
or refer to a TWS manual.

Hope, my efforts solve your query.

Have a Nice Day mate !! Cheers !!!

_______________________________
RJ :)
rj86
 
Posts: 1
Joined: Mon Sep 10, 2012 11:46 am
Has thanked: 0 time
Been thanked: 0 time

Re: TWS / OPC

Postby NicC » Mon Sep 10, 2012 1:28 pm

Hello and welcome!

I suspect, that as the original post was in March of this year, it was resolved in March of this year. Please pay attention to the dates of topics. Ususally it is ill-advised to resurrect an old topic.

If you need to refer to a topic when posting your own query then refer to it - do not 'tail-gate' it.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times


Return to Other IBM Tools