IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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?||Banking|
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.