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.
Add a way to pre-encrypt db2 user password before adding it in response file to do db2 silent install.
We are OEM customer to provider our user Db2+Cognos installation, we're using db2 silent install with a response file, for now, there is no way (no tools, no command) to encrypt a plain db2 user password so that we can add this encrypted password in the db2 response file to do the silent install.
We have to provide a plain password in the db2 response file, it's not secure and right to put a plain password in the file.
According to IBM support, the only way we can encrypt db2 user password is by running the setup wizard and generate a response file with encrypted password. But we can't do that, because we're providing our customer a response file to silently install Db2, they shouldn't run setup wizard to generate the response file by themselves.
Do not place IBM confidential, company confidential, or personal information into any field.