Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Under review
Workspace DataStage
Created by Guest
Created on May 10, 2024

Enhancing DataStage Monitoring and Debugging Capabilities

One of the critical aspects of monitoring, tuning, or debugging individual jobs or an entire DataStage project is to clearly understand which database system activities are triggered by which stage in a specific DataStage job within a particular DataStage project. Currently, there is no functionality to view, at the project, job, or stage level, the number of connections opened against a specific database system by DataStage, or the current status of each of these connections from a DataStage perspective (such as waiting for a DB response, processing, waiting for input data, idle, etc.).

Databases typically maintain a unique identifier for each session. As a first step, we propose logging this identifier to the DataStage job log at the start and end of each session. This would provide a clear picture of when each connection is initiated and terminated, allowing for more effective monitoring and debugging.

Furthermore, it would be beneficial to log the total waiting time from a DataStage perspective at the end of each session. This information would provide valuable insights into potential bottlenecks or inefficiencies in the system, enabling optimizations and improvements to be made. This enhancement would greatly improve the transparency and manageability of DataStage projects, leading to more efficient and reliable data processing operations.

Needed By Quarter
  • Guest
    Reply
    |
    May 10, 2024

    Oracle allows for a client session identifier (CLIENT_IDENTIFIER) which can be set at the start of the session. Currently one could explicitly set the identifier in the conductor (before-sql) and player processes (before-sql (node)) like this

    call dbms_session.set_identifier('#DSProjectName#_#DSJobName#.#DSJobInvocationId#_#DSStageName#');

    This requires manually setting it up in each stage though. It would be beneficial to have an option to set this automatically. With it one can trace the execution from within the database system.

    Oracle is just an example here. Other database systems provide similiar capabilities, like e.g. Teradata supports Query Bands, which can also be set from the Datastage job / stage.

    I think we would need both: logging database sessions with the identifier in DataStage and setting the client identifier.