DSXchange

Allegedly, yes, but I've always found it best to explicitly create them in the Projects where you need them.

Perhaps so, but I can't comment on a term that someone made up and "circular strain" falls squarely into that camp. Seems pretty clear that a best guess would be that you had some kind of sequencing issue and while I sincerely doubt you had to split things up between transformers it may he...

Just for the record, you don't need the extra "IsNull" check with the NullToEmpty transform on both sides.

Your first syntax is fine unless both sides could be null. Simpler to use the NullToEmpty() transform, perhaps on both sides:

NullToEmpty(lkp_CRC.CRC) <> NullToEmpty(CRC)

Would you be willing to post your dsx or at least the relevant portion(s)? Not really sure what "at the top" means.

You'd only be able to read it in PX if all of the columns in the file were defined as string fields... which is all they really are, anyway, when you get right down to it.

Your header record is being rejected by the stage since it doesn't match the metadata for the columns. If you added a reject link to the stage you would see this happening, otherwise it just gets "skipped".

What makes you think I haven't?

I guess I should have also asked - is this particular to any one data source? Say, like... DB2?

Just want to reiterate that you use "-wait" OR "-jobstatus" and not the two of them together. The "-jobstatus" option is what is getting you the 1,2,3 (etc) return codes and "-wait" gets you zero or none-zero return codes. It's important to understand that it'...

Is this specific to AIX?

Where exactly in the dsx are you still seeing reference to the original table name?

Right, you would need to use a combination of -lognewest and -logdetail to get what you want.

Reread the first word in my previous response.

And you could only be reading the file 'in parallel mode' if it is a fixed-width file, so my money is on sequential.