IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 10 2019
  • Uncommitted Candidate
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. 

What is your industry? Banking
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Chris Sanders commented
    19 Aug, 2019 01:34pm

    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.

    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Apr, 2019 11:10pm

    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.