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 Db2 for i
Created by Guest
Created on Nov 1, 2016

Startup JVM on QZDASOINIT prestart process.

Would like the ability to specify a program or command to execute that will start up a JVM, for each of my prestarted QZDASOINIT jobs.

Use Case:

I have about 100+ customers running web apps, and connected via JDBC pooling from Spring. We are running up to 50+ QZDASOINIT prestarted jobs, that because active when necessary. These JDBC calls are calling RPG programs that utilize Java class. As you know, the first instance of the job is the killer, when starting up the JVM. And this could happen anytime during the day, when the user decides to call a program that uses Java.

So, my thought is that if the QZDA job could have the JVM already started at the time it begins during the Pre-start process, then this lag would go away.

Idea priority Medium
  • Guest
    Mar 23, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    We recognize that adding a new exit point for this purpose could be helpful. However, the database team has many higher priority requests, so a new exit point is not likely to be implemented anytime soon.

  • Guest
    Jun 22, 2017

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - DB2 for i
    Operating system - IBM i
    Source - ISV (Independent Software Vendor)

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - JAVA
    Operating system - IBM i
    Source - ISV (Independent Software Vendor)