DSXchange

Hello Experts:

Pls. help me understand the the engines/mechanism involve in Server and Parallel Jobs under unix environment?

Thanks.

Server jobs execute in what is effectively a virtual machine called the DataStage Run Machine. This is what you install as the "DataStage server" and is also used to execute job sequences. The DataStage Run Machine is written in a combination of C and DataStage BASIC.

Parallel jobs execute something called osh (for Orchestrate shell), which is the primary executable for the parallel execution technology that Ascential acquired when they purchased Torrent Systems. This is a "pure C" (well, C++ is included) environment.

ray.wurlod wrote:Server jobs execute in what is effectively a virtual machine called the DataStage Run Machine. This is what you install as the "DataStage server" and is also used to execute job sequences. The DataS ...

Thanks for the reply Ray.

But, how do we execute Server Jobs and Parallel Jobs under unix system command line?

Do these types of jobs require different executables?

Say, DSRunJob <args> is used for executing both types of job or something else for server or parallel job?

From the command line you use dsjob for all job types. DataStage figures out which executable to use.

ray.wurlod wrote: The DataStage Run Machine is written in a combination of C and DataStage BASIC.

I didnt know that C was used too. Good to know.

Primarily for the memory management aspects - there are no functions in DataStage BASIC for this. The STREAMS I/O module is used to increase performance of the Sequential File stage.

Anywhere you see a subroutine call (for example when stage tracing) where the subroutine name begins with "$" a call to a C function is involved. This, for example, $DSD.SeqPut() is a call to a C function, but DSD.BCIPut is "pure" DataStage BASIC.

Neat. Thanks Ray.