DSXchange

From what you are saying, the status in the end was not 'Aborted'. How do I go about fixing the job sequence to have an 'Aborted' status when a job in the sequence aborts? Seyed You will need to select "Automatically Handle activities that fail" with in the Job Properties of the Job seque...

Seyed wrote: Job Activity #1
Check Pointed

Job Activity #2
Check Pointed

Job Activity #3
Check Pointed
Seyed

Are you selecting "Do not checkpoint run" option within the Job Activity Stage? If so, uncheck it.

This can be achieved using a Transformer stage with the help of Stage Variables. One thing I am not sure about your process is where exactly your SK's are getting created. Before looking up against the Dimension table or after looking up against the dimension table. Assuming you are using the BusKey...

This can currently be achieved in Job Sequences within the Job Activity Stage where you can use Functions.

Some additional information such as how many records the table has, the many records the output SQL produces, how many columns you are trying to extract, if the columns you use in the where conditions are indexed or not will help us answer you better.

Within the Job properties of a Job Sequence you will have to enable "Add Checkpoints so sequence is restartable on failure" to see the "Donot Checkpoint run" with in the activity stage.

If the Job Sequence is restarted, it will skip the components that are not checked for "Do not Check point run". In the case you provided, whenever the Job Sequence is restarted it will execute the Command Activity component if the "Donot Check point run" is checked within the Ac...

Use to get rid of numeric values and vice versa.

This typically happens when Null handling is not done on the derivations within the Transformer stage that have some kind of transform logic built into it and the source value is NULL. For Example, if your derivation is something like Trim(field1) and if field1 has NULL values, you will have rejecte...

What partition do you have on your LookUp Stage. Because your LFS was created using Entire partitioning, did you use Same partitioning within the LookUp Stage. You can try that if did not already or you can also try setting the Preserve partitioning flag to Clear and run the job.

I have tried passing SQL statements as parameters to read data from tables but so far never to update/insert. But I am assuming it should still be similar for user defined update/inserts. Auto generated Update statements within the DB2 stage usually look like this UPDATE TABLE SET TABLE.COLUMN = ORC...

The OP's post and example indicates that the output is required only one column and not multiple columns. So, anbu's solution will work.

"/eeadm2/IBM/InformationServer/Server/Datasets/lookuptable.20100803.jm02qdd": No space left on device APT_BufferOperator: Add block to queue failed. This means that your buffer file systems all ran out of file space, or that some other system error occurred. Please ensure that you have su...

kpsita wrote:I can't use the sql as such because my master source is a file.Thanks

A solution has already been provided by anbu and myself.

Assuming your password is encrypted in your job properties, are you typing in your password there or are you referring it to an environment variable. Also, what DB2 stage are you using? API or Enterprise? Are you setting your password within the DB2 stage using #parametername# #$ENV_VARIABLE_NAME# o...