Hi Ameet,
"Error reporting" can be quite misleading or it just a very wide topis to cover.
Especially you are preparing pre-sales document, there will be very high chance that whatever you put up in the document. You have to proof it to the customer.
Try to write it generic and keep it high level, give a few scenario or event specific. For example data error and etc.
cheers,
j
ERROR REPORTING IN DATASTAGE
Moderators: chulett, rschirm, roy
Ameet
I think the way DataStage can scrub data is the part of the product. I would show how DataStage can do multiple rejects. You can check for nulls if you want to simplify. If a field cannot be null in the database then you should check for nulls so the database does not reject the insert or update. This is simple and easy to demonstrate.
Kim.
Kim Duke
DwNav - ETL Navigator
www.Duke-Consulting.com
I think the way DataStage can scrub data is the part of the product. I would show how DataStage can do multiple rejects. You can check for nulls if you want to simplify. If a field cannot be null in the database then you should check for nulls so the database does not reject the insert or update. This is simple and easy to demonstrate.
Kim.
Kim Duke
DwNav - ETL Navigator
www.Duke-Consulting.com