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
Need additional ways to route jobs into subsystems other than User ID and IP address via SET_SERVER_SBS_ROUTING
We are using a WebSphere application that accesses the IBM i using DB2 UDB for iSeries (Toolbox). By default, this runs jobs on the IBM i under the QUSRWRK subsystem. We need to configure the system so that all the QZDASOINIT (or QZDASSINIT) jobs for our application are submitted to their own subsystem/memory pool.
The SET_SERVER_SBS_ROUTING procedure will allow you to do this based on user ID and/or IP address. Our problem is that the same user on the same IP address may be running other applications and we do not want to have these routed to our applications subsystem. We are trying to separate our application from other unknown applications that the user may run.
I thought there might be a way to specify something in custom properties on the data source level (JDBC providers > DB2 UDB for iSeries (Toolbox) > Data sources > ITMUIDB > Custom properties), but it seems there is nothing that will use any custom property to do what we need.
Another way might be to use the Special Registers as mentioned in this article: https://techchannel.com/Trends/02/2019/client-special-registers
Neither of these options may work, just my thoughts. Any way that we can cause a request from our application to be routed to a specific subsystem would be helpful. It doesn't have to be done using the SET_SERVER_SBS_ROUTING procedure.
Do not place IBM confidential, company confidential, or personal information into any field.