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.
|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.
|Priority Justification||Informational messaging in job log|
|Customer Name||Customer wishes to remain anonymous. Please contact IBM account team.|
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 "email@example.com" 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