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.
extended ESQL/C login structure for solving password length problem
In an application using ESQL/C authentication with instance users, a user can change his password by using sql with a passwort length greater than the 18 character limit imposed by the struct InetLogin (see case TS003855467). After the change of password, the user cannot login anymore since the structure is too small to contain his new password.
Current Possible Workarounds:
Intruct users to avoid passwords longer than 18 characters (ugly and not really recommended, but currently the only viable solution).
Switch to an ODBC Database Connection.
Provide a "renovated" structure InetLoginExtended or InetLogin2 with a deliberate design, which avoids the limitations.
Do not place IBM confidential, company confidential, or personal information into any field.