Watson Supply Chain Ideas

Submit new product ideas for Watson Supply Chain 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

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

SMS Compressed Dataset Enhancement with NDM

Visa would like to see Connect Direct transmission of SMS compressed datasets improved. Today, when we transmit a compressed dataset, if it is done with out coding the DCB parms in the process it always fails on the remote node with a space abend. The benefit of Connect Direct is you can avoid doing DCB parms with Z/OS to Z/OS transmissions. It would make sense for Connect Direct to be able to figure out the real size of the sending dataset, so that it could properly allocate the same dataset on the otherside.

We initially had a problem ticket opened for this issue, and support advised us this would indeed need to be an enhancement request. Please advise if you need any supporting information or if you have any questions.

 

This is somewhat urgent for us, as we have thousands of Connect Direct Processes that currently have no DCB information coded with in. We are about to enabled SMS Compression on many of our production datasets, but we will have to add DCB information in for every HLQ we turn on SMS compression for to avoid the space abends on the remote Z/OS node. This feature being added would save us an immense amount of work.

 

Thanks,

Craig

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 10 2018
  • Declined
How will this idea be used?

This is somewhat urgent for us, as we have thousands of Connect Direct Processes that currently have no DCB information coded with in. We are about to enabled SMS Compression on many of our production datasets, but we will have to add DCB information in for every HLQ we turn on SMS compression for to avoid the space abends on the remote Z/OS node. This feature being added would save us an immense amount of work.

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
    August 14, 2018 13:10

    Thank you for opening this enhancement request with IBM.  I have reviewed it thoroughly with my developers.  Unfortunately we don't believe that this is a candidate for C:D z/OS enhancement due to technical limitations.  I must reject this request, but I've included some suggestions from our development team on other ways to meet your needs.  Please don't hesitate to contact our support team if you have questions.


    SMS compression and allocation is controlled by SMS generally with an SMS Management class. Data class or Storage class definition and each zOS may define those differently with different names. A CD Process cannot propagate those names from the PNODE to the SNODE because of that.  Adding DCB Space information into the Process is one way to do that; however the more effective way is on the receiving side define an SMS class to handle that allocation and override what the CD Process attempts to do.

     

    SIncerly,

    Chris Sanders

    Connect:Direct Offering Manager