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 Future consideration
Workspace Cognos Analytics
Created by Guest
Created on Feb 5, 2015

Fix CGSLAUNCHER 100% CPU hang issue

When users use charts with fine staggered collision mode in Cognos Workspace on TM1 cubes with many zero values, it hangs and pegs the Cognos servers' CGSLAUNCHER.exe processes at 100%. There's some type of infinite loop that does not allow the process to return. The only thing to do is to reboot the Cognos servers.

Cognos Workspace is the tool to promote self-service analysis and reporting. However, we cannot knowingly promote this tool knowing that a basic usage such as charting of data from our TM1 server could easily bring our Cognos servers to a halt.

Suggestion: Place some type of timeout in chart rendering engine which stops generating a chart if lots of zero value data is encountered or if certain number of minutes have passed in generating the chart. It is better to fail the chart rendering process for a particular chart vs bringing down the whole Cognos server.