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 Nov 30, 2017

allow three part names in db2 for i services

please add ability to use three-part naming in UDTF or in db2 for i services like
It seems that the 3-part naming isn't working or supported in UDTFs. .e.g.:!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.JOB_INFO%20UDTF


Use Case:

someone could simply use a central IBM i system to retrieve information from various systems.
like how long did my backup take one system a, system b, system c .. or day-end processing statistics.

Idea priority Medium
  • Guest
    Feb 9, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed. This request has a low priority since there is a work-around.

    To direct a table function to be run on a remote system, add a three-part reference to a table on that system. Here is an example. Replace RMTDB with the system you want to access.

    select current server, h.*
    from table(qsys2.history_log_info()) h
    where exists
    (select 1 from RMTDB.sysibm.sysdummy1);

  • Guest
    Jan 16, 2018

    We haven't yet considered whether or not to provide this enhancement.
    I should point out that there are two alternatives that could be used today:
    1) Create a procedure on the target IBM i's that invokes the UDTF. Call the procedure using 3-part names.
    2) Create a view on the target IBM i's where the view invokes the UDTF. Query the view using 3-part names.
    2b) The view could be parameterized using global variables.
    Regards, Scott

  • Guest
    Jan 16, 2018

    The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature to the general IBM i community. There are alternate ways to do this, though they are a bit involved. The audience for this would be those with multiple systems running the same application stack, and it would be much appreciated by them.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see

    For more details about CAAC's role with RFEs, see

    Dawn May - CAAC Program Manager


3-part names in stored procedures and UDTF

Today 3-parts names are allowed to run SQL select , update and delete - statements to access resources on remote servers. However, 3-parts names are not allowed for stores procedures and user defined table functions. Use Case: Today you can run a ...
almost 6 years ago in IBM i / Db2 for i 4 Not under consideration

Allow three part naming on table functions

I'd like to see the ability to use three part naming on table functions, like RemoteSystem.QSYS2.HISTORY_LOG_INFO Use Case: Retrieving statistics for a system health dashboard.
about 5 years ago in IBM i / Db2 for i 2 Not under consideration