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 Feb 27, 2022

Obscure the RUNSQL and RUNSQLSTM Workfile names in QTEMP

When using RUNSQLSTM in CL, a source file is created in QTEMP with the name QSQLSRC.
Users with QTEMP on their library lists now have a "magically appeared" file on their library list that may cause corruption of tasks that previously ran normally.
This request is to use an obscured source file name in QTEMP if need by IBM i provided commands OR clean them up once the command completes OR provide a parameter with a default that can be changed by the customer that deletes said files from QTEMP once the command completes.

Use Case:

As mentioned, If using SQL and storing SQL in QSQLSRC then using RUNSQLSTM on one file with SRCFILE(*LIBL/QSQLSRC) MBR(PICKLES).
You run RUNSQSTM it processings the member named PICKLES and in doing so, creates a source named QSQLSRC in the QTEMP library WITH a member named PICKLES.
If that source member is needed again for other purposes in that same jobstream, the SRCFILE(*LIBL/QSQLSRC) MBR(PICKLES) will select the QTEMP version instead of the one that was first on the library list, causing a failure of the process.

Idea priority High
  • Guest
    Mar 21, 2022

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

    Reworking the file names that are used for creating SQL routines is not a simple task. The file names are recognized and relied upon by IBM i code and by some third party and customer applications. These files in QTEMP have been used since V4R2 (25 years ago) when SQL procedures were introduced and this is the first time anyone on the database team has heard this concern.

  • Guest
    Mar 17, 2022

    I think maybe whomever is "CAAC" needs to re-read this request. I have no idea how someone could think that providing a CL Command Generated Name in QTEMP named QSQLSRC and a request asking that it be obscured would impact "many processes that write to QTEMP".

    How about IBM create a file named QRPGLESRC in QTEMP whenever you compile an RPG program? Would that cause you any issues? That is effectively what happens when using RUNSQLSTM in a CL program or interactively. A new QSQLSRC is generated in QTEMP and left behind when the RUNSQLSTM ends. So in that respect, yes, whomever owns the RUNSQLSTM neeeds to do proper clean up, but they do not.

  • Guest
    Mar 15, 2022

    The CAAC has reviewed this requirement and recommends that IBM not implement this request. The developer needs to do his/her own clean-up in QTEMP. This sounds like it would change many processes that write to QTEMP.

    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

    Nancy Uthke-Schmucki - CAAC Program Manager