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 Core OS
Created by Guest
Created on Mar 26, 2021

allow for a alternate log for CPIAD09 messages

the CPIAD09 messages from our QZDASOINIT jobs are choking our QHST log, and making it difficult to navigate. Please provide the ability to have these messages go to another message queue.

Use Case:

Browsing the QHST log

Idea priority Medium
  • Guest
    Oct 27, 2021

    Moving this request to Uncommitted Candidate for further investigation.

  • Guest
    May 4, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    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
    Apr 8, 2021

    When testing what I suggested using the DB2 for i Service searching the History Log for a specific message ID on a system with much activity and many CPIAD09 in it. I think the response time of that search also needs to be taken into account when deciding if this is a valid workaround.

    In my test I did search the history log for several days and each day contains around a million records. Searching a lot of data takes time. So what is seen as a workable response time needs to be decided also.

  • Guest
    Apr 7, 2021

    Good suggestion. Moving to under consideration for further investigation.

  • Guest
    Mar 30, 2021

    Is the DB2 for i service for viewing the history not an acceptable alternative?

    The option to omit the message id CPIAD09 from the result set is possible.

    The question is if working with a different approach/user interface can be seen as good alternative or solution?

  • Guest
    Mar 28, 2021

    I agree with this request.
    CPIAD09 messages are very important to understand the incoming work requests, peak workload timeframes, etc., so logging them is required. But having them in the history log is problematic. An alternative log repository for the CPIAD09 (and CPIAD0B for the sign-on server and CPI3E34 for the DDM//DRDA server) message would be very helpful in making the history log more useable. One could also argue that the CPI1124/CPF1164 messages could also be sent to this alternative logging location. Another noisy message is TCP2617.

    Where I'm going with this is that there are a set of messages that can generate a lot of noise in the history log. The ones listed above are the most common, but on some systems, there are additional messages that can clutter up QHST.

    Wouldn't it be nice if the customer could have a way to select which messages should go to the alternative logging location to allow them to keep QHST as clean as they wish?

    It's very convenient that DSPLOG has a parameter for the log.