Hi Experts,
I have 2 set of stream say stream 1 and 2.
Stream 1: contains jobs A -> B -> C -> A (all are dependent)
It's a cyclic stream runs every hour
Stream 2: contains jobs D -> E -> F -> D (all are dependent)
It's a cyclic stream runs every 3 hours
So, my requirement was when ever stream-1 runs no jobs in stream-2 should run.
We tried giving high priority to stream-1 and define Quantitaive resourse = 1 for all jobs in stream-1 and 2. But it didn't work well.
I would like to know your suggestions, Thanks in advance.
Streams getting clash
Re: Streams getting clash
Sobriquet wrote:Hi Experts,
I have 2 set of stream say stream 1 and 2.
Stream 1: contains jobs A -> B -> C -> A (all are dependent)
It's a cyclic stream runs every hour
Stream 2: contains jobs D -> E -> F -> D (all are dependent)
It's a cyclic stream runs every 3 hours
So, my requirement was when ever stream-1 runs no jobs in stream-2 should run.
We tried giving high priority to stream-1 and define Quantitaive resourse = 1 for all jobs in stream-1 and 2. But it didn't work well.
I would like to know your suggestions, Thanks in advance.
Even i thought of that, but the problem is if Stream-2 got stuck because of some reason it should not effect Stream-1 execution at any point.chookgate wrote:Use exclusive control resources (all jobs require the same resource), and also make the first job in stream one dependent on a condition the first job in stream 2 deletes and the last job in stream 2 adds), and make the first job in stream 2 dependent on a condition the first job in stream 1 deletes and the last job in stream 1 adds.
Hi chookgate,chookgate wrote:So basically you don't want stream 1 to run whilst stream 2 is running and is incomplete - except when stream 2 has a problem then you want stream 1 to be able to run even though stream 2 isn't complete?
In that case think about what might make stream 2 "get stuck" and cater for it - eg you could set the jobs to "on error, do cond" and post back the condition that stream 1 needs to start.
If by "stuck" you mean a hanging or overrunning job - I don't think you can expect controlm to be able to tell the job is "stuck".
The actual intention was neither stream-1 bothers stream-2 (or) stream-2 bothers stream-1 if any of them get hung.
Yes i agree it was a limitation that control-M can't say if the job was stuck.
So, for the workaround we have did some modifications in stream like giving high priority to one stream and change the time of the second stream to start 15mins later (where we assume other stream gets completed).
I am seeking for better option with less complexity.
Best regards.
Yes you are right in the design of cyclic stream.bicycleor wrote:Can I ask how you did a cyclic stream? I was thinking of setting every job to be cyclic and chain them together, but it seem messy.
Stream 1: contains jobs A -> B -> C -> A (all are dependent)
It's a cyclic stream runs every hour
I am using ^M 6.1.
What was the complexity you are facing in designing the cyclic streams?