Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Created by Guest
Created on Jul 17, 2018

Establish a BigIntegrate process to clean up scratch and orphan pids on job failure

We are running BigIntegrate 11.5.2 in a 700+ node Hadoop cluster. We are seeing situations when jobs fail that are leaving behind scratch in our scratch space and orphan OSH pids. Two scenarios include:

BI job aborts on its own due to Environment issue, Data issue
BI process manually killed using Director client or KILL -15

We would like to request a process be developed outside of the normal BigIntegrate job process that can be trigger by BI when these two events occur. In this manner control of cleanup is still under BigIntegrate versus a cleanup script that needs to be run after the job aborts and leaves processing/scratch behind.

We suspect this problem is being experienced by other customers as well, and would be a beneficial addition to the overall BigIntegrate product.