This portal is to open public enhancement requests against products and services offered by the IBM Data & AI 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,
Post an idea
Upvote ideas that matter most to you
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
See this idea on ideas.ibm.com
Especially at the beginning of a month our customers execute masses of reports at once. The queue within Cognos is huge.
Most of the reports run fast, but there are also many reports that run longer (> 30 min. and runtime is even longer in this high utilization scenario). We then run into a situation where all batch report server processes are in use for a longer time, so the next report in the queue must wait until a long running report has been finished executing. The queue is getting longer and longer then.
The idea would be to be able to configure maximum time a report can use the batch report server process (e.g. 30 min.) in a high utilization scenario. After expiration of this time, the report execution is being paused (or even killed) and put back to the start of the queue. This should happen without the user being aware of it.
The maximum time as outlined above, should not be applied, when batch report server processes are available. Then the property "Maximum execution time for the batch report service (seconds)" is relevant.
Another idea would be to prioritize report executions in a high utilization scenario according to their run history. Fast reports should be first, slow reports last.
The above would help us that 90% of the reports will finish earlier in a high utilization scenario and only 10% will run (much) longer than today.
Needed By | Yesterday (Let's go already!) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.