IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

INZU066E is issued and HPU continues to process and produce additional error codes and can mislead root cause

Customer coded incorrect Table during Unload statement. Their job outlog showed error codes INZU063I and INZU101E. This caused the customer to assume that the Unload function contained an UNSUPPORTED keyword, causing confusion. After further review, they noticed they incorrectly coded the Table. Once HPU encounters an invalid or non existent Table, HPU should not continue to function and only invoke the lone error message. In this case it used INZU066E, which references TABLE SPACE. The error message should be more accurate in terms of the Object that is invalid.

BTW, the TABLE was incorrect, but INZU066E mentions an incorrect Table Space. The error message should be more precise and identify the TABLE is incorrect.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 31 2020
  • Planned for future release
Who would benefit from this IDEA? Customers researching various errors that HPU should not even process.
How should it work?

HPU should stop processing once an invalid or non existent TABLE is realized and invokes an error message. Also INZU066E refers to a Table Space even though the TABLE was invalid. The error message should be more accurate about the obeject in question.

Attached file explains how customer thought they had an error unloading a TABLE while using HEX in the 'where' clause. They assumed HEX was not supported because of the error messages. Upon further review, they made a user error in coding the HEX statement and also realized the TABLE was not valid.

Idea Priority Low
Priority Justification Informational messaging in job log
Customer Name Customer wishes to remain anonymous. Please contact IBM account team.
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions