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.
Teradata connector restricts max Response Row size to 64K bytes only
We have data sources where column field lengths are in excess of varchar(3000), using the teradata connector with immediate mode, job fails with error "RDBMS code 9990: Response Row size exceeds 64K bytes and is incompatible with the Client softwa...
We would like to connect an Amazon S3 connector to crawl our MFA-enabled S3 instance to pull in data to use in the Watson CP4D environment, but the current Amazon S3 connector does not support connecting to MFA-enabled environments.
Redshift connector slow in IIS DataStage for Insert/Update
We have a use case in which we need to process records from IIS DataStage into an aws Redshift instance. When using the stage as currently implemented, we're seeing a throughput that averages 2-6 records a second which is far below the acceptable ...
DataStage Designer - Fields for Siebel Business Objects or Components returning wrong values
This issues has been experienced on both InfoSphere Information Server 11.5 and 126.96.36.199. After submitting an IBM PMR to try to resolve the issues the final response from IBM Support was: Our Engineering team reviewed the issue and have advised th...
We are using Information Server 11.7.1 and have multiple ETL jobs that use SAS connectors to execute SAS code from the ETL server ( SAS 9.4 M3 ). However the SAS version has now been upgraded to SAS 9.4 M6 and the connectivity via the provided con...
As we've been migrating from Netezza to DB2 (with the support of IBM) - It's been noticed (by IBM) that the LZ4 Compression Option is not available in the DB2 Connector. Tests performed via the DB2 Command Line (on the Datastage server) show signi...
over 1 year ago
Functionality already exists
Teradate connector did not record the events by END TRANSACTION
Teradate connector did not record the events by END TRANSACTION in a job log. In normal cases, job log shows events as follows(1) BEGIN TRANSACTION(2) SQL STATEMENT (insert ..., for example)(3) The count of processing records is NNNNN(4) END TRANS...
Do not place IBM confidential, company confidential, or personal information into any field.