DSXchange

Bad advice. The job is one process, but it has child processes. If you kill the job process, its child processes become zombies which are much more difficult to kill.

You're more likely to find a timeout to tune in the Oracle client software. There's nothing in uvconfig that would help.

If you don't have an export, you may be able to restore the entire project from system backup (temporarily changing the name of the existing project directory). Then export the job in question, rename the project directory (once it's not in use), and reinstate the real directory as the project direc...

Welcome aboard. :D

The functionality you seek (called "parameter sets") will be available in the next ("Hawk") version, due out later this year.

Until then you're stuck doing it "the old way".

What function are you using in the Modify stage specification? Data type conversion is not necessarily automatic.

Without knowing which columns are in tables E and F it's hard to advise. You could use two separate jobs, or two streams in one job. Read rows from source table, split into two streams (Copy stage) then process each stream in its own Transformer stage before using whatever stage type is appropriate ...

That's correct behaviour for any form of outer join. If there is no match, columns from the right Data Set (or table) return NULL.

That's entirely your choice. It depends a lot on what you do with the product, and how you do it.

There are no specific exam preparation materials. As noted, the IBM class Advanced DataStage EE is helpful (since it and the certification exam were developed in tandem). DataStage Essentials EE is a prerequisite for the advanced class.

Beware that it's now Beta 2 - the rules may have changed.

In the Columns grid scroll right and you will find rules that can be set on a per-column basis, including incomplete and "contains terminator" rules. Set the incomplete rule to Replace. Click on Help while there to learn more about the precedence requirements of these rules.

You need to know how your Japanese characters are encoded. You must specify the exactly correct character map to convert these to DataStage's variant of Unicode. Note that a different map may be needed to view the characters correctly in a DataStage client. But this is mapping characters. It is not ...

A lookup against a hashed file IS a left outer join if you don't constrain the output link based on the result of the lookup. And there's no reason not to create a 64-bit hashed file unless your operating system sets an upper limit of 2GB on file sizes. Check with your UNIX administrator.

Be patient. If someone has disabled the use of categories in the View menu and you have a lot of jobs in the project, it can take a lot of time to retrieve all the jobs. Once it's finished refreshing, open the View menu and check whether display of categories is selected. Ultimately, go through your...

I suspect gateleys is running DataStage on a Windows platform rather than a UNIX platform.