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
Post 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,
Post an idea
Upvote ideas that matter most to you
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 product management 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 notification 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.
Allow more than one separator character when unloading in delimited format
A competitor's unload tool allowed us to specify more than one character in the separator field when unloading data in delimited format.
We had to use more than one character, because for unloads of certain tables, we couldn't find a character that didn't also appear in the data somewhere.
So using 2 or more characters enabled us to overcome this issue.
We no longer have the competitor's unload tool. When we next have to unload these tables in delimited format using HPU, our workaround will probably be to select a literal of e.g. '###' between each column.
The competitor's manual stated that only one separator character was allowed, but it did accept 4 characters when running the unload!
So we did try using more than one separator character in HPU just in case the manual wasn't accurate as with the competitor's. While more than one character was truncated in the data, more than one character was allowed when specifying TITLE ON. We raised case TS004488740 and IBM has raised APAR PH31907 to correct that mis-match, to bring the number of separator characters in the header in line with what's allowed in the data.
The case recommended raising an AHA idea to allow more than one separator character.
Do not place IBM confidential, company confidential, or personal information into any field.