Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Delivered
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Apr 12, 2017

Log embedded sql statements

With WRKREGINF/QIBM_QZDA_SQL2 we are able to 'catch' any SQL statement executed via Database Server.
We need a similar technique to catch SQL statements executed through 'EXEC SQL' in RPG programs. Could be (Statement, SQLCOD, ..).
Responsetime included would be perfect even though this is not available with QIBM_QZDA_SQL2


Use Case:

Performance investigations are always expensive to do. To optimize/automate this we collect data from all parts of our application to pin point to where the hotspots are. We need to connect the sql statement to the module/procedure where it is executed.
We can then automatically monitor changes in responsetime and point to the right spot and much more...


Idea priority Medium
  • Guest
    Reply
    |
    May 13, 2021

    This enhancement was delivered in spring 2021 with IBM i 7.4 PTF Group level 13 and IBM i 7.3 PTF Group level 24.

    The Query Supervisor is now available for 7.4 and 7.3.

  • Guest
    Reply
    |
    Apr 24, 2021

    On April 13, IBM announced a new database monitoring feature called the Query Supervisor which should help answer many of the questions you might have about a query that is actively running. This will be released as part of the IBM i 7.4 DB PTF Group 13 and IBM i 7.3 DB PTF Group 24 in May.

    This wiki page contains links to more information about this enhancement: https://www.ibm.com/support/pages/node/6442049

  • Guest
    Reply
    |
    Mar 21, 2018

    If the intent is to catch long running SQL statements, you can already use the governors and database monitors and plan cache to satisfy this requirement.
    If the intent is to monitor for access to a specific table or tables, use of the database open exit point would be a good solution.
    If the intent is more for real time auditing, exit points are not a very good solution because there are MANY interfaces into SQL besides embedded SQL and host server access. Instead you might consider using a database monitor and an instead of trigger over a view. For more information see: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/STRDBMON%20Over%20a%20View%20%28Enables%20faster%20SQL%20statement%20auditing%29

  • Guest
    Reply
    |
    Apr 18, 2017

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - DB2 for i
    Operating system - IBM i
    Source - ISV (Independent Software Vendor)

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Languages - RPG
    Operating system - IBM i
    Source - ISV (Independent Software Vendor)