DSXchange

Use @INROWNUM < 2 as a contstraint on an output link (input link to you Oracle stage. Only the first row will meet the constraint.

Why aren't the duplicates being treated the same way as the bad PK records. If the Oracle PK unique constraint is active on table 1 then the bad PKs and the duplicates should fail on an INSERT into table 1. Is so, they can be routed to table 2 via a constraint. What am I missing?

Is there a method for determining when the last record is traveling down a link? I would like to build a constraint for a link that would only evaluate to TRUE when the last record of an input set is detected. The first row is easy (@INROWNUM = 1). Is there anything like @LASTROWNUM ???

We are contemplating developing an EAI Realtime MQSeries DataStage job that will process XML Messages. We'd like to talk with anybody who is in production with such a DataStage configuration. The DataStage job will utilize the MQSeries Plug-in stage with a wait time of -1 (indefinite wait). Messages...

Assuming that the plug-in type (e.g. Oracle) supports transaction grouping and that the two output tables are in the same RDBMS and that they are in the same output stage linked to the same transformer stage, then you can group the two (or more) output links as a transaction group. Both links will h...