DSXchange

OK, let's concentrate on what you mean by "breaking". What exact error message is received?

If you can hold off till version 8.7, released any day now, you will get an Operations Console that does this for you.

It depends. A table name might be referred to in its table definition, in a DataStage job that mentions the table, in a routine that deals with the table. The different kinds of object are stored in different repository tables, so that there is no single place to look. Table definitions are stored i...

Business Glossary does not give you column granularity. It only gives a high level account, called "business lineage". Metadata Workbench gives the more detailed "data lineage". However, neither lineage reports values; only lineage. Structural changes ought to be auditable in the...

The overrides are already in files (one for each type of override). You view these from the Rules Manager client, by default using Notepad. All you have to do is copy/paste or Save As. Or you could learn the location of the files in your project and copy them from there. What's your purpose in expor...

DataStage has its own conventions for stdout and stderr file units, so you must be very careful using cout, and printf and similar functions. Indeed, there ought to be no need to use functions like printf in DataStage parallel routines.

Surely it's enough that your other columns are your pivot keys?

Yes. If the share point path is directly accessible from the DataStage server you can write directly to a file there. Otherwise use an after-job subroutine to copy/move the file to its share point location.

An OK trigger will not fire if the job has even one warning. Please check whether this is the case; you may need to refine the trigger expression.

Research "transaction isolation level".

Did you specify a pathname for the new ".ds" file? If not, look in your project directory on the server.

One thing that gives me the "irrits" is those who suggest running on a single node as the way to "solve" poor partitioning choices.

It's not a solution.

01011101010001010101010010001100101010010101001010100111110101010101001110101010110101001010011010101010010110101010010111101010101010101010101

In a word, contention.

DataStage will not implicitly truncate a VarChar. As you have discovered.