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.

Add a new idea Subscribe
Status Delivered
Workspace IBM Rational Business Developer
Categories Other
Created by Guest
Created on Jun 11, 2009

RELATED IDEAS

Generated java code has security flaws (support SQL prepare for all databases)

In EGL, with the following syntax:

get rec with
#sql{
select
x
from tbl t1
where
x = :rec.x
};

You generate, in java, a simple sql Statement, and you concatenate the rec.x value as a normal string, using as a control the only escapeQuotes function (blacklist approach).

If instead you were using the following syntax:

prepare pstmt from "select x from tbl t1 where x = ?";
get rec with pstmt using rec.x;

You'd have, in java, a sql PreparedStatement, which is much more safer. The problem is, on COBOL side, that then you'd generate dynamic SQL, which is unsafe.

Customer's request, would be to have anyway a PreparedStatement in java, even using the standard syntax.

For their business, RBD was adopted for the specific purpose to have both java and COBOL generation

Idea priority High
  • 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
    |     Feb 11, 2010

    This enhancement is now available in fix pack 7.1.0.5. It will also included in our next 7.5.x fix pack.

  • Guest
    Reply
    |     Jan 6, 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
    |     Jan 6, 2010

    Thank you for this suggestion. EGL is currently inconsistent in this area - we use SQL prepare for some databases , such as DB2, Derby, and Cloudscape, but not for others. In our next set of fix packs (7.1.x and 7.5.x) we plan to provide this support consistently for all supported databases.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.