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.
This requirement has been re-evaluated. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
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
In summary, this is certainly something we want to address but it will be medium term delivery, not short term in the next release.
Ian, thank you for the extra information.
I had submitted an update this RFE but it seems not to have been saved, so I'll do it again.
To answer the question, as there are only a (relatively) few API commands it is hard to split this into many tiers.
My advice would be split it by READ / WRITE functionality, initially.
In my experience most customers use CONNECT/DISCONNECT/TERMINATE and GET/FETCH/TRANSLATE. And ORDER/QUERY. All these are READ only data from the API and do not update any CPSM objects.
Commands that provide updates to CICS or CPSM objects could be done at a later stage as I believe they are lesser used commands... such as CREATE/PERFORM/SET/REMOVE/UPDATE.
Perhaps unspecified commands are a halfway house / third tier to be done as another stage.
We have moved this requirement into the 'Need More Information' state. As Ian says above, this is a considerable piece of work and would likely be achieved only in a number of phases and not in a single release. Therefore, the further information required is a priority list of API's (or API areas). This will help us determine an order of priority for delivery. Many thanks.
As I'm sure you can imagine, this would be a considerable piece of work. It would likely be achieved only in a number of phases and not in a single release, so it would be useful to understand the priority list of API which provide the most value first.
Mayur, please can you take a look at this and add a comment. Comments are private to RTC unless prefixed by in which case they are mirrored back to RFE which is open to anyone to see. I suggest we start with some private comments.