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 Is a defect
Created by Guest
Created on May 8, 2019

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:




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.


What is your industry? Financial Markets
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. 

  • Admin
    Chris Sanders
    Jul 1, 2019

    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.


    Chris Sanders

    Connect:Direct Offering Manager