DSXchange

ArndW is right. Try to perform all the tests outlined by other posters. Also, dont forget to tell us what do you see in the message file other than the commit info.

You dont even need to set the TS parameter with the macro value. You can use DSJobStartDate with the file name directly surrounded with #s.

Are you controlling the process of passing parameters via unix script. It will not work. That was one of the main reasons why we had to contact ascential and they are the ones who asked us to pass the encrypted password.

It was worth a shot. Well, try doing an exact search on 'Unable to convert the adapter spec '. Its revealing 2 more posts. Read through them, it might help.

Are you doing INSERT or REPLACE? Try with an even smaller count. Like say maybe just 10K records. Also when the job gets hung. How do you kill the job? DB2 is a real pain. Stopping the job by director will still leave an alive thread to the database. Do this, call you DBA, ask him how many threads a...

I dont see any where predicate in the sql. Dont you need to define a key for the update?

The commit size is provided in the property 'Save Count'. And the property where you have to give the fully qualified name of the message file is 'Local Message File Name'. Set indexing mode to AUTO_SELECT. After making these changes. Run for maybe 100K records and see if it works. Start with a low ...

What about macros. In server, Instead of TS, you could have used #DSJobStartDate#.
You cant do that in PX ? I dont have access to PX at the moment or else i would have tried it out.

Exactly. Thankyou Kumar.
This also helps protect nosey developers from going in and getting the true password. But if you try to pass the ecrypted password from Designer or director, it doesnt work. Isnt that cool

Well. How are you going to control the sequence of your entire process. If at the end you are using a unix script to call a bunch of different jobs or call one Master control sequence job, do as kumar suggested. Set the warn limit to 1. This will take care of your situation. The dsengine will force ...

What is the exact warning message you are getting the log file?

Thank you Craig for the backup (not on the cukoo part ).
Sainath, if your input file is whatever you have shown in your original post, my solution will work. Otherwise as requested, we need the snapshot of the original input file.

Great. Thanks guys. Just wanted to clarify whether it is possible to do deletes using a universe stage. I have never done it myself, but since i was sure that sql statements work on in account hashed files, and delete is a sql statement. So wanted to know if that is possible.
Cool, thanks guys.

Craig, cant he access the hashed file with universe stage and supply a delete command ? wouldnt that work ?

Well there is a change in your key column. From your sample data, your key changes from k1 to null, again to null before it hits k2. My solution will work if your input data file is exactly like the way you have shown. If it is different then you need to give me the exact snapshot of your input file...