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 Future consideration
Workspace IBM i
Categories Print
Created by Guest
Created on Jul 1, 2021

Enhance QGYOLSPL or QUSRSPLA to Find Last SPOOLED File

Today with Print Server Jobs, Threads and SQL Server Jobs, the QSPRILSP is all but useless in these environments.
This request is to enhance either the QGYOLSPL or the QUSRSPLA API so they have the ability to retrieve the identity of the Last Created SPOOLED File by search for it using one (or more) of the following:
1) A User Profile
2) A Job
3) A SPOOLED File Name

Use Case:

For some reason:
QSPRILSP doesn't return the last SPOOLED file when it is run in a thread, nor when it is run in an Server Job (print or SQL).
QGYOLSPL doesn't have the ability to specify the SPOOLED file name on the Selection Input parameter.
QUSRSPLA doesn't provide a User Profile-based search, nor a JOB ID of *ANY/*ALL.
Thus nothing today provides the capability of the QSPRILSP from prior Versions of IBM i where threads and Server Jobs were a Future Objective.

A good enough API would be one that allowed me to retrieve the last SPOOLED file created of a given SPOOLED file name (or any), or by the User for this job (or any), or within a Job (or any/all) rather than enhance the other two APIs.

Idea priority High
  • Guest
    Nov 30, 2021

    .IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.

  • Guest
    Nov 30, 2021

    Similar requests were declined because we believed that we would have to walk through the list of job threads to find the last spooled file for all of them. By the time this was accomplished there would be a very good chance that we would not be returning the correct spooled file.
    However, we recently came up with another approach which would allow us to retrieve this information relatively quickly. As such, there would be a much better chance to return the correct one. We will continue to investigate.

  • Guest
    Nov 29, 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 - Print
    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

  • Guest
    Aug 24, 2021

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. It should not be so difficult to do a common operation like this.

    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

  • Guest
    Jul 19, 2021

    Such a common sense requirement, I would have voted 10 times if I could.

  • Guest
    Jul 8, 2021

    How did they help Rudi?
    I read them previously and if you're in ACS Run SQL Scripts, were you able to automate retrieval using an SQL interface? That is/was my goal.
    For now, I've written a "simple" QUSLSPL interface that works for the user or the job (but sadly has no built-in spooled file name option). It solved the immediate issue but I mean... it is interesting times.

  • Guest
    Jul 2, 2021

    Hello Bob,

    We had similar problem with finding a spoolfile run from Run SQL Scipt (RSS) in ACS. We found two IBM KB item which helped solving that.

    -- Retrieving Spooled Files Generated in a Host Server Job
    -- ==>

    -- Finding and Working with Spooled Files Generated under a QPRTJOB Job
    -- ==>

    No idea if they are a solution for you, but I thought it was worth mentioning them. As long as this RFE is not delivered they might help you in the same way as they did me.

    Greetings Rudi


Add a LAST SPOOLED File Created by Job or related Jobs to Job Structure

Add a Job structure that contains a reference to the Last SPOOLED file created by:The JobQPRTJOB server jobs created by the jobThreads spawned by the jobSQL Server Jobs used by the job The provide an API to access that information until the said J...
almost 3 years ago in IBM i / Print 3 Future consideration