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
Created by Guest
Created on Nov 10, 2023

Add an API or similar option to an existing API to get all messages for a specified Job

Today if you need all messages for an ACTIVE Job you have the Joblog Message APIs, and if you extract the Exception Message Queue for the job you also have that msg queue. But in the context of a Scheduled Job that runs and has finished processing, and you need to retrieve a list of all the messages and various messages Queue to which that job sent messages, you have to list all the messages in the world and then filter then manually by that completed job's identity. 

It would be nice to be able to query the message queue by Job name/identity. For example, I want all the messages in QSYSOPR that job 005638/BOB/MONTHEND generated, even though that job has ended. Next I need all the messages in any MSGQ that was associated with that same job. Today, you can't really do that without, as I suggested, dumping all the messages in all the messages queues and then filtering by the SENDER_JOB identity. 

If this is more trouble than it is worth, then so be it, but it would be very helpful to scan the scheduled jobs and determine what messages were associated with them... the job log messages aren't available via API once the job has completed so that doesn't offer a viable solution in this context.

Idea priority Low
  • Guest
    Jan 4, 2024
    Thank you for submitting your Idea to IBM. It is not likely that this request will be implemented due to existing alternatives and it having lower priority than other work items.

    IBM Power Systems development
    1 reply
  • Guest
    Dec 12, 2023

    You can have the joblog for a completed job, if you make the job run with LOGOUTPUT(*PND).

    Then you can use the QSYS2.JOBLOG_INFO table function or the message API's on the job and get all the messages in the joblog.

  • Guest
    Nov 22, 2023

    Can't you use the SQL service QSYS2.MESSAGE_QUEUE_INFO to accomplish this?
    select * from QSYS2.MESSAGE_QUEUE_INFO where FROM_JOB = '<job_number>/<Job_User>/<Job_Name>';


    2 replies