Skip to Main Content
IBM Z Software


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Delivered
Categories Runtime
Created by Guest
Created on Apr 4, 2012

Transaction tracking from WAS into CICS through CICS TG

The requirement is for a unique request correlation token that

-- Is created dynamically at the point of entry of a request into WAS
-- Is passed between J2EE components in WAS and between different WAS server JVMs
-- Is passed across the JCA interface to resource adapters to enable other middle ware components (in this case CTG and CICS)
-- Is passed by CTG to CICS and is used by the CICS transaction tracking infrastructure
-- Is compatible with the J2C beans developed in RAD

Idea priority High
  • Guest
    Reply
    |
    Oct 5, 2015

    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

  • Guest
    Reply
    |
    Dec 21, 2012

    This requirement is addressed by CICS TG 9.0 which is generally available December 14th 2012.

  • Guest
    Reply
    |
    Aug 21, 2012

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status.  Please note:
    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.   Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

  • Guest
    Reply
    |
    Apr 26, 2012

    As customers may already have a "request-tracking-infrastructure" in place in the distributed environment, it should be possiblel to also add a customer-"request correlation token" in an "Exit" on the WAS-side and propagate it to CTG / CICS. in CICS, there should be an "Exit" which can be used to e.g. remove this token and store it e.g. in a TS-Queue to be accessed by the application later. The propagation of the customer-"request correlation token" within CICS is of special interest when the CICS application does outbound Webservice calls to e.g. IIS (Microsoft .net application server). (Ann.: For Webservices to CICS, we are currently already implementing the propagation of the "customer-"request correlation token" to CICS -> within CICS -> from CICS to e.g. IIS) .