DSXchange

Put specific Sort stages on the inputs of stages that require sorted input.

If the data are already sorted, set the sort mode to "don't sort, previously sorted".

The presence of the Sort stages will obviate the need for DataStage to insert any tsort operators into the score.

I agree with that. It's a good general rule that's been taught on Windows sys admin training since Windows NT (and probably before). One machine one major application. And don't use your (Windows) domain controllers for anything else.

RT = "run time". BP = "BASIC program". SC = "source code". DS = "design" (not DataStage). QS = "QualityStage".

Omit is not available in version 8.

It should not matter. The ISO 8601 standard prescribes yyyy-mm-dd and yyyy-mm-dd hh:mm:ss formats precisely because they can be sorted as strings without conversion.

Can you please explain, therefore, what you mean by "not working", preferably with examples?

You could try Null Field Length of 0. Null field value of "" will not work, because this is not valid as a decimal number. However, you could read the field as VarChar and then specify "" as the representation of NULL, and convert to decimal in a subsequent stage.

Does the mngr.cfg configuration file exist in your project? It seems unable to find this file.

It was never "lots". And certainly never warranted three exclamation points.

I slept through most all of that!

(Time zone, not boredom. Excellent that it was systematically resolved.)

This is sounding more and more like a commercial arrangement. If you want Ramesh (or anyone else) to work for you how much are you prepared to pay for it?

The DataStage parallel engine actually runs on MKS Toolkit - this engine is written to run on UNIX and this was easier than rewriting the engine to run natively on Windows.

If you use a Sequential File stage do you still get the padding? If not, dare I suggest that it is Oracle, rather than DataStage, that is padding the strings? Get the DBA to trace a few rows of the data being inserted.

My bad - I was replying from memory.

You can read a partitioned table sequentially. What you can not do is read a non-partitioned table in parallel.

Look for the Partition Table property.

What do you mean by "it doesn't work"?

What error messages (if any) are being logged? You need to provide more diagnostic information than "it doesn't work".

The variable Test is not being assigned a value - you will need to parse its value out of the InputArg argument.