DSXchange

You mean something like this

So if i have understood your requirement correctly, the number of times a particular record will be inserted will depend upon a parameter value. Correct? A couple of ways, -look into the start loop and end loop activity in a sequence job. Run the same job n number of times -build your load ready fil...

I did not use any code to open the file like OPENSEQ. Ray suggested OPENSEQ if you want to use the STATUS command. This command will tell you if your file is of zero bytes or not. But you want to get the row count on a particular link using DS functions. So basically you dont need OPENSEQ command. ...

Try this

Welcome as in "Congrats in gathering up the courage and posting your very first message".
And o yea one more thing, "I saved a bunch of money by switching to geico"

What do you mean not respond? No effect at all. What about through the command line? When you go into the dirctor, whats the jobstatus there? Any funny log file messages?

What function are you using. Z in the field means its a signed number. The only function available for signed functions is DataTypePicS9().

Check out this post.

Welcome Aboard As Kris mentioned, you will need to write a Basic routine to handle this. Look into your BASIC guide and search for the STATUS command. Your concern will be the 6th field in the dynamic array that the STATUS command returns. Something like OPENSEQ Arg1 TO myfile ELSE CALL DSLogWarn...

First , does the batch script run when datastage in not involved (from command prompt).
If yes and you are absolutely sure that its not working from within datastage, then throw in info messages after every few steps to see where the script is breaking and why. This way you can debug it.

kcbland wrote: you're best to segregate extraction and loading processing not only for simplicity, but for ease in tuning, restart, etc.

Kumar i think the strongest reason is for modularization and restartabilty.
My 2 centy.

If you want to keep everything in datastage, then go for Ken's suggestion.

Here, take a look at this page on why that error occured and what to do to fix it.

Welcome aboard Ram This is something that you want to keep outside datastage. Write a small shell script. That will get you going. From the top of my head, something like #!/usr/bin/ksh awk -F"|" '{ print $1 }' myfile.txt | sort | uniq > uniqfile.txt cat uniqfile.txt | while read...

What is meant by him is that re-design your job with a different logic. You are trying to insert a duplicate key which has a unique key index. This cannot be done. It would be only assumptions by posters if you donot post your job design and provide more information on it.