How to make certain jobs only run when it is decided to run jobs for that region for testing.

[RenateLynn Edwards]

I need to see if anyone has any suggestions for the following scenarios.

There are a few jobs that would be set up to run simular to how they run in production but ONLY when we are testing in that region.   I.E. 
1.  QARMW250 would need to run every other Sunday but ONLY if we are testing in the QA region.  I have used a do not run after date to cause it not to run if we aren't testing in that region or to take off the date to let it run if we are testing in that region.  .   
2.  QASTR099 is triggered in by QASTR010 but currently is set to exec=n because we aren't running tests in region QA.

This is something we have recently come across because before this we only dealt with one or two strings of jobs that needed to run and it was easy to know what they were, but it looks like we are going to have 12-20 or more jobs in the future that we have to either have scheduled or have triggered that ONLY should run when testing in that region is taking place.   And we will have to also set parameters on if we are only testing for say 5 days, do we turn on everything or only some things, but when we are testing in that region for 2-3 months we would need to turn everything on but then turn it off when we push the upgrade testing to the next region.   

How does everyone keep track of these kinds of jobs?   To kow when the exec=n or the don't run after date need to be changed so that the jobs run if we start running tests in that region and have to go back to exec=n and change date to not run after when we are through testing in that region.   

thanks


------------------------------
RenateLynn Edwards
Workload Automation Administrator CA7/CA11/CA1
Security Service Federal Credit Union
Texas
------------------------------

[emckenzi]

You can use the BADTE and ADATE together.  Ex. If you want the jobs to run for only a specific period of time like BDATE=21061, BTIME=0600,ADATE=21067,ATIME=0600. The jobs will turn off automatically.  You will have to keep changing the dates to turn them back on and off.  This is how we do it.  We normally turn off the head of stream jobs because we turn off the entire region, not one or two jobs.  We have an environment group that lets us know what jobs and when to turn the jobs on/off.

[RenateLynn Edwards]

How are you turning off the entire region?

------------------------------
RenateLynn Edwards
Workload Automation Administrator CA7/CA11/CA1
Security Service Federal Credit Union
Texas
------------------------------

[Damion Rennie]

Perhaps a different scenario​ but when we run our DR events we will use a combination of NXTCYC (OFF) and/or EXEC=N to prevent batch from running over a period. We usually DEMAND on a job that contains a BTI with all these commands within. When the DR event has completed there is a task on the SoE to DEMAND on the backout which will NXTCYC (ON) and EXEC=Y.

[RenateLynn Edwards]

Thanks @Damion Rennie, that sounds like an interesting way to do this.  ​

------------------------------
RenateLynn Edwards
Workload Automation Administrator CA7/CA11/CA1
Security Service Federal Credit Union
Texas
------------------------------