DSXchange

Another way to do the same thing. Is In your source column nullable = "Y" and target columns Nullable = "N" Use a If Then Else statement Like... If IsNull(col1) Then <default_value> Else (col1) This should also work. Sorry forgot to mention use the above in a transformer stage.

Another way to do the same thing. Is
In your source column nullable = "Y" and target columns Nullable = "N"
Use a If Then Else statement
Like...
If IsNull(col1) Then <default_value> Else (col1)
This should also work.

Not Nulls I have a situation where some columns coming in after a lookup against lookup filesets are Nullable = 'Y'. The current business logic does'nt help much to default them to a specific value implicitly if NULL. Rather, it performs a check greater then or + or lesser than for certain values on...

First Change the target column to Varchar. What is the length of the datatype ?
Then. let work on it.

define the target column as VarChar. Following is a sample logic that you can use:

If Right(Trim(y),3)[1,1] = '.' Then y Else If Right(Trim(y),3)[2,1] = '.' Then y : '0' Else y : '.00'

where y = Trim(DecimalToString(DSLink2.a,"fix_zero,suppress_zero"),"0","L")

fix_zero,suppress_zero
Should take care of suppressing all leading and trailing zeros. So is that extra care?
Thanks

Trim(DecimalToString(DSLink2.a,"fix_zero,suppress_zero"),"0","L")
How do "0" and "L" play a role here?

Im sorting data using Sort Stage. In the Sort stage Im using Create Key Change Column option. The keyChange datatype by default is TinyInt.
I need to use it as a calculation for a Integer and Decimal(9,2) type datatype target columns.
How do I go about the type conversion?

What does the fix zero and suppress zero do in type conversion.
Say we have 0.00 as a decimal. How does this play a role?
Thanks!

Im trying to perform a business logic where I sort on columns. Then I use the keychange column. Im trying to catch a column which is a decimal(9,2). If this value = 0 Then I say target column = keychange * -1. Now the target column is also defined as a decimal value. The keychange out of DS is TinyI...

Im confised about the way AGGR works. Lets assume we want to sort, group by and sum in PX with 2 CPUs. Say, we have a file Ename Empno Deptno Sal Mgr John 100 10 1000 102 Smith 101 20 2000 102 Eric 102 10 3000 102 Raj 103 10 2000 101 Tom 104 30 2000 101 Dan 105 30 1000 101 Drew 106 20 2000 102 We pa...

DS : Use hash mode for a relatively small number of groups; generally, fewer than about 1000 groups per megabyte of memory. Sort mode requires the input data set to have been partition sorted with all of the grouping keys specified as hashing and sorting keys. Im currently using Sort mode since I ha...

I am using Sort method in the AGGR stage.
DO I need to use a SORT stage before the AGGR stage and sort all the columns that I am grouping by in the AGGR stage? Is it permissible to sort all the columns in the AGGR stage itself that I am also grouping by.
Thanks

I am sorting by 36 columns, grouping the same 36 columns, partitioning by 3 of the sorting columns i.e 3 columns (sort+parition). Performing sum calculation on 7 other columns. I have not checked the key on any columns in the column window. Each time I run I have different no. of rows outputted from...

Im running DB2 as source and the PX job has a aggregator stage. I have turned the run time column propagation off. It still gives me this error AGGR1: When checking operator: User inserted sort "AGGR1.INPUT_REC4_Sort" does not fulfill the sort requirements of the downstream operator "...