When a transaction abends in a region, CPSM should not route any transactions in the same WLM transaction group Merged

When a transaction abends in a region, CPSM should not route any transactions in the same WLM transaction group to this region until the region is healthy again

Customer had observed that following an abend of a transaction in a CICS region, CPSM was still routing transactions with different ids to the CICS region. CPSM currently allows the 'Acceptable level of abend probability' and the 'Acceptable abend load threshold' to be specified on a WLMSPEC or on a TRANGRP definition. However, these values are taken into account on a transaction ID basis. So, if TRAN1 abends in CICS1, the abend compensation logic in CPSM's routing will ensure that another instance of TRANS1 is not routed to CICS1 as defined by the above mentioned probability/threshold values. However, other transactions (eg. TRANS2, TRANS3, etc.) may still be routed to CICS1. If we understand correctly, once a transaction abends in a given CICS region, Customer would like to regard the region as unhealthy and steer all transactions away from that region until the region becomes healthy again. To address this, we could add a check box to the WLMSPEC and TRANGRP definitions to indicate that once a transaction abends in a region, no transactions should be routed to that region until the region becomes healthy again.