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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.