Because of the technical nature of some of the descriptions
in this manual, it sometimes talks about details of the engine that drives
parallel jobs. This involves the use of terms that might be unfamiliar to ordinary
parallel job users.
- Operators. These underlie the stages in an IBM® WebSphere® DataStage™ job.
A single stage might correspond to a single operator, or a number of operators,
depending on the properties you have set, and whether you have chosen to partition
or collect or sort data on the input link to a stage. At compilation, WebSphere DataStage evaluates
your job design and will sometimes optimize operators out if they are judged
to be superfluous, or insert other operators if they are needed for the logic
of the job.
- OSH. This is the scripting language used internally
by the WebSphere DataStage parallel
engine.
- Players. Players are the workhorse processes in a
parallel job. There is generally a player for each operator on each node.
Players are the children of section leaders; there is one section leader per
processing node. Section leaders are started by the conductor process running
on the conductor node (the conductor node is defined in the configuration
file).
IBM Information Server, Version 8.1
This topic is also in the IBM WebSphere DataStage and QualityStage Parallel Job Advanced Developer Guide.
