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.
DataStage server jobs are failing due to no ODBC connector support to load data into Snowflake database
Currently, we have several DataStage server jobs designed to solve a specific problem and running fine to extract data sourcing from flat files & SQL servers and targeting to Netezza database. Now we are in the process of migrating the on-prem Data Warehouse to the cloud (Azure) Snowflake database and the DataStage server jobs are failing to load data into the snowflake database due to character conversion issues. The target ODBC connector (no snowflake connector available in DataStage server canvas) to load data into the Snowflake is translating data into unreadable (Asian characters) characters and DataStage jobs are failing.
It is not practical for us to convert all of these 100s of server jobs into parallel jobs and it is also a huge risk to the project. So we suggest providing a fix to the character translation with an existing ODBC connector.
Do not place IBM confidential, company confidential, or personal information into any field.