This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Our Mainframe event Acquisition System (MEAS) software product is integrated with AppDynamics Application Performance Monitor (APM). This integration allows APM to monitor transactions that cross platform boundaries, such as from a Windows Application Server to CICS Transaction Gateway (CTG) and CICS TS on z/OS and back. When the transaction is initiated on the distributed systems platform, APM injects a unique transaction correlation id into the transaction header.
When the transaction makes the transition from distributed systems to z/OS and uses the IPIC protocol, CTG creates an ODR, then calls CICS TS. When CICS TS sees that an ODR has already been created, the call to exit XAPADMGR does not take place. In this case, we cannot populate the ODR with the APM created unique ID to continue to track the transaction.
We respectfully request an option be added to CTG which when set, would indicate to CTG that it should not create ODR data. This then will allow the XAPADMGR exit in CICS to be called where we can insert the APM unique ID in the ODR.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Enterprise Tooling
Product - CICS Transaction Gateway
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - CICS Transaction Gateway
Correct - we would like to be able to inject our existing unique ID into the USERCORRDATA field, in CTG T2 exit, regardless of run time environment or communications protocol.
Today, CICS TG creates the ODR, and optionally sets a correlation value in the USERCORRDATA field - only for JEE applications running in WAS 8.5. For IPIC connections, XAPADMGR is not triggered. The proposal is simply to open up the setting of USERCORRDATA to other CICS TG APIs, and other CICS TG application run time environments (any JEE application server, purse Java applications, .NET Framework-based applications.
XADAPMGR would still not be triggered for IPIC connections from CICS TG - we are not proposing to change that.
Thank you very much for your reply. Am I correct to understand that you are indicating that we can inject our existing unique id that is passed to us from an open-system application call to CTG and place that value in USERCORDATA? Then USERCORRDATA will be passed to the XAPADMGR and TRUE exits in any/all CICS regions used in the business transaction?
There is a misapprehension built into the request, in that the removal of ODR data within CICS TG components connecting to CICS using IPIC, will not then result in XAPADMGR being called. A more realistic proposal would be for some mechanism to be built into the CICS TG APIs, allowing the injection of a value for use as USERCORRDATA. Please provide an indication as to whether this alternative proposal would suit your requirements.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Enterprise Tooling
Product - CICS Transaction Gateway
Component - Runtime
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
Component - Other