Author: Robert Sample
Posted: Mon Feb 27, 2017 10:33 pm (GMT 5.5)
You have made a number of assumptions that you would need to verify with your site support group BEFORE going any further:
1. The different CICS regions each have access to the same programs. This is rarely true. Each region has its own DFHRPL, and thus programs may -- or may not -- be shared between regions.
2. Jobs connecting to the region are put on hold due to high CPU usage. This is rarely, if ever, true. Jobs won't execute because MAXTASKS is reached; as long as MAXTASKS isn't reached then the job can connect to a region with high CPU usage. There may be other constraints that impact your job execution (look up short-on-storage conditions in CICS for example).
3. High CPU usage may -- or may not -- be related to MAXTASKS; you could have a single transaction using lots of CPU time.
4. Since CICS regions are dynamic, a region with high CPU usage now may have almost no CPU usage 2 minutes from now (and vice versa).
5. How do you plan on determining whether or not a given CICS region has high CPU usage (or MAXTASKS or whatever your limiting factor is)? This is NOT a simple thing to determine. There is no API or function to provide this so you'll have to write code.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Mon Feb 27, 2017 10:33 pm (GMT 5.5)
You have made a number of assumptions that you would need to verify with your site support group BEFORE going any further:
1. The different CICS regions each have access to the same programs. This is rarely true. Each region has its own DFHRPL, and thus programs may -- or may not -- be shared between regions.
2. Jobs connecting to the region are put on hold due to high CPU usage. This is rarely, if ever, true. Jobs won't execute because MAXTASKS is reached; as long as MAXTASKS isn't reached then the job can connect to a region with high CPU usage. There may be other constraints that impact your job execution (look up short-on-storage conditions in CICS for example).
3. High CPU usage may -- or may not -- be related to MAXTASKS; you could have a single transaction using lots of CPU time.
4. Since CICS regions are dynamic, a region with high CPU usage now may have almost no CPU usage 2 minutes from now (and vice versa).
5. How do you plan on determining whether or not a given CICS region has high CPU usage (or MAXTASKS or whatever your limiting factor is)? This is NOT a simple thing to determine. There is no API or function to provide this so you'll have to write code.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth