Enhance EXPIRY processing TS-queues performance

You can use a TSMODEL to set an EXPIRY on a TS-queue.
If you install such a TSMODEL in CICS, then CICS will initiate a SCAN process, that will scan main/auxilary and CF-TS-Pools for queues that has expired.
This scan process will run in all cics regions that have a TSMODEL with an EXPIRY specified.
The scan will run with an interval of 1/10 of the lowest EXPIRY interval.
For example, if you have two TSMODEL, one with EXPIRY=10(minutes) and one with EXPIRY=30(minutes), then the scan process will run every 1 minute in each cics region that have the TSMODEL installed.
Even when the TSMODEL specifies no POOL (local queues) both MAIN/AUXILARY and all CF-TS-POOLS are scanned every minute.

No SMF110 records is written for the process that does the scans for expired TS-queues. The increase of CPU-usage is only seen in the SMF30 records.

The performance impact of having many cicses (in our case 190+) scan all the CFs are so massive, that the way these scans are done should be changed in order to mitigate the performance impact.



We suggest the following changes:

1) For TSMODELs without a POOL, the scan process should only scan locally in main/auxiliary and use the PREFIX to qualify the scan.

2) For TSMODELS with a POOL, the scan process should scan only that POOL and use the PREFIX to qualify the scan.

CICS should coordinate between regions connected to a specific pool in order to only do the scan from one region.

3) The INTERVAL of scans should be customisable in the TSMODEL.

4) The scans should run under a CICS system transaction that will write SMF110. So we are able to track the resource usage of these scans.