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,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
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.
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
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.
Do not place IBM confidential, company confidential, or personal information into any field.