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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.