Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Aug 10, 2022

DB2 profiles - register START PROFILE and STOP PROFILE commands

Summary: Log all -START PROFILE and -STOP PROFILE commands in a DB2 table, ready to be used for queries onto the history tables.


When DB2 profiles are being enabled (SYSIBM.DSN_PROFILE_TABLE.PROFILE_ENABLED='Y'), the next -START PROFILE command will activate those profiles and add, for every enabled profile, a row to the SYSIBM.DSN_PROFILE%HISTORY tables. A -DISPLAY PROFILE command returns message DSNT753I with a timestamp that indicates when the most recent -START PROFILE command has ended.

Therefore, to query the history tables, we have to subtract some seconds from the given timestamp and use the resulting timestamp as input to a query. The processing looks something like

  1. Issue -DISPLAY PROFILE (per DB2 member)

  2. Copy/note the timestamp value(s)

  3. Subtract some seconds from the timestamp(s)

  4. Specify the timestamp value(s) in the query

  5. Run the query

When PROFILE_ENABLED='N' is specified for all profiles, a subsequent -START PROFILE command will not activate any profile, and no history rows are created. The -DISPLAY PROFILE command returns the timestamp of that most recent start command.

This enables queries for the "current time".

However, there are situations were we need to know whether profiles were activated, or not, respectively, on a specific day and at a specific time. The missing historic timestamps of all past -START and -STOP PROFILE commands make it impossible to query for a specific time.

  • If all -START/-STOP PROFILE timestamps (per group member) would be available (preferably in a DB2 table), such queries would be enabled by joining the log table with the history table.

  • Also, the current way to get those timestamps for the "current time" (-DISPLAY PROFILE, get the timestamp, subtract some seconds, use the result in the query) would be made much easier.

Needed By Yesterday (Let's go already!)
  • Guest
    Aug 10, 2022

    This is a very good Idea, because the Implementation right now is just a half solution and

    not really helpful. The Idea of profiles is good.