DSXchange

I did specify "in a 32-bit operating system". Yours isn't.

Trim(many spaces) always returns one space, not none. This is documented behaviour. There are other functions for removing spaces.

Rahul Bharadwaj wrote:Please let me know the Equivalent property for 'contains terminators' (Column property in server) in parallel job.

There isn't one.

Check "fixed width format" check box on the Format tab, then supply a delimited list (spaces or commas) of the column widths in the column widths field.

In the project directory tell us what's in ./\&COMO\&/DSRTRACE_dsadm-466950 file.

Why not you can include the parameter set in the sequence? Because the parameter set has to be determined dynamically. I would put this logic into a Routine, and use the return value from that routine to provide the value to the job parameter or update the values file of the Parameter Set that the ...

Does the indicated session number show up in web console? If so, disconnect that one.

You could try running a probe with dsdlockd (with -p option).

Worst case, re-start all services.

You have to read past all the fields, for such is the nature of sequential file access, but you can set the "drop on import" property for those that you do not require in the job.

Use NullToValue() function to provide a value that indicates that the source was null, perhaps -999999.99 (or any value that will never occur in your real data).

Why "using Transformer"? Surely an Aggregator is the correct stage type to get a minimum value. You could also sort the data by date and use a Remove Duplicates to keep only the minimum. There's also a flaw in your logic. I have get the min date of ColA and compare it to all the dates in C...

Join stage does support more than two inputs (though the joins are still done pairwise under the covers).

CFF stage supports one OCCURS DEPENDING ON clause. So what's the value in COL7 ?

More to the point, an Excel ODBC driver for UNIX that is compatible with the Data Direct driver manager.

It must be documented somewhere - I don't make this stuff up! Maybe it was on the Advanced DataStage training materials. I really can't remember - it may have been "what's new in version 7.5" material!

What do you mean by "escape" the key column?

The only non-custom stage of which I'm aware that can use a parameter as an input column name is the Modify stage.