The transaction resource class data fields produced by the CICS® Monitoring Facility (CMF) are described in this section.
Transaction resource class data provides additional transaction-level information about individual resources accessed by a transaction. Currently, the transaction resource class covers file and temporary storage queue resources.
The maximum number of files and temporary storage queues monitored for each transaction is limited by the FILE and TSQUEUE parameters on the DFHMCT TYPE=INITIAL macro. The default is FILE=8 for files and TSQUEUE=4 for temporary storage queues. Therefore, you might need to assemble an MCT that specifies either or both FILE and TSQUEUE options if the default values are insufficient, or if you do not want to collect transaction resource data for either files or temporary storage queues. One transaction resource record is written for each transaction that is being monitored, provided the transaction accesses at least one of the resources for which monitoring data is requested, (for example, at least 1 file if you specify FILE=number).
Transaction resource records are variable length, depending on the number of resources for which data is being collected (for example, one transaction might access only 1 file, another 5 files and 2 temporary storage queues, and so on).
For only one file, the record length is 188 bytes plus 96 bytes for the file data (284 bytes). Each additional file adds another 96 bytes. The maximum number of files for which you can collect transaction resource data is 64.
For only one temporary storage queue, the record length is 188 bytes plus 96 bytes for the temporary storage queue data (284 bytes). Each additional temporary storage queue adds another 96 bytes. The maximum number of temporary storage queues for which you can collect transaction resource data is 32.
Performance class data also provides information about file and temporary storage queue resource accesses, but this information in the performance record is given in total only for all files (see DFHFILE fields) and all temporary storage queues (see DFHTEMP fields). Transaction resource data breaks this information down by individual file name and temporary storage queue name, up to the maximum number specified in the MCT. Transaction resource information is completed for each task when the task terminates.
In contrast to performance class data records whose format is described in associated dictionary entries, transaction resource class data records are not defined in the dictionary record. The transaction resource class data records are fixed format.