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 Delivered
Workspace IBM i
Categories System Management
Created by Guest
Created on Feb 3, 2021

Service for Journal Receiver Attributes

Create a service that would allow us to easily see the Journal Receiver Attributes for all currently attached journal receivers. We are looking to determine if any are near the Last Sequence Number threshold.

Use Case:

A journal receiver reaches the maximum number of entries and all activity comes to a halt.
Super simple fix: CHGJRN JRN(LIB/currentattachedreceiver) JRNRCV(*GEN) SEQOPT(*RESET)
Here's the hard part – Is any other journal in or near this state? Let's prevent this issue!
wrkjrn *all/*all
There's a whole list of journals.
wrkjrna LIB/journal – F17 to display the attached receiver
Do I need to reset it - yes or no - move on to the next journal.
Rinse and Repeat - for every journal on your system and then every journal you have on every other system.

An alternative would be this command, but then you have to know the name of the receiver. DSPJRNRCVA lib/receivername . I guess you could do this command – wrkjrnrcv *all/*all and check the highest numbered journal for each name pattern.
Wouldn't it be cool if we had a service that could determine the last receiver on all the journals and then show us the attributes so we could determine if anything needs a fix-a-roo?

We could write a program - but a service would be more fun.

Thanks for your consideration and have a great day!

Idea priority Low
  • Guest
    May 5, 2022
    IBM believes that the request described has been solved and is available with IBM i 7.5, and with DB PTF Groups IBM i 7.4 SF99704 Level 20 and IBM i 7.3 SF99703 Level 28.

    A new view, QSYS2.JOURNAL_RECEIVER_INFO has been provided to return journal receiver attributes.

    For a description of this change, see
  • Guest
    Mar 12, 2021

    IBM understands this request and will consider this request as part of our future planning. No commitments are to be implied.

  • Guest
    Feb 17, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a “nice to have” LOW priority feature.

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial 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.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ and the article "The Five Hottest IBM i RFEs Of The Quarter" at

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Feb 4, 2021

    You can keep track of this with the QSYS2.SYSLIMITS view: