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 May 18, 2023

Allow stored procedures created as *PGM objects to be called as exit point programs

When using the CREATE PROCEDURE SQL statement to create a *PGM Object it is NOT possible to call the generated object outside of SQL; doing so results in an error reporting "Pointer not set". Looking at the code generated as an intermediary step in the CREATE PROCEDURE process, an extra parameter is passed to the *PGM object. 

When using the *PGM object as an exit point program; which you can specify without any error being raised, you do not have the option to control the parameters passed to the exit point program. These are defined by IBM. In our case we were using the exit point associated with the DLTJRNRCV command so that we could prevent the deletion of a journal receiver that our software was processing entries from. 

Idea priority Urgent
  • Guest
    May 31, 2023
    The documentation about the CL CALL statement not working with SQL procedures is on this page:

    Db2 for i development
    IBM Power Systems Development
  • Guest
    May 30, 2023
    IBM does not intend to provide a solution to this Idea at this time, so it is being closed.

    SQL procedures are intended to be called within an SQL environment, handling input parameters and returning errors in an SQL-defined way. IBM does not plan to modify the design of SQL procedures to make them run cleanly with the CL CALL command.

    To share logic, you can embed a call to the SQL procedure from within a native language exit program. This can be done using embedded SQL or the RUNSQL CL command.

    Db2 for i development
    IBM Power Systems Development
    1 reply
  • Admin
    Maria del Carmen Ruvalcaba Cevallos
    May 30, 2023

    The CAAC has reviewed this IBM Idea and recommends that IBM not implement this request.

    It is a narrow application without much benefit to the Community.

    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 IBM Ideas on the broader IBM i community and has therefore reviewed your Idea.

    For more information about CAAC, see

    Carmelita Ruvalcaba - CAAC Program Manager