IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
CICS and IMS transactions in composite requests
Even though all transactions on a CICS or IMS™ region in the managed space appear in ITCAM for Application Diagnostics, they are not necessarily treated as part of a composite request, even if they invoke programs on other regions.
A transaction on a CICS or IMS region is part of a composite request if it meets the following criteria:
- The CICS or IMS region is in the managed space.
- The Home Server is in the managed space.
- The application server that serves the Home Request is a J2EE application server, and is in the managed space.
- For CICS: The application on the Home Server uses ECI to access CTG. (This includes applications that use CCI as their JCA resource adapter, since CCI uses ECI.)
- The ECI invocation is synchronous.
- The COMMAREA of the CICS program invocation has at least 11 bytes of available space.
- For IMS: The application on the Home Server uses IMS Connect for Java (IC4J) to access IMS Connect.
If any of these criteria are not met for an EAI request, ITCAM for Application Diagnostics does not identify the request as being part of a composite request. However, the core ITCAM for Application Diagnostics features are still available for whatever parts of the transaction are in the managed space.
For example, if an application in C++ invokes a CICS program on a CICS region in the managed space through CTG, the CICS program is displayed as a request inITCAM for Application Diagnostics. However, the C++ application request is not displayed in ITCAM for Application Diagnostics. The reason is,ITCAM for Application Diagnostics does not monitor C++ applications. In this case, ITCAM for Application Diagnostics does not identify the CICS transaction as part of a composite request.
Likewise, if a Java application uses EPI to access CTG, ITCAM for Application Diagnostics does not track the EAI as a composite request, even if the application is in the managed space. In this case, the requests on both the J2EE application server and in the CICS region are displayed in ITCAM for Application Diagnostics, but are displayed independently, and are not identified as a composite request.
The final condition, based on the application's use of the COMMAREA, is due to the methodology of tracking composite requests, which involves use of the COMMAREA. In practice, it is rare that program invocations use so much of the COMMAREA that there is not room for this correlation information. In these exceptional cases, ITCAM for Application Diagnostics does not attempt to identify the EAI as a composite request, and the individual requests are displayed in ITCAM for Application Diagnostics as independent requests.
Parent topic:
Composite requests involving CICS and IMS systems