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 Under review
Workspace Db2 for z/OS
Created by Guest
Created on May 24, 2022

DB2 message showing a trace was started

Today we have situations where people authorized to start DB2 traces sometimes issue START TRACE commands with little qualifications with lead to traces being collected for lots of DB2 threads which ends having impact on general performance of the subsystem.

Example: START TRACE having as QUALIFICATION only plan DISTSERV, which conducts to all distributed threads running on that subsystem collectind trace.

We have a internal code developed to regularly check, analyzing the output of DIS TRACE DETAIL command, if these kind of traces are started. If these scenario is found, a STO TRACE command is issued.

But as DB2 does not issue messages to MSTR and/or SYSLOG stating that a trace ws started, we have to periodically (example: each 5 minutes) issue DIS TRACE commands.

In this Idea we ask to be possible knows when a DB2 trace is started, sending a message do MSTR and or SYSLOG when this occurs. If the message could show the complete START TRACE command issued, it woud be better, so we wouldn't need to issue a DIS TRACE DETAIL to get details. But at least a message stating that a trace was started.

Needed By Not sure -- Just thought it was cool