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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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
CSMIs are really are part of the 'user' transaction and we wouldn't consider them 'system' transactions at all.
It is not correct that for transaction routing between a TOR and AOR that CSMI, as well as the user's transaction, are started. In the transaction routing case; in the TOR a transaction is started which then routes the same transaction ID (not CSMI) to the AOR where is attached to process the application program(s). There is only one transaction created in each region (one in the TOR and one in the AOR) and CSMI is not used at all in this case. CSMI's are used for function shipping requests, for example; to AORs in the Distributed Program Link case or to FORs for requests such as remote files, remote tsqueues, remote start requests, and so on. But even when CSMIs are used, they are only ever executing as part of the 'user' application and they therefore need to be controlled and managed just like any user transaction. Also, from a CPSM WLM perspective they need to be included and managed as part of the total CICS user workload.