DSXchange

You can do it with a simple before-job command, but a script (or routine) would give you better control (for example checking whether the directory already exists). For the simple method just use a set of operating system commands in the Input Values field for ExecSH as the before-job subroutine, fo...

Welcome aboard. Start by disabling operator combination so that you can more accurately diagnose what's going on.

The rule is "last one in wins". There are two 10s in the sample data. The first 10 would be "removed" by being overwritten.

Convert the # to @VM and load into a hashed file with a key generated as @OUTROWNUM. Then read from the hashed file dynamically normalized on your multi-valued column. You will need to set up the table definition with the "supports multi-valued columns" check box selected.

Configure enough columns for the largest expected N.

Not enough information. What logic are you using in your SCD stage? What is it about the third node (#2) that caused the failure to be there?
What data volumes are involved? How big (number of rows, size of rows) is the dimension table?

I think they need the RMM stage.

To quote from that classic film The Castle - "tell 'em they're dreaming".

Hashed files have guaranteed unique keys. That rules them out for what you want to do. The only other solution is to use a UniVerse stage, which uses the same style of SQL as does the ODBC stage. Whether you use UniVerse or ODBC, your lookup speed will be enhanced through use of an index on the sear...

Parse into separate columns then run these through a Pivot stage.

I think it's probably worth re-thinking your logic. NullToEmpty(inS1xfm.CLAIM_KEY) implies a "cast" from BigInt to String and then your Else clause converts it back to BigInt - however your Then clause generates a value ("") that can not be successfully converted back to BigInt. Why not just use If ...

Lots of people, as a Search would have revealed. This "small rectangle" pad character is actually a NUL byte (0x00). It is the default string pad character used in DataStage parallel jobs. In C programming, this character is understood to mean "end of string", which may explain what you're seeing wh...

a)There is no difference between the two enviroments.we checked with Datastage admin regarding this. Is there any we can find if there is any difference between two datastage environments. Check with the Datastage admin? Seriously, though, your diagnosis has been systematic thus far. But you're onl...

Assuming that the data type of the outbound column is string, and that you're doing this in a Transformer stage, then a suitable expression is

You are working on a job that has an after-job subroutine that checks the row counts, and is the source of the logged message. The underlying reason for the difference is in the job design, almost certainly in the constraint expression used in a Transformer stage.

What's different (a) between the two environments and (b) between the data in the two environments? Have you checked that it is exactly the same job in each environment?