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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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: https://www.seidengroup.com/2022/05/04/simplify-with-subsystems/
Do not place IBM confidential, company confidential, or personal information into any field.