DSXchange

Kenny,

If target is DB2 then $APT_ORACLE_PRESERVE_BLANK is not required.

Could you please also confirm that value given in $APT_PAD_CHAR variable is 0x20 and not 0X20.

Thanks Craig, forgot about this possibility.

I guess you are looking for the usage of UNIX newline as record delimiter.

I guess, datatype of this field in source stage is also CHAR and you are using default pad character 0x00. That is the reason you are not able to compare it with null. Add $APT_PAD_CHAR environment variable in your job as job parameter and change its default value to 0x20. Then in transformer stage,...

this should have been worked...please specify datatype and nullability of this column in transformer and your target stage.

The target column is numeric.. and the scale is 10..Is that why it is loading 10 digits???

what is scale and precision of this field specified in target column?

if your IF conditions are finite, then create separate stage variable for each IF condition. Finally concatenate all stage variables in new column derivation.

and the HASH keys are like the columns Statecode,SPECIALTY_PRODUCT_INDIC etc, please explain it more clearly. Did you assign these keys as Hash Keys in datastage? Describe your job design as well and partitioning(if any) wherever mentioned. (how to run in single node if i had 2-node config file and...

equals to 1 here means that conditions(both) specified with the braces should be true.
Even if you remove '= 1' here, it should give same result.

not sure about this one, but I guess its related to NLS setting of your DB2 database.

Is there any other way to get rid of these special characters other than changing the datatype

Change $APT_PAD_CHAR value to 0x20 instead of default value 0x00 as job parameter

Please explain about your job design, then only we would be able to answer your query.

As far as I know its NO, but wait for some other replies as well.

I want to trim first and then check for null values empty string and null are two different things. If you are using modify stage just for this purpose, I don't think its a good idea. Moreover as you have mentioned that in source sequential you defined that column as nullable No, then in that case ...

I would also go with Kris and thinks that you are probably using transformation functions on this column without handling nulls explicitly.