DSXchange

What is the target datatype for CLAIM_ID.This also need to convert from Nullable to not nullable

In a sort stage sort on A(Ascending) then B(Descending) and C(Descending).And hash partition on A.Now use a remove duplicate stage on the basis of A.You will get the maximum occurrence.

I have desigened the whole job in the following way. Seq_Super I have two jobs job1 and job2.In both of the jobs I have ticked Do not checkpoint run option. Again I have a sequence Seq_Sub where job3 and job4 are there.For both of the cases I have unticked Do not checkpoint run option. Now I include...

I have a sequence job with the following design Job1----->Job2----->Job3----->Job4 My requirement is if Job1 or Job 2 aborts then the sequence job will start from begging.And if Job3 or Job4 aborts then the sequence job will start from the aborting point. I have checked Do not checkpoint run for Job...

Yes,am also searching for the same

What is the WAVES concept in datastage?How it helps to improve the performence?

You can do the both look up in continue,continue mode.Then in a filter check 1 and 2.If anyone of these satisfy then record will be passed.

1. After extraction of b add a transformer and default a colunmn say COL1 with some default value and declared as nullable yes 2. Then first look up with a an b with a as stream and set both as continue. 3.Look up the record set with with c.In the look up condition gives COL1 is null.And set the opt...

1. Make a union of Id from Table b and Table c in your extraction query.
2. Lookup Table a and the above extraction and mention lookup condition not matched to failure.

Are you using Upsert method or you are doing insert and update seperately in different stages

Is there extra patch that needs to be installed to avoid this situation

I have a parallel job with the following design Dataset----->surrogatekey------>target DB2 table I am using DB sequence as surrogate key generator.The user with which the job ran was not access to the particular DB sequence.So the job got fatal error.But instead of aborting the job it has been finis...

If you defined stage variable like following way

sVar1
sVar2
sVar3

Then the order of execution will be sVar1 then svar2 then sVar3

Is the field on which you are checking null is varchar ?

In this case IDENTITY is user defined column can be created in a transformer stage.So in that case for every incoming record assign it's value to 1.Then in spite of being a not null column this field will not contain any null value.