Generated OSH Primer
Designer inserts comment blocks to assist in understanding
the generated OSH. Note that operator
order within the generated OSH is the order a stage was added to the job canvas
OSH uses the
familiar syntax of the UNIX shell to create applications for Data Stage
Enterprise Edition
1. operator
name
2. operator
options (use “-name value” format)
Schema
(for generator, import, export)
Inputs
Outputs
The following
data sources are supported as input/output
Virtual data
set, (name.v)
Persistent data
set
(name.ds or [ds] name)
File sets
(name.fs or [fs] name)
External files
(name or [file] name)
Every operator
has inputs numbered sequentially starting from 0.
For example:
op1 0> dst
op1 1<src
Terminology
|
Framework
|
DataStage |
|
schema |
table definition |
|
property |
format |
|
type |
SQL type + length [and scale] |
|
virtual |
dataset link |
|
record/field |
row/column |
|
operator |
stage |
|
step, flow, OSH command |
job |
|
Framework |
DS engine |
·
GUI uses both terminologies
·
Log messages (info, warnings, errors) use
Framework term
Example Stage / Operator Mapping
Within Designer, stages represent operators, but there
is not always a 1:1 correspondence.
Sequential File
_ Source: import
_ Target: export
DataSet: copy
Sort (DataStage): tsort
Aggregator: group
Row Generator, Column Generator, Surrogate Key Generator:
generator
Oracle
_ Source: oraread
_ Sparse Lookup: oralookup
_ Target Load: orawrite
_ Target Upsert: oraupsert
Lookup File Set
_ Target: lookup -createOnly