DSXchange

That's because you are using DSGetLogSummary rather than DSGetLogDetail.

Senior only proposed this approach. The bad thing is whenever new person come to board, they are not trying to find what we have and what should be done to improve. Instead of that , they want to change the entire approach as per their experience / what they know. They are going to link the server ...

As you should if literally all you are doing is calling dsjob from the command line. Let us know how it goes.

... the end result of which was shown as "my guess" above.

That's true, it (an Aggregator) could stand in for the Remove Duplicates stage here.

As shown above. Keep in mind the fact that, in an integer, there is no "right side of the decimal".

Sorry, missed the "integer" part. You... can't. Ask them what "-84.469345" should be as an integer and then you'll know how to handle the conversion. My guess? "-84469345".

What have you tried? Isn't this just a simple StringToDecimal() conversion?

Groucho Marx.

Ok, fair enough. What about all of the questions asked over in that thread, especially NLS settings? Without knowing those answers, I don't know if this would make any difference but I would try (assuming these are dynamic hashed files) zipping the directory and Dictionary file if present, copying t...

I'm going to repeat something - if all you are determining dynamically is the Invocation ID then there's no reason to not use a Job Activity stage for this. However, if you are actually deciding on the job name as well at runtime, then this approach is appropriate.

I didn't mean same (as in similar) issue but was wondering if you two worked together and were posting the same question. Still a yes?

The first post shows them using "-jobstatus". As to the why of the error, you'd probably need to go to support for that since we're not privy to the inner workings. But to me it stems from improper use of the Routine Activity stage with ExecSH, I would think it would be fine if you wrote a...

So, there's no routine code involved and all the stage does is call ExecSH? Use the Execute Command stage instead, run dsjob from there if that's all you are doing.

We start by getting you into your own post. Now, much like was mentioned in the post you jumped on, have you done any of the configuration tasks needed to use DB2 with DataStage? Particularly the "bind20" utility? Also note I had to guess at your Release, Job Type and OS - please edit and ...