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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Add option for setting NONE character of Special Value property instead of setting the full absolute value without changing padding character
We need to have an option to set the character used in the NONE Special Value property in a type tree's field. The only way it works now is by setting the exact value to be evaluated to NONE. So, for example, if we are setting the NONE special value of a three-character long and a five-character long text fields to have <NULL> bytes instead of the default spaces and want those values to be evaluated to NONE, we have to set the NONE Special Value of the first field to "<NULL><NULL><NULL>" and the second to "<NULL><NULL><NULL><NULL><NULL>". There doesn't seem to be a way to just say that we want the default NONE byte of this field to be "<NULL>" instead of the default "<SP>" for text fields or zero for numeric fields. Of course this example is a simple one, but in our case we have over 1000 fields that range from 5 characters to over 500 characters, so setting the exact absolute value of all those fields doesn't make sense and will make the type tree extremely hard to maintain in case the copybook needed to be reimported, which happens twice a year anyways in this project.
Note: This needs to be applied without changing the padding characters. So for text fields, for example, the padding character to still be <SP>, or whatever character it is, and zero for numeric fields, and so on.
What is your industry?
How will this idea be used?
Since setting the NONE Special Value of every single field in the type tree is hard to maintain, especially with the constantly changing schema, having this option to set the byte used for NONE Special Value instead of entering the full value will enable using the NONE property for our solution. As a result, we will be able to distinguish between NULL fields and blank fields (fields that are all blank, but shouldn't be dealt with as NULL. For example, a five-byte numeric field named "count" having value 00000 as should be a valid value and should be different from a null value, where we will get 5 <NULL> bytes)
Do not place IBM confidential, company confidential, or personal information into any field.