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.
We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The RFE requests function that is already partially supplied by the CICS CM tool. An approach to break this down further could be to raise an RFE for a simple compare editor in CICS Explorer, and an RFE against CICS CM for the more advanced comparison features.
I would like to extend this request to include resource definitions that are not yet defined, but are "staged" in a DFHCSDUP input deck, DFHDPLOY XML input file, or installed but from different zFS directories. The feature would include the ability to provide a set of installation-specific "rules" that could be used to audit and potentially fail an update that was being provided in the form of a DFHCSDUP input deck or DFHDPLOY XML input.
Use Case: A change is being propagated up through the hierarchy, either via DFHCSDUP or DFHDPLOY which also contains a set of resource definitions. Having this feature would facilitate:
1) Providing a "what changed" audit trail associated with the resource definition change.
2) Allowing enforcement of installation-specific policies related to resource definitions, such as issuing a "warning" message for new programs/transactions whose resource definitions specify 24-bit storage, failing changes to existing resources that would alter significant attributes such as changing previously existing threadsafe programs to non-threadsafe, changing the recoverability or allowed access types (read, update, etc.) attributes for file(s).
(I do realize that some of these functions are provided in part by the Configuration Manager product, however as currently implemented CM does not fit well in large shops consisting of many regions spanning multiple Sysplex's and running out of multiple CSD's)
Also useful would be a means of easily reporting on resource definitions added/changed after a given date/time, so that no resource changes are overlooked/dropped during a release upgrade. This could be provided in the form of a sample DFHCSDUP EXTRACT exit program that would buffer the resource attributes until the CHANGETIME is passed, and then checked against the input watershed date/time.