DSXchange

Use Sum(1) to get count. Generate the 1 values upstream for example in a Column Generator stage using a Cycle with only the one value.

If it's actually a server job (as posted), use a Transformer stage to generate the 1 values.

Assuming your developers are diligent in only ever loading imported table definitions from the repository into job designs, right click on the table definition and perform a "where used" analysis.

What is the data type?
Are they genuine spaces (0x20) or something else?

OK. Initial advice is "don't push - especially not on weekends".

Try changing the Data Element in the Columns grid to "Date". It may be that DataStage is expecting an internal format when data type is Date. The Data Element can cause a translation to be effected.

Can you simply standardise them in QualityStage, and re-arrange them afterwards in DataStage?

Try using Import Export Manager. All "deprecated" means at the moment is that it's no longer supported. It still works.

Performance on read is not tunable. If the hashed file is properly sized, this should be one I/O operation per key-based access (lookup), or one I/O operation per group (stream). Performance on write is tunable by preallocating the space for the hashed file, as Craig suggests. The Hashed File Calcul...

Well done.
Just be aware that there are two sets of Chinese characters (simplified and traditional), and they use different code pages and therefore different maps. The other family of maps is BIG5.

Welcome aboard.

Check the permissions on objects in the project directory (it must be writable by the group).

Check that the credentialled user belongs to the group.

Note that DataStage treats local user and domain\user separately by default.

Yes. Obviously you will want to export/import all your design work. If you've customised project properties, remember/record how they are set so that you can replicate these in the new environment. If you've created hashed files manually you will need to do that in the new environment. If you're usi...

Open the column metadata and specify the detailed format string for that particular timestamp field as "%yyyy-%mm-%dd %hh:%nn:%ss.3".

Set the data type as Timestamp Microsecond 23 3

These settings override the default settings.

Or even use the -exec option in find to execute the orchadmin rm {} command.

It depends what "supported" means in this context. Usually they maintain backwards compatibility for a while. I suggest you try one. If it doesn't work, throwing a "not supported" error, then you will be up for the effort of changing job design.