Sorting the CMF-DB2 records
The DB2® report is produced using an external SORT facility. An External Work data set is required to store the records before they are sorted. This data set is either specified explicitly using EXTERNAL(ddname), or CICS PA assigns one from the External Work File pool.
The records are sorted in the following order (the same as that
used in the Cross-System Work report):
- Network unit-of-work NETNAME
- Network unit-of-work ID
- Syncpoint count concatenated with the task stop time in reverse (descending) order
- APPLID
Note: The syncpoint count is used to resolve unsynchronized STORE
CLOCK (STCK) values between systems. The syncpoint count and stop
time, sorted in reverse (descending) order, shows the sequence of
tasks within the network unit-of-work. In some cases (for example,
where user event monitor points (EMPs) are used), the syncpoint count
does not reflect the sequence of events within a network unit-of-work.
For these instances, all the task records are printed, but not necessarily
in the order they happened. You can tell that this situation exists
if the stop times are not in descending order.
For more information on correlating the performance class data by network unit-of-work ID, see Correlating performance class data.
For DB2 records:
- Network unit-of-work NETNAME and ID are derived from the Accounting Token (field: QWHCTOKN).
- Syncpoint count and task stop time are not applicable. Thread ID and DB2 Begin time (in ascending order) are used.
- APPLID is the CICS® generic APPLID taken from the Connection Name (field: QWHCACCN).