DSXchange

All records are processed by all streams. Sorting and partitioning are done ahead of the Copy stage and preserved throughout.

Separate streams (via Copy stage?) funnelled back together.

Unless someone was monitoring the system at the time, you can't. It's gone. It's history.

For a extra few bucks you can buy a baseball bat that you can use to enforce best practice.

Why are you trying to create the warning file in the root directory? It's probably correct that you don't have write permission there.

Both UNIX and Windows are happy with "/" as the pathname delimiter character - at least those versions of Windows that support DataStage engine.

You could use the bulk loader (bcp).

You need a script. Use an Execute Command activity to execute the script.

That's what Oracle reports for the width when you're using multi-byte character set. Just leave it consistently set to VarChar(320) throughout the job and all will be well.

At a guess, Teradata does not permit the bulk loader to be used with a view. You will get more information from your Teradata errors manual.

This is a vertical pivot. Search DSXchange for techniques - at least three methods exist for server jobs.

Welcome aboard. Are you using a Complex Flat File stage? This has inbuilt support for packed decimal data.

Where is it, and is that findable by the user who executes DataStage job? (For example, what is the relationship between the location of db2nodes.cfg and the value of DB2INSTANCE or APT_DFLT_DBNAME?)

The CFF stage is documented as not handling more than one OCCURS DEPENDING ON clause. (I have not checked whether this limitation is removed in version 8.5.)

Either can be the default, as specified by the 64BIT_FILES setting in the uvconfig file. You don't want the default to be 64-bit, however, because this is wasteful for small hashed files, and the majority of hashed files are small (less than 1GB).