DSXchange

USERSTATUS could be one solution. So could writing the count to a file and then using Execute Command to 'read' the value, triggers after that could go to JobB or JobC.

Why not take the user-defined SQL route using NEXTVAL? That or a Sequence Generator?

So not a "need" after all but rather a preference. Fair enough.

Or a Server job writing to a Folder stage...

mmanes wrote:Ok, but I have to insert the value in the field into transformer stage.

Why do you "have to" do it in a transformer?

SPuneet wrote:But the seq fails if any underlying job fails.

Only if you tell it to. What compilation options do you have enabled?

Use APT_RDBMS_COMMIT_ROWS for DB2. Default is 2048.

ray.wurlod wrote:ODBCINI is not a mandatory environment variable.

And just for the record EDI_ITLS, it IS mandatory if your .odbc.ini file is in a "non-standard location" as that's how it knows where to find it.

Forget the 4, it plays no role here. An integer can store a value up to 2147483647. However, if you are confident your value will never go over 999999 then use 6 for the length otherwise best to use 10 (or 11 if signed).

It's an integer, the (4) just means it is stored in 4 bytes. Look up the maximum size of an integer and account for that.

Yes. That error would imply that your XML is not well formed.

Same answer. It's not "fine" there, your tool is converting it for display. DataStage isn't.

This is all about your database but wanted to point out that you can't set APT_ORAUPSERT_COMMIT_ROW_INTERVAL for DB2 - the "ORA" part means Oracle.

As noted, there are lots of examples of usage out there. Don't know anything about 'Newton Apples' but found a couple of lessons there: http://newtonapples.com/datastage-transformer-looping-1 http://newtonapples.com/datastage-transformer-looping-2 A search for "datastage transformer looping&quo...

What happens when you stick with the original datatypes?