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


Add a new idea Subscribe
Status Not under consideration
Workspace DataStage
Created by Guest
Created on Feb 19, 2019

RELATED IDEAS

ability to log warnings having a connector with rejects link

Currently having a connector with a reject link one can only choose to Abort or ignore rejects. I need the option (out of the box) to log warnings.

Rejects should be captured - that is why I like a rejects link. Sometimes I do not want to abort the job and sequence but I want to capture the problematic rows at the same time. that is why this option is needed. Should be simple to implement.

This Idea has already been entered as an RFE by Michael Tiefenbacher

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=61089

  • Guest
    Reply
    |     Oct 20, 2020

    Thanks for the additional explanation. I will mark this as future consideration as we progress with our roadmap.

  • Guest
    Reply
    |     Sep 25, 2020

    Hi Scott,

    it would be ideal to implement this as Michael has suggested it. Then you could still specify to abort a job after n rejects, or don't abort it but finish with warnings if it has rejects. If you get warnings then you can either promote the warning to an abort via a message handler or handle the job with warnings in the sequence. Maybe it would also be good to specify that the job does load the whole data into the table and logs all rejects but have it abort in the end by specifying Abort after (rows) -1. With the current behavior (Abort after n rows) you actually have to set it to abort after 1 row rejected (to be sure to handle rejects) and then you can only log the first reject.

    KR Ralf

  • Guest
    Reply
    |     Sep 8, 2020

    Hi Scott,

    the request was entered originally foir the Db2 Connector. It is not about capturing the rejects - this is possible and clear. It is about the job behaviour in such a case.

    If the target Db2 connector stage experiences rejects I have only options to end the job successfully or to abort it. My request / idea was to have the joice to get a warning and end the job with finished with warnings.

    This has the effect that the job will finish - and additional jobs in row could run - but I get notified in a way to have a closer look at the unexpected reject.

    This is needed when the reject is not bad enough to abort the job but it will raise the developers attention to look at the rejects. If the job finishes without warning it is not simple to figure out if there had been rejects (having many jobs in nightly run) - without building additional processing logic.

    In the end I want a simple way to end a job Finised with Warnings if I get rejects in a connector stage.

    thanks best regards

    Michael

  • Guest
    Reply
    |     Sep 8, 2020

    Thank you for submitting this idea. Could you please help clarify what you are looking for.

    If we use the JDBC Connector as an example:

    https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.7.0/com.ibm.swg.im.iis.conn.jdbc.usage.doc/topics/jdbc_manage_reject_data.html

    You can currently capture rejects based on conditions such as SQL Error or Row not Updated/Inserted/Deleted. Such a reject would be sent down the Reject link and can be processed in any desired fashion. You could for instance log it to the job log using a Peek.

    Is your enhancement request centering around number 8 from the Knowledge Center document above, i.e. having an option to "never abort" and to just handle all Rejects that come in?

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.