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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Mar 21, 2022

Full EXPLAIN support for all types of trigger

With Triggers you cannot use the REBIND option OWNER on a rebind. Why not? Not even for EXPLAIN(ONLY). We must get the ability, like with "normal" packages, to EXPLAIN into another set of EXPLAIN tables.

Further, if you are using Advanced Triggers EXPLAIN(ONLY) is not allowed at all! Thus making the advanced triggers slightly less advanced than basic triggers where you can use that syntax.

Bottom line: Bring EXPLAIN(ONLY) and REBIND options for all static packages to the same level

Needed By Quarter
  • Admin
    Janet Figone
    Apr 15, 2022

    Dear Roy, The Db2 for z/OS team would like you to please be aware of the following correction:

    The PACKAGE OWNER option is not allowed on the ALTER TRIGGER SQL statement either. This is because there is no EXECUTE privilege check when trigger is fired. So the trigger's owner and trigger package's owner must be the same to avoid a security issue. Another reason is to conform with other Db2 products in the family where the trigger's owner is not changed by ALTER.


    The Db2 for z/OS team

  • Admin
    Janet Figone
    Apr 14, 2022

    Dear Roy, The Db2 for z/OS development team has reviewed this enhancement request and has the following feedback for you:

    • We are accepting the part of this requirement for EXPLAIN(ONLY) on REBIND advanced trigger package and thus have dispositioned the state to future consideration. We do allow this bind option for native SQL procedure's package so we will be consistent there.

    • However, not all bind options will be allowed. For example, regarding the question about why OWNER can't be changed on REBIND of a trigger package; the reason is that the package is part of the trigger and we follow the native SQL stored procedure paradigm. The clause PACKAGE OWNER can be used on the ALTER TRIGGER statement to change the owner of the package. This is consistent with ALTER PROCEDURE PACKAGE OWNER (and not using REBIND subcommand) for a native SQL procedure's package.

    Thank you,

    The Db2 for z/OS team.