DSXchange

Right, mentioned those as viable avenues. What about it didn't work as expected?

It's a BASIC function so you either need a Server job or a custom Before/After routine to call it, that or a Server Shared Container. That being said, you should be able to use it on a Parallel job.

I would suggest you not care. Have you talked to your DBA about this? You have absolutely not control over what 'block' Oracle decides to use and I honestly don't know why you would even be worrying about it.

Otherwise, could you please explain how 'this is causing problem'?

In other words, changed 'less' to 'more'... gotcha. So, not crazy.

That's one answer.

Ok... perhaps it's early yet for me but isn't #3 backwards? Enabling disable combination (setting it to true) could get you more steps, not less... i.e. the most possible steps since nothing can be combined.

I've done that without issue... what kind of problem are you seeing?

The same way you'd do it without DataStage. Do you need help with the 'in DataStage' part or the actual scripting?

OK, that helps and is exactly what I explained how to do. Your job parameter needs to be appropriate for the actual value, nothing about how the parameters are passed will resolve things twice, so to speak. So... use a Sequence job to do the 'cat' and capture the output, then pass that output in as ...

Still unclear, I'm afraid. However, your "I want to take" declaration is something I do believe I explained. If you don't agree, please be more specific... perhaps a fully fleshed out example of what you are trying to do would help in that case.

You could also generate a row with 'somedate' in it and then use that in your target stage to do the delete. Or generate the row and slip your 'somedate' job parameter into it before the target and issue the delete.

Several ways to skin this cat.

Compiler in dev, runtime everywhere else.

... and then there's this if (perhaps) you are talking about Parameter Value Files. If you have a file with values in it that you want to bring into a job as Job Parameters then you'll need to read the file in some fashion and capture the output to pass in. It could be as simple as 'cat #filename#' ...

Hmmm... does the service accept any kind of 'bulk' processing or is it strictly singleton calls?