DSXchange

Give us an example. What path do you want to add to which system variable. IF you talking about datastage variables then in windows environment everything is controlled by registers as far as i know.

Not with Oracle Ray. Thats why its a pain to find what column is the culprit. It becomes more and more annoying if there are hundreds of columns.

Wow. Thats a first one. May i ask why do you want to automate such a thing? Just out of curiosity. You can write a dos batch. Google for sample dos batchs to get an idea of how its written. You execute them through command line. Within datastage, you would use DSExecute() routine to fire off a dos b...

chulett wrote:Two question marks would mean you need two columns. To do that you'd need to send the same batch_id in twice.

O yea. Totally forgot about that. THis is the pesky DRS stage we are dealing with. I guess the only other option is the second method i suggested.

Ok. I just built a test here and it works. Dont know what your doing wrong. Open your favourite sql tool and see if just the select count(*) from table where batch_id = 'a true value'. See if that works. Then put in your delete statement and put the count subselect in the where predicate. See if it ...

Do each of these 40 files trigger 40 different jobs or could be the same job? Give us more details. What is this job, is it a single job or a batch. Are there any dependencies between the files?

Do a search my friend. This has been discussed here before. Like thisfor instance.

You dont need to pass it. In your job sequencer, you can call this routine from the default value of the job parameter. Click on the Value Expression for your job parameter, right click and from the drop down list, choose DS Routine. Call your routine which passes the value you need.

Search this forum. You will get plenty of examples.

Only one warning huh..? I was under the impression that for every violation of rule there is a warning. Test it out. Build a sample job that has this violation in two columns. Send in 10 rows. And see how many warnings you end up getting.

OR try this sql instead. Delete from Table WHERE (batch_id = ?) AND (select count(*) from sysdp.dbo.SpData WHERE (batch_id = ?) >0 )

That conditional statement might not be working. Get rid of it. Do a lookup on target table on batch id. If exists only then pass rows to your target stage.

Technically the stage variable will be called for every single row. For small amount of records this execution time is negligible. But if you have millions of records it might make a small difference. Do this, keep the stage variable. Dont provide any derivation for it.For initial value, call the ma...

Ok great. Now since there are no more rows to delete and your passing a delete command, the sql statement is ending with a warning. Do this, do a lookup on the table on the batch id and constraint only the id that exists. This way a delete command will be sent for only the id that is present.

That is definately the problem. The error message tells you that

dsguy wrote:>##E TFOP 000481 06:42:57(008) <Oracle_Enterprise_49> Incorrect dboption list; it failed on Expected "," or "}", got: "$", line 1.

Read this post. I think its a bug and there is an ECASE out there for the same.