Ways to Identify the delays involved in DPL transaction execution spanned across multiple regions
Nageswararao V Gokavarapu 2700013B8D Visits (4795)
TXSeries provides multiple utilities to monitor the execution status of the transaction. Users can use the following tools to monitor the transaction execution when transaction spanned across multiple regions.
1. CICS Monitoring Facility (CMF) is a comprehensive customizable facility provided by TXSeries. It gives a complete view of the time spent by a transaction in the system across its lifetime. CMF contains about 100 pre-defined fields, which collect data. Each CMF record contains information from all of these fields for each transaction. Because monitoring all these fields can result in the usage of a large amount of disk space, CMF allows you to select specific fields for moni
User can enable the CMF facility in all regions to check the transaction statistics like when transaction started and when it completed, time spent for scheduling the transaction, program name etc. The following link provides more details on different CMF fields supported by TXSeries and its desc
2. As the transaction is spanned across the multiple regions, user can enable Remote Task Information facility to debug the DPL transactions spanned across multi region environment. This utility will provide information like the CICSAS process IDs which executed the task, task number, transaction name and many more. Using this information user can map the tasks executed across multiple region which are part of single instance of a transaction. The following link provides complete filed details that this facility provides. http
3. If user intend to log some more information during routing the transaction across regions while executing EXEC CICS LINK, user can define additional customized DPL user exit to log the additional information. From TXSeries 8.1, multiple user exits can be defined by the user and those user exists executes one after the other based on the UserExitSequence attribute definition.
For more information on user exit chaining refer, http
User can define the UserExitSequence attribute along with UserExitNumber in program definition entry. For more details on these fields refer, http
Starting from TXSeries 8.1, additional fields added in the DPL user exit to provide details of the client and peer region. This DPL user exit is invoked during LINK invocation on front-end region, before executing the called program on back-end region and after returning from LINK API in front-end region. User can add additional log information in user exit if required.
For more details on these fields refer, http
These 3 facilities user can enable to understand the complete flow of transaction across regions when transaction spanned across multiple regions.