Transaction resource class data
Transaction resource class data provides additional transaction-level information about individual resources accessed by a transaction. Currently, the transaction resource class covers distributed program link, file, and temporary storage queue resources.
CICS® writes one transaction resource record for each transaction that is being monitored, if the transaction accesses at least one of the resources for which monitoring data is requested.
Transaction resource data is collected when a transaction ends. You can collect information for up to a maximum of 64 distributed program links, 64 files, and 64 temporary storage queues.
The transaction resource records produced are of variable length depending on the number of resources for which data is being collected. For only one distributed program link, the record length is 436 bytes plus 32 bytes for the program data, making a total of 468 bytes. Each additional resource extends the length of the record. Each file adds 112 bytes and each temporary storage queue adds another 120 bytes. For example, if a transaction accessed 1 distributed program link, 5 files, and 2 temporary storage queues, the total length would be 436 bytes + 32 bytes + 560 bytes + 240 bytes = 1268 bytes.
Performance class data provides information about distributed program link, file, and temporary storage queue resource accesses, but this information in the performance record is given only in total, for all distributed program links, files, and temporary storage queues. Transaction resource data breaks this information down by individual distributed program link name, file name, and temporary storage queue name. The distributed program link information is held in the DFHPROG performance data group, the file information is in the DFHFILE performance data group, and the temporary storage queue information is held in the DFHTEMP performance data group.
You can enable transaction resource class monitoring at startup by coding MNRES=ON (together with MN=ON) as a system initialization parameter. Alternatively, you can use the monitoring facility transaction CEMN or the CEMT or EXEC CICS SET MONITOR command to enable transaction resource monitoring dynamically.
The maximum number of distributed program links, files, and temporary storage queues monitored for each transaction is specified by the DPL, FILE, and TSQUEUE parameters on the DFHMCT TYPE=INITIAL macro. The default is DPL=0 for distributed program links, FILE=8 for files, and TSQUEUE=8 for temporary storage queues. If transaction resource class monitoring is enabled (MNRES=ON), these defaults apply if you have not specified those options in the MCT. If the default values are insufficient, you must assemble an MCT that specifies a higher number.
If you do not want to collect transaction resource data for either files or temporary storage queues, but you do want to collect transaction resource data for the other resource, you must assemble an MCT that specifies FILE=0 or TSQUEUE=0 to stop transaction resource data being collected for the appropriate resource.
Transaction resource class data for a file or temporary storage queue is collected and recorded only for local resources, not for remote resources. When an application accesses a remote file or temporary storage queue, a transaction resource record is produced in the CICS region where the resource is defined locally, but no record is produced in the application-owning region.