Skip to Main Content

This is an IBM Automation portal for Integration 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 (

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 Future consideration
Workspace App Connect
Created by Guest
Created on Oct 2, 2014

Enable Parser / Validation Exceptions to populate SQLSTATE / SQLCODE for use in ESQL Handlers

ESQL exception handlers can filter on and access special registers

SQLState, SQLCode, NativeError, NativeErrorText

Some exceptions populate these such that the handler can filte / test / action some conditions (SQL exceptions, MQ, User Exceptions)

Many broker exceptions do not seem to populate these fields (parser / validation) making it almost impossible to handle these in ESQL - they must be handled by a Try/Catch node only.

It would also be useful if the ESQL Handler had visibility of the ExceptionList that would be set if it had been caught by a node. This alone might enable a Handler to do something with ALL exceptions.

It could also be useful if there was a ReThrow node (such that a catch path can also rethrow the last exception) - or have a way for ESQL to do this either via RESIGNAL - or the THROW statement

Idea priority Medium
RFE ID 60032
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Oct 6, 2020

    RFE Review. We continue to monitor this RFE and acknowledge that the exception handler style which is applied to database interaction could have value for other ESQL syntax operations such as the parsing example mentioned specifically. For now, status of this RFE is maintained as Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Oct 9, 2014

    Thanks for raising. We'd like to improve the capabilities of the ESQL language, and we'll add this in to the candidate list for the next tranche of such enhancements.