Example 1
In this example, all the input data will be included in the output vector.
The example assumes that the job is running sequentially. The column definitions
for the input data set are in the following table. The columns all have the same type and names in
the form column_nameN.:
Column name | SQL type |
---|---|
col0 | TinyInt |
col1 | TinyInt |
col2 | TinyInt |
col3 | TinyInt |
col4 | TinyInt |
The following are some rows from the
input data set:
col0 | col1 | col2 | col3 | col4 | |
---|---|---|---|---|---|
row | 3 | 6 | 2 | 9 | 9 |
row | 3 | 2 | 7 | 2 | 4 |
row | 7 | 8 | 8 | 5 | 3 |
row | 4 | 8 | 7 | 1 | 6 |
row | 1 | 6 | 2 | 5 | 1 |
row | 0 | 1 | 6 | 7 | 8 |
row | 9 | 9 | 6 | 4 | 2 |
row | 0 | 8 | 4 | 4 | 3 |
row | 1 | 7 | 2 | 5 | 3 |
row | 7 | 9 | 4 | 7 | 8 |
The stage outputs the vectors it builds from the input data in a single column called col. You do not have to explicitly define the output column name, IBM® DataStage® will do this for you as the job runs, but you might wish to do so to make the job more understandable.
The Column's Common Partial Name property is set to 'col' in the Properties tab.
The output data set will be:
col | |||||
---|---|---|---|---|---|
Vector index | 0 | 1 | 2 | 3 | 4 |
row | 3 | 6 | 2 | 9 | 9 |
row | 3 | 2 | 7 | 2 | 4 |
row | 7 | 8 | 8 | 5 | 3 |
row | 4 | 8 | 7 | 1 | 6 |
row | 1 | 6 | 2 | 5 | 1 |
row | 0 | 1 | 6 | 7 | 8 |
row | 9 | 9 | 6 | 4 | 2 |
row | 0 | 8 | 4 | 4 | 3 |
row | 1 | 7 | 2 | 5 | 3 |
row | 7 | 9 | 4 | 7 | 8 |