IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.