DSXchange

NullToValue() might be a better choice of function.

Convert() only converts character-by-character, so the function you specified would generate ">" not ">=". You need the pxEreplace() function.

Run jobs in Validate mode. This does everything except process data, and reports any errors. Indeed, this is the purpose of Validate mode.

Parameterize all pathnames. Linux identifier names are case sensitive; Windows identifier names are not. Compiler and linker options are different so beware if constructing Build stages, or using compiler overrides in the Transformer stage.

Just a few of the top of my head.

Yes. It only releases abandoned locks. But if you want to be more cautious, don't.

The test utility requires that the data and frequencies be in Data Sets.

When you get up to Match, you will find that both match stages require frequencies as input. So you have to generate them if for this reason alone. The test results database drives the interactive Match Designer test utility. You need to have created this database and an ODBC connection to it. What ...

Verify the input pattern that is generated. For example +// if there is only one word in the name. Parse the first token into PrimaryName and drop the two / tokens.

membershipdirector@dsxchange.com or membershipdirector@dsxchange.net

What's different about the servers or how they are configured or how Information Server and/or DataStage are configured?

"Nothing" is not the correct answer.

Set the variable in the environment of the user under whose identity the job actually runs when it's run from Designer.

To discover this identity, include a before-job subroutine ExecSH to execute an id command.

You might also consider if the format you gave is consistent. This expression is appropriate for the parallel or BASIC Transformer stages.

If you use a BASIC Transformer stage you have as a complete solution.

A round table discussion at IOD 2009 suggested that this figure might even be as high as 5 times the volume of data to be profiled.

Spend some time learning how parallel jobs are constructed and executed at run time. The Conductor process composes the "score" (another osh script) by combining the generated osh from the job design with information from the current parallel execution configuration file. During this proce...