This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 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
Specific links you will want to bookmark for future use
let db2adutl work cross-dbpartition on one LPAR, as it did before
Before DB2 184.108.40.206.1 db2adutl could work on different dbpartitions on the same LPAR. Now it throws an error that input database partition number/current database partition number are different, if DB2NODE is not explicitly set. db2adutl should be able to set DB2NODE on its own / attach to the given dbpartition as long as the parameter DBPARTITIONNUM is given. Current behavior under DB2 220.127.116.11.1 seems to be a bug, more than IBM postulated "works as designed". This buggy "feature" was not documented, too.
Do not place IBM confidential, company confidential, or personal information into any field.