DSXchange

Ok here is what i can offer. Load your file into a temp table in the same schema and run this query. Replace the table names and column names in my query. This is off of memory and is not tested. You might bump into a few errors, but they will be minor. As far as i can see it, its logically correct ...

Read the Designer Guide, specifically the section 'Job Activity Properties' under 'Job Sequence'. It will tell you how to assign parameter values to individual jobs within a job-sequence.

What is your database? Maybe i can help you write a sql query that does this for you.

Did you completely overlook my question ?

You can run a job sequence using the above command. But the parameter you pass will be for that job sequence. You have to pass those parameters down to individual jobs within the job sequence.

Or you can just give parameters as you would from command line. Narasimha, if i may,

A picture ='s thousand words. Did i get that right, i think i did. So yes, as i was saying, give an an example of your sample data, and what should be the output for each and every condition.

Keep it simple and visible. As Ray suggested, do it in two jobs. First one fetches the table name. Second one gets that value as a job parameter. Tie them together via a job sequence.

How exactly did you delete those files ???

Find out what the trigger is doing, try to implement that within datastage. This way you can keep your load and get the trigger's job done.

You should never kill a job thats accessing a database. Things like this start happening. Ask your dba to kill that particular thread, generated by your id.

That rest of Rays message said 'End of Story'. If you still dont agree, you will have to take this upto IBM. Nothing we can do. Use your favourite sql tool to view the data.

The connection between client and server does not depend upon that, as far as i know. All you need is the correct server name, username and offcourse, password. Your in.

Why is the data doubling? That should not happen. Try trimming the keys and then sending it in. What about at the database end, are the keys a surrogate number or a character key? Your seeing an increase in performance for 'insert then update' because there are more inserts then updates. The opposit...

Are you using the DB2 enterprise stage? What if you use the DB2 API stage.