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 diagnostics when routing work by user profile with allow_rollover set to NO and the subsystem is not active
When routing work by user profile with QSYS2.SET_SERVER_SBS_ROUTING, the allow_rollover parameter dictates the behavior if the target subsystem is not active. I always recommend allow_rollover to be NO in a production environment as that allows ending the subsystems to keep users off the machine at certain timeframes. Also, the performance and management of BCI jobs in the default subsystem is less than desirable behavior in a production environment.
However, if the target subsystem is not active, it can be quite an exercise to determine this is the problem! There are no diagnostic messages that the routing to the target subsystem failed. On 7.4 and earlier, you just see one CPIAD09 message instead of two.
In addition, if you look at the prestart job statistics, the number rejected is zero, for both the QZDASOINIT jobs in QUSRWRK and in the target subsystem. Again, no clues that connections were rejected.
This Idea is to request diagnostic information logged indicating that a connection is rejected when the target subsystem is not active.
Do not place IBM confidential, company confidential, or personal information into any field.