MQ transaction groupings
You can use combinations of two of the possible transaction grouping fields to define a transaction grouping. The transaction grouping defines a transaction as a group of MQ thread occurrences that have the same value in the chosen transaction grouping fields. For example, if you choose CORR as the primary transaction grouping field, all MQ thread occurrences with the same correlation ID are grouped into a transaction. For Server Request data, the default primary grouping is TYPE and the secondary transaction grouping is blank (no grouping). For J2EE and WEB data, the default primary and secondary transaction grouping is blank (no grouping).
For a description of each transaction grouping field, see MQ-transaction-groupings-values.
You can establish a separate transaction grouping for each of the seven connection types that request MQ services. UIE then summarizes the data for each connection type based on the transaction groupings that you establish.
The default transaction groupings for each connection type appear in the following table:
Connection type | Primary transaction grouping | Secondary transaction grouping |
---|---|---|
CICS | CORR | TRAN |
IMS MPP and BMP | CORR | TRAN |
MVS/TSO | CORR | TRAN |
IMSCNTL | CORR | TRAN |
COMMAND SERVER | CORR | TRAN |
CHANNEL INITIATOR | CORR | TRAN |