DSXchange

Do you need a /D switch for the domain, the same as dscmdexport?

Why don't you research this, perhaps by a Google search?

It is a technique available in all operating systems for transferring data between a writer process and a reader process.

Quel dommage!

... to "how to restart server after particular job finished"?

Three sources? Table1 and Table2? Is this some new field of mathematics?

You seem to have a simple full outer join requirement. If the tables are all in the same database perform the join there.

Otherwise search DSXchange for techniques for performing a full outer join in a server job.

Time to talk with your official support provider. I can not reproduce what you're claiming.

There's no dot in the email address.

Try membershipdirector@dsxchange.com (maybe with a CC to editor@dsxchange.com).

Maybe they're snowed in!

Start by thinking about how you'd do it in SQL. A UNION, maybe? Then, essentially, replicate that methodology in DataStage. Probably the easiest is to have DataStage execute the SQL you got in the first step to perform the extraction.

Use the full path of sortcl or include its parent directory in your command search list (the PATH environment variable). Standard UNIX stuff.

By "data element" do you mean a DataStage Data Element?

If so, your easiest solution is probably a global search and replace in an export file - structure of Data Elements in the DSX file is simple.

They are effectively the same. If, however, you ever move to a UNIX server then you will not have the SQL Server Enterprise stage. This is only available on Windows, whereas the ODBC Enterprise stage is available on all platforms.

Use Director client Status view sorted by Status.

Only possibly but, because of that, it's usually a good idea.

You don't eliminate them - they are your customer's data!

You figure out how to handle them, typically by specifying the correct character mappings in both DataStage and Teradata.

The installation process creates it there because it's certain that that folder exists (having been created from the installation script) - it can not be certain that \Tmp or \Temp exist.

Is it just me, or has this thread strayed somewhat from its topic?