DSXchange

$ENV, $PROJDEF and $UNSET are not environment variables.

They are reserved tokens that can be provided as default values for job parameters that are environment variables.

Operating system environment variables ARE case sensitive.

There is a log entry called "Summary of Sequence Run" near the end of the sequence's log.

Otherwise you need to create a recursive routine. I have one somewhere - I'll see if I can dig it out.

The Sequential File stage scans the input stream until it finds a character that isn't part of an integer (or a delimiter) and returns that. Then it scans to find the next field or record delimiter. So it's working as designed. Technically, the value "1 2" is NOT an integer, so maybe you n...

Try using Iconv() function with "MB" conversion.

Welcome aboard.

What are the NLS settings for this stage/job?

Does the metadata on the Columns grid specify scale = 2?

Start by reading this W3 article on canonical normalization issues. It may give some insight into where in your data the problem lies.

That error message is coming from a Job activity, or from a call to the dsjob command line.

Job parameters may not be null. You need to intercept the value and convert it from null to something appropriate, such as "". One way would be to interpose a User Variables activity.

If the code point value is over 255 you will need UniChar() function rather than Char() function.

Been a long time, been a long time, been a long lonely, lonely, lonely, lonely time...

Amazing effort since he hasn't actually played with DataStage for four years.

There are three job designs using the SKG stage.

A job with no input or output link will create the state file.

A job with an input link only can be used to initialize the state file.

A job with an output link only can be used to deliver surrogate key values.

It might help to see the metadata so that the record length can be established, then you can use that information to identify whether any data are actually missing.

No idea.

You're not showing us the same data in each file. "Looks like" they may be, but the same they're not.

What has changed since it was working properly? (Hint: "nothing" is not the correct answer.)