Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Under review
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: 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.

Idea priority Medium
  • 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.

    Dawn