DSXchange

Yes, but you'll need a routine to interrogate the job log of Sequence 1.

DS_TRANSFORMS contains Transforms (pre-stored expressions), not Transformer stages. Transformer stages are recorded in DS_JOBOBJECTS. But I agree with Arnd's advice that the API is a smarter way to retrieve the information - we can't guarantee that DS_JOBOBJECTS will be the storage mechanism in futu...

MWB uses the table definition. It also uses columns on links. And it knows whether each link is an output link (stage is reading data) or an input link (stage is writing data). It is by this means that automated services seek to stitch together the lineage. You can see the same when you do Stage Bin...

One at a time is all you can do from BO, whether using Import Export Manager or Metadata Asset Manager (version 8.7).

The term is US-centric. It means anything outside the borders of the USA. This includes Canada and Mexico. Character set is not suggested by "international" in this context. Character set is managed by NLS. In theory you could process US data specified in Kanji characters. However, I suspe...

Doing Import Metadata, I identify down to schema level, then Set Pre-Filter before Identify Next Level to bring back tables. Even though I supply a string that exists in some of the table names in the schema, the importer brings back every table in the schema. Since there are tens of thousands of ta...

You can handle the message, but you can't prevent it being generated. DataStage thinks it's something you ought to know about and, do you know, I agree.

Your number is stored as a decimal number and an exponent. It's more likely that your number is stored as a binary mantissa and exponent. In a DFloat the mantissa is 51 bits and the exponent is 11 bits and has an implied constant offset. There is a sign bit for the mantissa and a sign bit for the e...

Read EVERYTHING in the error message. We know the column that's throwing the warning, but in which stage?

If the basis for "distinct" is indexed in the database it will make a huge amount of sense to include DISTINCT in the query, mainly for the reason Arnd articulated, but also because the query can be resolved entirely in the index, a huge performance gain. Relative cost (volume of distinct ...

Aha!

Project names are case sensitive. Your failed request specified DBProject when it should have specified DBproject.

Start with something simple. Can you use -lprojects remotely?

Under what user name does the DataStage job run (that is, how are your Engine credentials set)? Does THIS user have execute permission to the rename script?

In job sequence 1 ensure that "log warning for any activity that completes with other than success" is selected.
In the main sequence create a non-success trigger on the Job activity that runs job sequence 1, and direct that to a Notification activity.

While I haven't done PVCS, we simply downloaded the Eclipse plug-in for SubVersion from the web.