DSXchange

Only for external routines.

Remember what Kim advised about modularization? This is one of the reasons why.

Here is another argument.

foo = "DSU.MyRoutine" Call @foo(Result, other_args) The technique is called "indirect call". And it's in the DataStage BASIC manual. I've used it in the past to create data-driven business rules validation. For functions the first argument position is reserved for the return val...

A regular server job with code posted into the Job Control tab will suffice. A Batch style job is the same thing, but created in Director (which means it gets "Batch::" prefixed to its name and it gets compiled automatically). Batch is a way to allow operators (who don't have access to Des...

You can copy blocks of lines from one DSParams file to another. Try to preserve alphabetical order within sections in the new DSParams file.

I like it. So when you talk with support you quote version "8.1 with fixes to the installer", or "8.1wftti" for short.

Currently on 8.1.0.0 and there's nothing executable with "export" in its name on the server side.

Export the old project, create the new one empty and then import the old one into it.

Did you look at one node of two, perhaps?

Thanks for that. IBM are currently setting up the grid, will just have to wait and see (and test).

It's not too great a step from "dynamic" to "dynamite". Beware trying to do anything "dynamic" in what is designed to be a metadata-driven tool.

As noted elsewhere recently, the local repository is not used for table definitions at all. They are always in the unified respository in version 8.

Use stage tracing (from the Tracing tab of the Job Run Options dialog) to capture statistics about the Transformer stage(s). Since you have provided no information about the job design there's not really much advice we can sensibly give.

Hmm...

Resolved already. How?

Partitioning not right?

Please edit your previous post, surround your code with Code tags (to preserve the indenting) and disable smilies before clicking Submit.