DSXchange

Not in version 7. Pivot stage only performs a horizontal pivot (columns to rows). What you're seeking to do is a vertical pivot. Vertical pivot capability is suggested to be in the Pivot stage in version 8.1 (later this year).

In a phrase, unsorted though grouped data.

The vendor does claim to be compliant with standards as much as possible. I agree with Phil that behaviour with doubled quote characters (which IS a standard) does not comply. Has anyone raised this as an issue through their official support channel? Because that's the only way you'd ever get it fix...

It's called the Manager client.

4. Take a snapshot when processing with DataStage. Next month execute a DIFFERENCE query to extract the data.

5. Take a snapshot when processing with DataStage. Next month perform a lookup against the snapshot. If the key is not found, a new row has been inserted.

Job control routines don't have names. However, in a DSX or XML export file they do have property names.

Select all the columns you want to apply the function. With them selected right click and choose Derivation Substitution from the menu. In the field at the bottom enter Trim($1) and click OK, then Yes to All.

U has not participated thus far in this thread.

A combination of find and grep commands will do that for you. For example something like:

That way you don't need to know the location of the osh directories in advance.

You should only have nine columns in your job design. Therefore your parameter markers should be numbered :1 through :9. DataStage does not provide the value for the first column; that is supplied by the invoked sequence. The number of parameter markers must match the number of columns in the job de...

Why?

I have tried with the @INROWNUM.But its not giving the correct output. Can you help how to call server routine in parallel job. No. It's not the right thing to do. If you want a routine in a parallel job, write a parallel routine. If it's not giving the correct output, what IS the correct output? H...

You set environment variables in one shell (command) which finishes. Its environment is therefore lost. When you start dsjob this is a new process, with a new environment. What you need to do is create a script that sets the environment variables (and exports them) and then - in the same script - ex...

Why? There's a perfectly good system variable that will do that for you.

Why? There's a perfectly good system variable that will do that for you.