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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Jun 6, 2022

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:

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.

Idea priority Medium
  • Guest
    Sep 7, 2022
    Thank you for submitting your idea to IBM. While we agree it would be nice to have more routing options, trying to retrofit this into our existing routing scheme may be overly complicated and difficult to predict what the expected outcome is with all the possible combinations. Therefore I am declining at this time, but will keep your use case in mind for future reference if this topic resurfaces at a time when we are able to pursue it further.
    IBM Power Systems Development
  • Guest
    Jun 20, 2022
    Moving to Under Consideration for further evaluation.
    IBM Power Systems Development
  • Guest
    Jun 7, 2022

    I have come across this situation in my work with clients. I think the option to run in the same subsystem as the requester may be a good way to approach this request. This would be similar to what you can do with the QSQSRVR jobs today, but extend it to ODBC/JDBC. However, this will only work if the application server is on the same partition as the database server jobs.

    I also like the suggestion mention about using the client special registers as a way to route work. This could provide a lot of flexibility and would add support where the application server is not running on the same partition as the database server jobs.