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.
Continue to Support Datastage DB2 Connector for DB2 for i v7.3+
Currently the InfoSphere Information Server 11.5 Datastage DB2 Connector doesn't support a supported version of DB2 for i.
Also include support for Surrogate Key Generator Stage for DB2 supports DB2 for i v7.3+
Business Impact for IBM: If DB2 for i v7.3 connectivity is forced to use ODBC connector (vs DB2 connector), that opens a easier migration path to other DBMS'. If we are able to use the DB2 connector for DB2 for i, we wouldn't have to change datastage jobs if we wanted to switch to the Db2 LUW common SQL engine.
The Surrogate key stage depends on Connecting with DB2 connect to DB2 for i if database sequence types are used.
so the base DB2 LUW product that connects to DB2 for i under the covers for info server DB2 connector stage supports connecting to DB2 for i.. and the next version of DB2 LUW 11.1 too. So why would info server not continue to support the use of the DB2 connector with the remote DB2 for i database cataloged with DB2 LUW? Especially with the Common SQL engine strategic direction.
This case I still have open TS000795643 where the update a row with a db2 connector doesn't work after an IBM i upgrade from 7.1 to 7.3 where it works with another IBM DB2 for i that was upgraded from 7.2 to 7.3.
Do not place IBM confidential, company confidential, or personal information into any field.