Skip to Main Content
IBM Sterling

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Apr 10, 2019

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? 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. 

  • Admin
    Sep 8, 2023

    This enhancement has been implemented in Connect:Direct v6.3. Hence marking this as delivered. Thank you for your patience.

    Product Management

  • Guest
    Jun 5, 2020

    Greetings. I am with CDZ development and am researching this RFE. I have some questions and comments. Currently, CDZ will not propagate DATACLAS, and will not propagate SPACE and DCB if either DATACLAS or LIKE is specified in the TO section.

    Do you want CDZ to propagate the source dataset's DATACLAS based on the setting of a new INITPARM? If not, how then?

    Do you want CDZ to propagate SPACE and DCB if the DATACLAS is propagated? Or also propagate SPACE and DCB if the DATACLAS is specified in the TO section? Do you want them propagated based on the same setting as for DATACLAS propagation? Or a separate setting?

    Do you want CDZ to propagate DATACLAS, SPACE and DCB if the LIKE parameter is specified in the TO section?

    Note that in all cases, propagation will not be done for a parameter if that parameter is specified in the TO section.

    Note that if the DATACLAS's OVERRIDE SPACE=YES, then the DATACLAS SPACE attributes unconditionally override any other method of supplying SPACE attributes. CDZ cannot change that.

  • Admin
    Chris Sanders
    Aug 19, 2019

    Thank you for opening this enhancement request with IBM. I have reviewed it with my team and we believe that it would be valuable addition to C:D zEDC capabilities. I have accepted this as an uncommitted candidate and we will look to add it to our roadmap moving forward.


    Chris Sanders

    Connect:Direct Offering Manager

  • Guest
    Apr 10, 2019

    Just to add a little detail on what we would like:

    Have the ability to propagate the data class from source to target if both are zOS.

    If dataclas is propagated or explicitly specified to have the ability to propagate the DCB and space information.