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.
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
At this time we have no plans to support a generic SPI. The CPSM API may be able to provide what you are looking for.
Our priority are those resources that cannot be CSD installed without some prior action.
Some examples are that have to be disabled or discarded are DB2ENTRY, ENQMODEL, JVMSERVER, LIBRARY, PROCESSTYPE, TDQUEUE, URIMAP.
Other resources require more action such as FILEs have to be closed and disabled, CONNECTIONs have to be released and out of service.
There must be others that I have yet to encounter.
Our highest priorities are those resources that we change most often. these would be FILE, CONNECTION, DB2ENTRY, TDQUEUE.
Another consideration would be IPCONN if there is any special action required before it can be installed.
This is a low priority as I am currently modifying the parm list, resource name and CDVA used by a single DFHECALL. BUT this very chancy and would like to see the CICS requests made more versitile.
We see the strategic approach to managing the life-cycle of a collection of related resources as being via the CICS bundle concept, because, for example unlike CSD resources, the group concept is maintained even after install. So a single EXEC CICS ENABLE/DISABLE/DISCARD BUNDLE(BUND01) is all that is required to manage all the resources within the bundle. You've seen us use bundles for new resources such as event bindings and OSGI artificats and over time you could expect that to be extended to the more traditional resources supported via CSD definitions today. However as you say there are 35 resources so its a case of which are a priority and why. If you have any feedback on this, we'd be interested to hear.