Capturing rejected rows from DB2/UDB API Stage
Posted: Mon Jul 10, 2006 1:33 pm
We are having problem capturing rows that are not loaded to the DB2 mainframe using the DB2/UDB API stage in a PX job. Here is the basic job design.
Seq ---> Transform ---> DB2/UDB API
|
V
Seq2
In the transform, we added an "OTHERWISE" contraint and chhecked the "Otherwise/Log" box. The data did not get loaded into the DB2 database because of some date format. However, the rejected rows are not written to the Seq2 file.
We have done the same design in a server job and the rejected rows are captured. We would like to achieve the same thing with a PX job using the same DB2/UDB API stage but have not been successful.
We cannot use the DB2/UDB Enterprise stage as our DB2 database is on a mainframe. Has anyone been successful with this using the DB2/UDB API stage on PX jobs? Any input would be greatly appreciated. Opened a case with Technical Support but have not received any feedback yet. Also done extensive searching in this forum but to no lead so far.
Thanks
Seq ---> Transform ---> DB2/UDB API
|
V
Seq2
In the transform, we added an "OTHERWISE" contraint and chhecked the "Otherwise/Log" box. The data did not get loaded into the DB2 database because of some date format. However, the rejected rows are not written to the Seq2 file.
We have done the same design in a server job and the rejected rows are captured. We would like to achieve the same thing with a PX job using the same DB2/UDB API stage but have not been successful.
We cannot use the DB2/UDB Enterprise stage as our DB2 database is on a mainframe. Has anyone been successful with this using the DB2/UDB API stage on PX jobs? Any input would be greatly appreciated. Opened a case with Technical Support but have not received any feedback yet. Also done extensive searching in this forum but to no lead so far.
Thanks