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 Db2 for i
Created by Guest
Created on Jan 27, 2023

Improve tracking of what job is the client job for QSQSRVR jobs with ability to review over time

Today, a CPF9898 message is logged to the QSQSRVR job log with the server mode connecting job information. This is useful while the client is actively using the job, but it is insufficient to assess the overall workload on QSQSRVR jobs by the various different clients that may be using server mode connections. 

With ODBC and JDBC, a CPIAD09 message is logged to the history log, and QSYS2.history_log_info can be used to summarize information about the connections - such as number of connections by current user and rates over time.  This same exercise cannot be done today for QSQSRVR jobs. 

While Collection Services includes the current user, this is not always captured and the prestart job could be used many times within a single CS interval. So while the Collection Services data can provide some insights into the clients using SQL server mode, it is not sufficiently robust to do a thorough assessment to provide recommendations. 

This is important information as it can build a case for clients on why they should be using subsystems to isolate different applications. Today, it can take quite a bit of study to quantify the workload driven in QSQSRVR jobs. 

For an example, see this article:

Idea priority Medium
  • Guest
    Feb 24, 2023
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it.

    Db2 for i development team
    IBM Power Systems Development