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

Provide additional granularity for the UPPER.CASE= initialization parameter

Currently, as documented in the C:D for zOS  V5.2 Administration Guide, the UPPER.CASE= parameter determines if initialization messages are send to the console in Upper (YES) or Lower/Mixed case (NO). However, this parameter also dictates  if information in the Select Statistics (SS)  Display report is presented in upper or mixed case.

In an environment where there are business partners that are non-mainframe nodes or partners that use Secure+, the Select Statistics Display Report presents a great deal of useful information Coding UPPER.CASE=NO is desirable in this situation because converting all of the information, such as destination filenames and secure+ certificate common names to upper case may be misleading.

Additionally, in an environment where an automation package is used, changing the UPPER.CASE parameter may necessitate a rework of some/many of the automation rules for Connect:Direct if they interrogate text beyond the message ID.

I would envision a possible solution as multiple sub-parameters under the UPPER.CASE initialization parameter. As an example:

 

UPPER.CASE=(YES, NO) 

 

Where the first sub-parameter control the case of the initialization messages and the second sub-parameter control the case of the Select Statistics Display report information. This would allow any Connect:Direct zOS user to change one of the options independently of the other.

.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 8 2019
  • Is a defect
How will this idea be used?

As a Service Bureau customer, I have many Connect:Direct business partners that are NOT mainframe nodes. As a service provider in the Finance/Banking industry we make extensive use of Secure+. Having information presented in Mixed case is critical to successful operation.

As a customer using extensive mainframe automation, we already have many Connect:Direct messages automate. We are also using UPPER.CASE=YES in our initialization parameters.    

Controlling the case for both of these options in a single parameter forces me to choose which one I can support at the cost of the other. 

What is your industry? Financial Markets
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Chris Sanders commented
    July 01, 2019 12:07

    Thank you for your patience as we reviewed and worked on this item. After discussion across my team we agreed that this should be handled as a defect. We have released PTF UI63481 for C:D z/OS v5.2. Please grab that maintenance which should resolve this issue.

    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager