Skip to Main Content
Cloud Platform

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

Start by posting 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 offering manager 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 a 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Delivered
Created by Guest
Created on Feb 10, 2020

Switching off test logs to avoid overload of results database


We are having multiple tests in a project to test our application and since our application is also running on multiple Infrastructure, we have requirement to run tests multiple times.

We notice that our results DB always gets full because of multiple executions and there is no way, we can switch off test level logs not to be written to database. We can do this only at the project level.

Idea priority Urgent
RFE ID 140047
RFE Product Rational Test Workbench
  • Guest
    Feb 4, 2022

    From version 10.2.2 a new configuration option within test suites is available to control the verbosity of logging, this can also be over-ridden on the command line for use in CI/CD pipelines.

  • Guest
    Jun 7, 2021


    The request is to provide an option to turn off test logging to result database like stubs.

  • Guest
    May 25, 2021

    In order for us to correctly understand your requirements would it be possible for you to answer the following questions:
    1. You are asking to be able to turn off results database logging for some Test Suites in a project but not others, is this a setting that you expect to see on the test suite itself?
    2. Alternatively, is this a mode of execution to be selected at the point where the test is launched, either as an option when running or as a preference within the tool?
    3. Do you need this to be available from other places such as the command line when using RunTests?

  • Guest
    Feb 13, 2020

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Feb 11, 2020

    We also struggle with maintenance of our results DB.
    Our current approach is to wait for it to fill up and everything comes crashing to a halt, then we remove EVERYTHING, so we have no log of recent results data and go again. We're lucky that we got allocated some significant disk space to extend our Tablespaces onto, so this tends to happen about once every 5 or 6 weeks.

    Housekeeping routines using IntegrationTester.cmd (or .exe or whatever) do not seem to work.