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 Future consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Oct 24, 2022
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit IBMI-I-2875 add a new audit field to the SQL fields.

Trigger Buffer should include Event Pgm, PgmLib, Procedure, and Statement (boost performance) Merged

Trigger programs should readily know the program, procedure, and statement that triggered them. This information is available by retrieving call stack and ignoring OS call stack entries but looking this up hurts performance (i.e. we want IBM to efficiently tell us which program initiated request). If IBM can include this information in trigger buffer automatically (or optionally) and do it more efficiently than we can via API calls then please by all means hook this up.

TRGBUF+
PGM CHAR(10)
PGMLIB CHAR(10)
PRC CHAR(64) or perhaps 128 but not 4096... (this field is a nice to have)
STM CHAR(10)

We love being able to STRDBG &PGMLIB/&PGM, F15 to select Listing View, and then Find the CSE &STM (inner line number) that triggered the trigger program. Helps us easily solve difficult problems.

We use triggers to capture history on everything we care about or need to troubleshoot. SQL temporal tables appear to be similar concept but lack these critically important fields (and thus we do not use them)(they should support them).

Idea priority Medium
  • Guest
    Reply
    |
    Nov 12, 2022
    Returning this information in the trigger buffer is not simple to implement and would have a performance impact on all triggers. A trigger solution will not be pursued.

    There is an existing enhancement request for new generated columns to return the program information. The is the solution we are considering for implementation. This Idea is being marked as a duplicate of the other request.
    http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=144877

    Db2 for i development
    IBM Power Systems Development