RMF report example: fewer ended transactions with increased response times
The RMF™ workload activity report shows increased response times and a decrease in the number of ended transactions over a few days.
Possible explanations
- Conversion from ISC link to MRO
- When two CICS® regions are
connected using an intersystem communication (ISC) link, they behave
differently than when they are connected using multi-region operation
(MRO). One key difference is that, with ISC, both the TOR and the
AOR are receiving a request from z/OS® Communications
Server, so each believes it is starting and ending a given transaction.
- If a user request is routed from the TOR to an AOR using ISC, two transactions complete. Assuming they have response times of 1 second and 0.75 seconds, the resulting average is 0.875 seconds.
- If a user request is routed from the TOR to an AOR using MRO, the TOR transaction completes taking 1 second. The AOR reports the 0.75 seconds as execution time.
Therefore, converting from an ISC link to an MRO connection for the same workload, as shown in this example, could result in half the number of ended transactions and in increase in the response time reported by RMF. The difference could be much more significant if the AOR to FOR link was converted.
Possible actions
- Increase CICS transaction goals
- Increase the CICS transaction goals before converting from ISC to MRO, particularly if the FOR transactions are classified to the same service class as your end-user transactions.