This portal is to open public enhancement requests for IBM Sterling products and services. 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 updateson 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
Enhance C:D to provide better support for zEDC datasets
We are implementing zEDC across our production environment and are trying to avoid mass updates to all of our C:D processes.
We would like to be able to transmit a zEDC dataset without having to update hundreds of existing processes.
Here is the issue in a nutshell:
1) zEDC compression is invoked via the data class.
2) If a zEDC compressed dataset is transmitted with C:D, the target will NOT be zEDC compressed because C:D does not propagate the data class.
This means that the target data set will not have the compression reductions the owners counted on and will be under-allocated, likely resulting in a space abend.
3) IF the zEDC data class is explicitly specified for the allocation of the target dataset (owner has to make a change to an existing process), C:D does not propagate either the space OR the DCB information to the target dataset. With no space / DCB information the allocation will fail. Therefore the owner must change the C:D process to include data class, DCB AND space information (which might be variable) if they want the target data set to be allocated like the source dataset.
Using the DFDSS I/O exit is one option, but that is also a change. So zEDC conversions would be far from transparent if the datasets are transmitted using C:D source datasets.
The down side to the I/O exit is that the GDGs are handled by explicit goovoo, not relative, on the receiving side and are not rolled in.
What is your industry?
How will this idea be used?
If C:D is enhanced to provide data class propagation it will help provide a seamless implementation of zEDC.
Do not place IBM confidential, company confidential, or personal information into any field.