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 EGL Language
Created by Guest
Created on Sep 24, 2008

Availability of DB Connection Handle

SQLLib.connect() API in EGL does not provide any handle / reference to DB connection. The connection object remains implicit. Connect and disconnect happens transaperently to the developer.

Our experience of using EGL for a large, complex project makes us believe that providing a feature to optionally receive a handle to DB connection will be required in following situations
1) sharing connection among multiple functions of same JSF handler
2) sharing it among multiple JSF handlers of included JSPs in same page.
3) detecting if a connection is already available, so as to avoid duplicate connection
4) cleanup in case of exception etc.

Idea priority Medium
  • 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
    |
    Jan 15, 2009

    Since EGL is a high level language, it is generally not our philosophy to give users direct access to the APIs for the underlying technologies. People typically set up their DataSource on WAS with a connection pool, so they don't need to manage the connections directly.

    Also, giving users direct access to the handles could cause interference with the EGL runtime's handle management. JSF Handlers do a commit when you go from one page to the next. If two of them shared the same connection object they'd be committing each others work (or more likely the commit would fail since the other transaction was in progress).

  • Guest
    Reply
    |
    Oct 16, 2008

    This RFE is consistent with our strategy and product roadmap and IBM is continuing to evaluate.