DSXchange

Guess so... I can't figure out WHY the "CLEANUP ON FAILURE" option caused that behavior, but I guess I can live without it...

The culprit appears to the "CLEANUP ON FAILURE" option. When that is set, no rows are actually loaded to the target table. However, with that option off, all rows are loaded successfully. I'm not sure why, but at least now I know how to avoid the problem. I tried addding the messages file ...

The SQL10007 error code is telling you that it could not load the SQL error message for SQL error 1390. The description of SQL1390 is: <blockquote> SQL1390C The environment variable DB2INSTANCE is not defined or is invalid. </blockquote> So, the etldev1 user does not have the same value in the DB2IN...

Followup:

Also, make sure the db2nodes.cfg file has the actual machine name(s) for each node, and not "localhost"...

Background: DEV system: 1 box with Datastage and 2 instances of DB2 all running on the same box PROD system: 3 boxes. 1 Datastage server. 1 SOURCE system running DB2, 1 TARGET system running DB2. Problem: We have several job sets that something like: DB2TABLE(on SOURCE) -> FILESET FILESET -> DB2TABL...

Looks like the db2nodes.cfg file is unreadable/corrupt/missing/etc.