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 25, 2021

Change all SQL Interfaces (RUNSQLSTM, RUNSQL, STRSQL, etc) to NOT generate QSQLSRC in QTEMP

When "compiling" an SQL Procedure, Function, Variable or sequence the system (RUNSQLSTM) generates 2 work files as outlined in
The 2nd file name is QSQL00001 (or similar) while the 1st file name is QSQLSRC. The problem is the first file name can cause conflicts and errors (with library list use, etc) when finding members in jobs where such functions were created. The request is to generate QSQL00001 and QSQL00002 or similar file names in QTEMP or similar instead of the commonly used QSQLSRC file.

Use Case:

In a user's job, we generated something a function or sequence that is "compiled" using RUNSQLSTM. Then the next step is to run an SQL statement from QSQLSRC which exists in the User's library list. However, if QTEMP appears on the library list before that User Library then the routine may try to access the file in QTEMP instead of the one that was on the user's library.

Idea priority Medium
  • Guest
    May 12, 2021

    "It is unfortunate that you are using a Q prefixed file..."
    100% of IBM i shops use source files that being with the letter Q.
    This was the same justification IBM gave us for creating a RUNSQL command name which 90% of IBM i shops already had installed from a 3rd-party or themselves, causing a decade of issues/challenges for customers. (The RUNSQLSTM should have had a new parm added to it, but I digress.)
    I would speculate the use of SQL, specifically RUNSQLSTM has increased in recent years and is now showing some challenges with the implementation or design choices. I would request that it be re-investigated and realize how easy it would be to use "generated" names not only for the 2nd source file you already create, but for the first one too. Thank you.

  • Guest
    May 8, 2021

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

    The names IBM selected for the source files and members when creating SQL procedures and functions was done intentionally and was part of the original design for SQL procedures back in V4R2. QSQLSRC was selected as a name intended for our SQL use and started with a Q, making it an IBM-named file. It is unfortunate that you are using a Q prefixed file that collides with our name. We do not plan to change our processing since we do not know where dependencies might have been established on these names in the last 25 years.

  • Guest
    Apr 8, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Db2 for i
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None