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 Not under consideration
Workspace IBM i
Created by Guest
Created on Jun 16, 2021

Block QZDASOINIT started as BCI job in QSERVER enhancement

Prevent database prestart jobs to start as BCI jobs is also ending the jobs rerouted to other subsystems when we use the solutions provided by the Doc.: #638059 historical #391825917


Use Case:

Client has split his service jobs over different subsystems for load and application purposes.
By default all connections are served by QUSRWRK. When we end this subsystem, the QZDASRVSD deamon is starting a new BCI job in QSERVER so defeating the purpose of ending the QUSRWRK subsystem.
Ending the host server*DATABASE, as solution B proposed in the doc is not a solution as this ends all service jobs,in all subsystems.
Implementing the solution A, provided by the Doc. results in also no longer serving the jobs in the other subsystems.
It seems that the deamon job is no longer looking further at the re-routing configuration to serve the other database jobs.


Idea priority High
  • Guest
    Nov 22, 2021

    Thank you for submitting your request. I agree this would be most useful. However, after thinking about this some more, I keep circling back to the limitation that we do not know the user profile name at the time the first request is put to the server (running in QUSRWRK, in this case). Therefore, we can't reject only the users that aren't to be rerouted because we don't know which ones are to be rerouted until we make that first connection.
    There might be other ways to configure things that might get you closer to what you are trying to accomplish, but I don't see a way to make it work for your specific use case, which seems like a very common setup.

  • Guest
    Aug 2, 2021

    Moving this to "under consideration" for further evaluation. But it is unlikely this can be accomplished with the limitations of the current design.

  • Guest
    Jul 14, 2021

    Here is a link to the support document referenced in the Description: https://www.ibm.com/support/pages/node/638059

    The following document further explains how the Route by User function works - https://www.ibm.com/support/pages/node/666597

    The request cannot go directly to the subsystem configured for the route by user because the user name is not known at the time the first connection is made. So a connection must be made in the subsystem where the prestart job is configured or where the daemon job is running before it can be routed to the subsystem configured for a specific user.

  • Guest
    Jul 12, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM