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 to customize minimum password length in IIAS-DB2 login
Today we have a restriction of minimum character length (12) on passwords for users in the IIAS's DB2 database. We know that we should encourage for increasing this limit, however, if we consider in the ecosystem of the applications of a banking s...
For IIAS environment, we need to manually clear out indoubt transactions for each and every partitions irrespective of number of indoubt transactions found.
To Clean indoubt transactions we need go interactive mode by listing indoubt transaction...
After insert on capture side on table with autonumber column, data is inserted, but sequence is not replicated on apply side.
You can follow the following steps to recreate the scenario.
CREATE LARGE TABLESPACE "TSD_DBA_TEST" IN DATABASE PARTITI...
We have an audit requirement to revoke Database and Platform user's access if they are inactive (hasn't been used) for 90 days.To satisfy above condition, we need to identify who has access to Platform and Database revoke if inactive for 90 days.
Netezza has RunAway query event. RunAway query event sends emails and traps to defined distribution lists and configured SNMP receivers. We have different QUERYTIMEOUT and aggregation setup for different servers in Netezza.
I observed that granting a role to user which is not available in AD /IIAS is also working. If a user is not available in AD/IIAS, then it should error out. If not, how will automation know if we are granting it to real user or not?
List of users...
Do not place IBM confidential, company confidential, or personal information into any field.