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 Not under consideration
Categories Runtime
Created by Guest
Created on Jan 18, 2012

Specify (remote) Transid on Function Shipped Requests other than DPL

It is currently possible to specify the transaction-id under which a DPL request will be invoked in the remote region using the "Transid" remote attribute on the program definition.

This should be expanded to all function shippable remote requests, eg- files, TD Queues, TS Models, etc.

The has benefits for transaction accounting, particularly in the ability to provide more accurately targeted charge-back, as well as for transaction security and performance monitoring purposes.

Nb- I originally raised this as a FITS request in 2002 (!) and, as I understand it, it was being considered as a suggestion, but it went missing somewhere along the line. (I recently confirmed this with Mark Cocker and John Tilling, who had been aware of it in at that time.)

Idea priority Medium
  • 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 - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Jun 9, 2012

    We currently have no plans to provide any enhancements in this area over and above what can be achieved via CICS PA's cross region report as mentioned earlier. The data is in the CICS 110 records so other products or roll your own can do the same.

  • Guest
    Reply
    |
    Jun 8, 2012

    Comments received by email

  • Guest
    Reply
    |
    May 17, 2012

    Paul, any further comments ?

  • Guest
    Reply
    |
    May 16, 2012

    Earlier comments have accurately described the various processes that could be, and indeed are, used to correlate cross-region transactions. Most, if not all, use the network uow to correlate the data from multiple CICS regions. CICS PA has the cross-system work report, and also data set where the actual data is combined into a single record that spans all the regions, and which can then be used as input to an accounting/chargeback process. From a z/OS WLM classification perspective CICS classifies the work request into its service/report class and this is then inherited wherever the transactions flows so that we can manage and report all the related transactions together.

  • Guest
    Reply
    |
    Feb 2, 2012

    The chargeback mechanism in the client I am concerned about is driven by CICS SMF 110 records. In this case the transaction-id for the server side function-shipping transaction is always CSMI. Of course it could potentially be modified via an exit but this is hardly as functional as being able to specify it in the resource definition. The client is using neither CICS PA nor WLM for transaction routing, but uses TDS (Tivoli Decision Support) in the chargeback process, but I don't know anything about how that all works. Does that help?

  • Guest
    Reply
    |
    Feb 1, 2012

    I think we need to understand better the business justification. As far as transaction accounting and chargeback is concerned it is possible to use CICS PA to report on cross region work and assume that other packages / ryo code can do the same. If monitoring and chargeback can be dealt with already, and z/OS WLM is rightly inheriting the SRT token from the AORs, then it is not clear what compelling reason really justifies this. Program link justifies it on the basis that the customer business logic might legitimately depend on the tranid.

  • Guest
    Reply
    |
    Jan 18, 2012

    Dorry, this was duplicated somehow with #16295 and so this one can be deleted.

0 MERGED

Specify (remote) Transid on Function Shipped Requests other than DPL

Merged
It is currently possible to specify the transaction-id under which a DPL request will be invoked in the remote region using the "Transid" remote attribute on the program definition. This should be expanded to all function shippable remote requests...
almost 13 years ago in CICS Transaction Server for z/OS / Runtime 2 Not under consideration