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 Not under consideration
Workspace DataStage
Created by Guest
Created on Aug 2, 2016

Installer to identify active DataStage processes

While installing patch on DataStage it took 5hrs to complete the installation .
After debugging it is found out that there are active processes hung the patch installation .
As part of patch installation we set maintenance mode ON .

During installing DSEngine/Services will be restarted which should kill all active process or any open DataStage session . Somehow this process was cleaned up correctly .

"WSVR0606W: Thread "ORB.thread.pool : 4" (00006e03) was previously reported to be hung but has completed. It was active for approximately 1107705 milliseconds. There is/are 0 thread(s) in total in the server that still may be hung."

It will be good to have installer inform user all the active processes which could hung the install process .so that user can kill / clear those active process or installer clear active processes before start installing the patch since it is ran as super user.