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 Mar 8, 2017

Use of unqualified objects in SQL-based triggers

When connecting to db2 on our iSeries we are used to using jt400/jdbc
property naming=system, which enables us to use unqualified objects
like tables, stored procedures and such. This brings great flexibility.
When a trigger containing unqualified objects is deployed, the deploying process checks if the referenced objects can be found in the job's
library list. The deploying process automatically qualifies the unqualified
tables and stored procedures in the final trigger-object and therewith
alters the code I have put in the trigger.

I have attached a pdf to demonstrate my case:

Step 1: deploy trigger
After deploying, request the trigger's SQL source through for example
iSeries navigator. As you can see, the trigger-definition refers to an
unqualified table. The deployment process finds table2 in the deploying
job's library list and adds this qualifier to the update command.
Effect of the trigger: updates on table1 also update some record in

Step 2: copy the table
After copying or restoring the table to another library/environment, request the trigger's SQL source. As you can see, the table qualifier of the table
remains the same and updates are being written to table2 in the
development library, instead of the test library.

Like can be read in IBM's documentation this works as designed.
IMHO IBM does not conform to a principle widely used on the iSeries: library lists. It would be a great enhancement if IBM would also implement this working in (SQL based) triggers.

For example: when developing in a DTAP street the developer creates and alters objects (programs, tables -including triggers-, etc.) in Development level.
Once the developer thinks his or her objects are ready for Test our DTAP-tool copies the objects to the Test environment. However: when tables with triggers are copied we will have to deviate from this procedure and would have to maintain a base of identical trigger-sources for each table for each level of the DTAP street and deploy them, using a library list that contains the right libraries for the level the object is copied to.

Use Case:

- deploy trigger
unqualified objects are checked on existence but are left unqualified.

- save file
- restore file (and trigger)
- when an operation is executed on the file which fires a trigger and the unqualified objects can not be found in the library list, the operation fails.

Idea priority Medium
  • Guest
    Dec 8, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    As you point out, static SQL in a trigger cannot use the library list. IBM will not be changing that behavior. However, when you use dynamic SQL your statement can use the library list to find objects.

  • Guest
    Mar 8, 2017

    This RFE was recorded on behalf of the customer as the original request was mistakenly associated with the RBD product and was then rejected by development ie
    ROCR ID:CQPAR00203678