Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Not under consideration
Created by Guest
Created on Mar 18, 2016

Maintaining connections with zOS DB2

This is really for DataStage but this interface prevents that selection.

Various teams are struggling with maintaining connections with zOS DB2. The most pressing is when using the bulk loader option in the DB2 connector stage. The bulk loader builds the load file then sends the file via FTP. This process time for large loads exceeds the DB2 idle thread timeout setting established as a reasonable wait by the mainframe DB2 team. The connection to DB2 is also dropped if front end processing in the job exceeds the timeout, All connections are of course established when the job begins.

Using the Keep Conductor Connection Alive = no as recommended in the DB2 connector stage does not sustain the connection. The mainframe timeout can not be prevented by DataStage.

Adding to this connection issue, there doesn't seem to be any handshake between mainframe and unix execution so that debugging log data can be traced to see where the connection is being dropped or why. The mainframe DB2 team has no processing logs to help.

Simply increasing the timeout setting for the mainframe DB2 instance isn't practical due to BI reporting against the same data. The timeout setting is appropriate for that purpose.