DSXchange

Just to be clear... using it will give you better performance in parallel reads and writes, though, if you have a partitioned DB2 database.

Try them both and let us know. Also, do you understand what 'DB2' as a partioning method does? Just because you have 'DB2 data' doesn't automagically mean you should be using it.

I guess.

Solve that problem first and then we can clean up whatever else was screwed up because of it.

No "buffers" in PX jobs. You can do that in Server but not here.

That error is specific to one particular job. Are you saying you can't make copies of any jobs?

My job abort when array size is set to 32767 for the source stage. (standard setting) That's your standard setting? :shock: Just because you can set a value to a high value doesn't mean it's a good idea to do so. That (IMHO) is a ridiculously large number. That is the number of rows it attempts to ...

Hello...did anyone go through a scenario like this? Rather than have no replies to your question, I'm going to post the less-than-helpful reply of "Sorry, no - I haven't or I would have posted something already". :( As for the 'bug in the tool' query, that kind of question should really g...

It doesn't sound like you want to pass it to a Job Activity stage since you're not looking up parameter values. I get the impression that you are overwriting the default values file for the parameter set and, if that is indeed what you are doing, then there's nothing to pass as far as I know. Just l...

Ah yes, the dreaded 'connect by prior'.

Yes, but you'd have to use a Server Shared Container to be able to do that, hence the suggestion to just do the whole thing in Server.

What I would look at doing would be writing a custom BASIC routine that leveraged DSExecute() to delete whatever filename is passed in. Then your Server job could source from your control table, filter on your status code and select the filename into your job. Then in a transformer, call the routine...

tbtcust wrote:this seems to be a solution I could use

Somewhat but now we know you have an 8.x/PX question unlike this 7.x/Server issue you posted into. And a parameter set doesn't really equate well to the User Variables stage. Plus you can decide when the issue is resolved over there. So... new post.

I'm planning to give the Datatstage V8.0 Certification I'm new to Datastage Aren't those two statements mutually exclusive, at least at this point in time? That 'stuff' you need for certification is called experience by the way. As in actually using the tool for some period of time and then getting...

Zafar wrote:There is a database on SOL server

So... 'SOL server' should really have said 'SQL Server'? As in that is the 'database' you keep mentioning?

Ironical typo, btw.

Hmmm... as Arnd noted right away, any records 'not inserted' get updated. Why? Because that's what you told it to do. And an error is generated only if both actions fail, the insert and then the update.