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 Core OS
Created by Guest
Created on Jun 19, 2019

Provide a Real Retrieve Identity of Last SPOOLED File API

The QSPRILSP API was useful to retrieve the last spool file created in a job. Today, however, it has been compromised and returns the last spooled file in the thread in which the API runs, not the last SPOOLED file for the job for which it was originally intended. For example, if no SPOOLED file is created in the current thread but one was created in the main job/thread, the QSPRILSP returns nothing.
Please provide a new API that does what we want, returns the LAST SPOOLED FILE for the JOB, regardless of the thread in which the API is run or the thread in which the SPOOLED file is created.

Use Case:

Using SQL we created a UDTF to return the information from the QSPRILSP API. However, since SQL is multi-threaded, and UDTF nearly always run in their own thread, the UDTF always returns nothing.

Idea priority Medium
  • Guest
    Oct 1, 2020

    The QSPRILSP API returns the last spooled file created in the thread the API is called in. But when you put it in a UDTF, SQL may call it from a secondary thread. The last spooled file is stored in the thread, not the job. It would be problematic for the API to search the thread control blocks for all threads in the job, some of which may have already ended, and the performance would be impacted. For these reasons we are not planning to implement this change.

  • Guest
    Jun 24, 2020

    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 - Core OS
    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 - Application Development
    Operating system - IBM i
    Source - None