DSXchange

Output of the join will be up to 150 rows for each left input row. So you call the routine that many times from a Transformer stage, each time returning 0 (success) or 1 (failure). Sum these; if the sum is non-zero at least one rule was violated. Note that this is a difficult task to achieve with a ...

Does the user have the "log in as a batch job" right?

This one can be ameliorated if PWD environment variable is set to "." (current directory).

Before/after subroutines only ever take a single string as argument. DataStage can perform parameter substitution in that string. What you seem to be asking for is a cut-down expression editor for the input value field.

Category placeholders don't have a JOBNO value and therefore that is reported as 0. Craig's solution is the one to use.

Once you upgrade to 8.x DataStage includes its own performance analysis tool that reports on CPU, memory, disk and various other measures on a per-job and even a per-stage basis.

I certainly hope so. I'm about to set up a system with more than 30,000 Business Glossary users.

You create and compile the routine external to DataStage. Preferably you also create and compile a main program with which to test it. The "parallel routine" that you create within DataStage is not actually a routine - it is an interlude - a record of the existence, location and arguments ...

Create a routine that can be passed the logic, fields to be tested and, if necessary, metadata.

Re-open the WAS console and examine global security to see which method is actually in use.

kanasai167 is on Windows. There is no dsenv file for Windows. It's only for UNIX-based servers.

You need a wrapper. Take a look at the example routines. or something like: FUNCTION MySendMail(aRecipient, aSubject, aBody, aAttachments) vServer = "MyEmailServer" vSender = "MyEmail@MyHost.com" vString = vServer : @FM : vSender : @FM : aRecipient : ... Call DSSendMail(vString) ...

Works happily in IE8 and IE7 for me.

I forgot to mention that you can use your mouse to draw on the "frosted" screen with "let it snow".

When you import from XML it's a two-stage process under the covers - first the XML is converted into DSX then a "real proper" import is done.