DSXchange

Jobid allows you to create a (short) alias for a (long) job name.

Not really. What can't you understand?

What Roy suggests is more likely to happen in server jobs than in parallel jobs, and is guaranteed for neither.

This is possible contention on the job log. There is a single-threaded process that generates the next log key number. How many instances are you running concurrently? Keep in mind that parallel jobs have many more processes than equivalent server jobs, and so will typically have rather more events ...

We have no idea of what "not working" means in this context.

Explain exactly what you are doing, including the data types of the reference key column and the column from the stream input that is mapped to it.

Mention, too, whether any error or warning message is logged in the job log.

Other than faking it (using a command line interface to execute a query against the local repository database) I too am unaware of any command line technique the like of which you write.

My guidance is that you should use Usage Analysis. That's why it's there. And if what you say is true about loading table definitions into jobs (well done!), then this technique will work infallibly. Of course it's possible to derive the information from the repository tables, and you can search DSX...

As much as is just short of your server running out of memory.

No you don't. You need to select the table definition and perform a Where Used analysis. Use the filter to restrict the search to jobs.

In scenario 2 you have two pivot keys so will get two columns in the output. The first output column will pivot on all columns in its derivation, but there is only one column mentioned, so this value will occur in all rows.

Does the SetDSParamsFromFile routine carry an Ascential copyright notice?

How is your "Lookup Failed" rule set? If it is Fail (the default), then your job will abort as soon as the first lookup fails. If it is Drop, you'll only know that not all lookups succeeded because the output link row count from the Lookup stage will be smaller than the stream input link r...

That is not the same question. Please start a separate thread, so that future searchers will not be confused.

Be sure. Check.