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
Routing Work by User Profile results in two CPIAD09 Message in QHST, both sent from a job in QUSRWRK
When routing work by user profile, using the QSYS2.SET_SERVER_SBS_ROUTING() service, there are two CPIAD09 messages in QHST. The first one is sent from an intermediate job running in QUSRWRK, the second is sent for the job running in the configured subsystem, but the message is sent from the intermediate job in QUSRWRK.
The second message is the most interesting one, since that is the job where the actual work requests run. However, the sender of the message is from the first job. This makes it impossible to search the history log for all the messages from the desired job.
Below is a more detailed description:
My test scenario is I found a job using a lot of CPU in my Collection Services data. CS does have the current user information, but it's much quicker to just do a DSPLOG to find the CPIAD09 message to locate the current user. But a DSPLOG on that job only return the CPF1124 message. This led me down my analysis path to determine what is happening, and the request to correct this situation by submitting this RFE.
I have set up my own subsystem and route my work to my subsystem (DAWNMAY) for all the supported server jobs.
There are now two CPIAD09 messages in QHST:
User DAWNM from client 127.0.0.1 connected to job 991629/QUSER/QZDASOINIT in subsystem QUSRWRK in QSYS on 12/04/18 06:55:30. User DAWNM from client 127.0.0.1 connected to job 924740/QUSER/QZDASOINIT in subsystem DAWNMAY in DAWNM on 12/04/18 06:55:30.
This makes it hard to find the CPIAD09 message in the history log if I am looking for who used job 924740/QUSER/QZDASOINIT.
A DSPLOG JOB(924740/QUSER/QZDASOINIT) does not show me the CPIAD09 messages I need to find.
I.e., CPIAD09 - Message . . . . : User DAWNM from client 127.0.0.1 connected to job 924740/QUSER/QZDASOINIT in subsystem DAWNMAY in DAWNM on 12/04/18 06:55:30.
The Message Details show this message was actually sent from the job running in QUSRWRK subsystem:
Message ID . . . . . . : CPIAD09 Sever Date sent . . . . . . : 12/04/18 Time Message type . . . . . : Information From . . . . . . . . . : DAWNM CCSID
The CPIAD09 message really needs to come from the job handling the work request, not the intermediate job in QUSRWRK.
My request is two changes:
#1. For the intermediate job, use a message other than CPIAD09 to log the fact that it initially handled the work request. Also, the message text should reflect that this was due to the QSYS2.SET_SERVER_SBS_ROUTING() configuration in place.
#2. The CPIAD09 message sent for the job in my configured subsystem should come directly from that job itself, not the prior job.
I am debugging an issue with my prestart server jobs. I want to review all the messages sent from my job. I cannot find the CPIAD09 message because it is sent from a different job.
I am using connection pooling and review the CPIAD09 messages to review the effectiveness of my configuration. I now have 2 CPIAD09 messages which skews the results.
Do not place IBM confidential, company confidential, or personal information into any field.