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
There has been no reponse from the customer about if an automation procedure was put in place after the CF structure was recovered. We have no plans to provide such function.
In the PMR associated with this RFE there was reference to "working with the automation team to restart CKTI once the structure is recovered". Were you table to put such a procedure in place ?
WMQ does not have any mechanism (like an event notification) that CICS could use to know when a CF structure (or other transient condition) has recovered. This has been considered by WMQ but is not going to be delivered any time soon, if ever.
Even If such a mechanism were implemented, it's not clear how CICS would know that starting/restarting CKTI would be a sensible reaction. If CICS actually knows that CKTI is interested in the recovery that just happened (not sure how it would know that) then it could start/restart CKTI.
A more viable alternative, which might also work for other recoverable situations, would be for CKTI itself to retry periodically (say every minute).
However, none of the above are necessarily an enormous improvement over doing it using automation.