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 (

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 ( - 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.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Feb 12, 2024

Adjust the functionality of AUDIT_JOURNAL_* table functions

I think the current behavior is quite confusing.  For example, if I'm trying to retrieve the QAUDJRN "PW" entries from a specific receiver, I might try this:

                                      STARTING_RECEIVER_NAME    => 'Q9B6300332', 
                                      ENDING_RECEIVER_LIBRARY   => 'QSYS', 
                                      ENDING_RECEIVER_NAME      => 'Q9B6300332') );


But due to the default value of STARTING_TIMESTAMP (which is "CURRENT DATE - 1 DAY") I will get no results back if this journal receiver is a few days old.  I think if I'm specifying a particular starting receiver, I should get all of the PW entries starting with that receiver.  It's very misleading to get back zero results.  It makes it seem like there were no PW entries in that receiver.

The DSPJRN command doesn't make such assumptions about the start date/time.  That's probably why the behavior of the SQL table function throws me off.

Idea priority Low
  • Guest
    Jun 9, 2024
    After further consideration, we are not going to make changes to the audit journal table functions at this time so the request is being closed.

    With 40 table functions that would need to be modified, we do not believe the cost of implementing a change would have an adequate benefit to the community.

    Db2 for i development team
    IBM Power Systems Development
  • Guest
    Mar 8, 2024

    Ok thanks. Maybe a new parameter that overrides the default behavior? I know that changing the current default behavior could introduce issues for other users, who have already built tools based on the current behavior of the functions.

  • Guest
    Feb 27, 2024
    We understand your point that the values provided by the input parameters allow for some misunderstanding of the user's intent. However, we will not consider changing the existing behavior since we believe modifying the user's input parameter values, whether explicitly provided or using the defaults, can lead to more confusion.

    We will investigate what it would take to issue an SQL warning for the situation you describe. We realize that most users ignore warnings, so this solution might not be helpful. The cost of modifying almost 40 existing functions to issue a warning is also a consideration when it comes to prioritizing this Idea request.

    Any comments from the community about our proposed solution while we continue our investigation would be appreciated.

    Db2 for i development team
    IBM Power Systems Development
  • Guest
    Feb 13, 2024

    Try this, hopefully using the *CURCHAIN value with time offset will help you

    Steve Bradshaw,
    Member of CEAC, TD of & Friendly Techie at

    SELECT journal_code, journal_entry_type, object, object_type, X.*



    'QSYS', 'QAUDJRN', -- Journal library and name
    STARTING_RECEIVER_NAME =>'*CURAVLCHN', -- Start from first receiver in the current chain
    JOURNAL_ENTRY_TYPES =>'PW' , -- Journal entry types
    STARTING_TIMESTAMP =>CURRENT TIMESTAMP - 24HOURS-- Time period, this can be Minutes, Hours, Days, Months
    ) ) AS x ;