Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Other
Created by Guest
Created on Mar 8, 2010

Migrated prepare syntax generates expensive loops [RTC 40352]

Performance enhancement to generated Java to the effect that the implicit SQL statements used to implement EGL I/O statements associated with SQL records should be prepared no more often than is necessary.

For implicit delete or replace of the current row in a result set, then prepare the statement once per result set on the first replace or delete for the result set.

For all other implicit SQL statements, prepare the statement once per connection the first time the statement is executed.

Idea priority High
  • Guest
    Reply
    |
    Mar 11, 2021

    IBM Business Developer is a continuous delivery offering, and aims to satisfy the needs of a rapidly evolving market segment. Product strategy evolves and requirements are continuously evaluated against that strategy. This RFE has recently been reappraised against the wider product strategy and does not fall into IBMs delivery plans for the next 12 month. Whilst this RFE might be valid and we might look to deliver longer term, this RFE is being rejected at this time.

  • Guest
    Reply
    |
    Mar 9, 2021

    This RFE is more than a decade old. It might not be relevant now. Please create a new RFE if this requirement is not yet addressed in the product and it still exists.

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Business Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Business Developer

  • Guest
    Reply
    |
    Jul 2, 2010

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    Reply
    |
    Jul 2, 2010

    We would like to see a solution for this RFE implemented as soon as possible. However, the proposed solution does not solve our problem, as the loop is performed in a batch main program, while the SQL is executed by a program called from within that batch main program. What needs to be done is telling the Oracle physical connection that it should cache the prepare result.
    From the JDBC manual:
    "Call the OracleConnection.setStatementCacheSize method on the physical connection. The argument you supply is the maximum number of statements in the cache. For example, the following code specifies a cache size of ten statements:
    ((OracleConnection)conn).setStatementCacheSize(10)"

    Why is this important to us ?
    1. Performance penalty for virtually all batch programs we will generate to Java. It could make the difference to get all batch processing done in the available batch window.
    2. It is unavoidable: we have to use "prepared statements" in order to be able to manage performance of queries and to avoid SQL injection
    3. It affects all companies running Java generated from EGL in a plain JVM
    4. Solution effort is probably very small.

  • Guest
    Reply
    |
    Mar 11, 2010

    We agree that this change would have a significant performance impact, especially for customers who are migrating from VA Generator to EGL, and moving from COBOLGen to JavaGen. This is a candidate for implementation in our next release.

  • Guest
    Reply
    |
    Mar 8, 2010

    submitting to RFE community