Combination of transactional subsystem data in a unit-of-work
When UIE processes transactional subsystem data, it attempts, by default, to combine all of the resources from the individual transactions that make up a unit-of-work and create a single transaction.
A unit-of-work can consist of:
- Transactions that execute within one subsystem, such as CICS MRO
- Transactions that execute across subsystems, such as CICS calling Db2 or IMS calling Db2
- Transactions that execute across systems, such as cross system MRO
- Transactions that execute across subsystems on different systems
To combine the resources of all the transactions in a unit-of-work, UIE matches the transactions that execute in server address spaces to the transactions that execute in the requestor address spaces, including:
- CICS MRO
- CICS-Db2
- CICS-IMS DBCTL
- CICS-MQ
- IMS-Db2
- IMS-MQ
Before the data can be combined, it must be sorted by the key fields that identify the requestor and server transactions. With large systems, sorting can require large amounts of DASD space and additional processing time. To override the default subsystem data matching, you can specify parameters for the APPLCONTROL command. You can use the APPLCONTROL command to turn off the matching of subsystem data, based on the subsystem type, system ID, or subsystem ID.
For more information, see APPLCONTROL.
In the UIE Summary report, a Unit-of-work ID Summary report will show the number of transactions that matched in a unit-of-work. A low matching percentage might indicate that you are not processing all the data for the unit-of-work or that you are missing key identifiers in the subsystem data. For example, the CICS unit-of-work ID is not contained in the Db2 accounting record.
Related topics