Best way to define this job?

JoPoCME · Post by **JoPoCME** » 29 Jul 2010 6:22

I have an idea but not sure it's the best way to go about it.

*edit* We are using Control-M Enterprise Manager 6.4

Our new day is at 12:00 noon.

We need to define an Enterprise job that will run at 10:00, 14:00, and when mainframe condition CICS-PERS-DOWN is satisfied. Meaning this job should run at the specified times or if the specified condition is met.

The job will be scheduled everyday so the time condition shouldn't be an issue but how do I get the job to ignore the time conditions in regards to the CICS-PERS-DOWN condition?

Hope I explained it clear enough...

I'm thinking that there will need to be three jobs created for this. One that is scheduled for the times and a second that is waiting daily for the condition CICS-PERS-DOWN so that it can DO FORCE JOB on the third job that doesn't have time conditions.

Any help is appreciated.

Banshee06 · Post by **Banshee06** » 29 Jul 2010 6:57

Well if you new day is at noon. Then you will have to have one job run at 10:00 am and another job for the 14:00 run.
Now does the CICS condition have to be satisfied with the time restraints?
Or if the CICS condition isn there at 10:00 or 14:00 the job will run anyway?
Or does it need to have the CICS condition also?

JoPoCME · Post by **JoPoCME** » 29 Jul 2010 7:07

Not sure I'll need a second job because of time since this will be running everyday and since it will be cyclic set to run at specific times. It would likely be necessary to have two jobs if it was to run only Mon. - Fri. I believe.

These need to run in these instances:

If it is 10:00 then execute job.

If it is 14:00 then execute job.

If condition CICS-PERS-DOWN is satisfied then execute job.

They are each individual runs and not co-dependent.

... I should have explained it more like that, sorry.

Banshee06 · Post by **Banshee06** » 29 Jul 2010 7:16

I would think you would need four jobs then
One for the 10:00 run at noon this job will go away
One for the 14:00 run
One for the am Conditional run which will go away at noon
One for the Pm conditonal run
Maybe someone else has a better solution but thats the way I setup jobs like these

JoPoCME · Post by **JoPoCME** » 29 Jul 2010 9:58

I see this being one scheduled cyclic job, one scheduled job and one force job...

Job 1 to run at set times of 10:00 and 14:00 everyday.

Job 2 that comes in everyday waiting for condition CICS-PERS-DOWN.

Job 3, forced by the job 2, which has no conditions.

Anyone else?

Banshee06 · Post by **Banshee06** » 29 Jul 2010 10:37

JoPoCME wrote:I see this being one scheduled cyclic job, one scheduled job and one force job...

Job 1 to run at set times of 10:00 and 14:00 everyday.

Job 2 that comes in everyday waiting for condition CICS-PERS-DOWN.

Job 3, forced by the job 2, which has no conditions.

Anyone else?

Cyclic jobs will not span past a new day.
They will disapper at noon

JoPoCME · Post by **JoPoCME** » 30 Jul 2010 2:30

I thought they would run at the specified times as long as they aren't scheduled in a time frame. I am familar with having to create two jobs that have a time frame that spans across the new day but assumed that when you choose the cyclic option of "set times" the would run at those times.

Banshee06 · Post by **Banshee06** » 30 Jul 2010 3:52

If you have a job start after noon then it can run at 14:00 and at 8:00 the next morning. that would work if you want to run it 7 days a week.
But if you need to run the job Monday morning through Friday afternoon then you need to do somthing different.

If you have a job setup to run Monday morning as cyclic at running at 8:00 that morning and at 14:00 that afternoon the job will go away at noon and wont run the 14:00 run of the job.

JoPoCME · Post by **JoPoCME** » 30 Jul 2010 5:16

In this case the job runs everyday.

Banshee06 · Post by **Banshee06** » 30 Jul 2010 5:31

Good looks like you got a solution