DSXchange

You can set the 'null field value' property for each field individually in the schema file.

Import of that file's table definition will probably yield VarChar, VarChar, Integer and VarChar. It's treating the file's content as data, not as metadata. You can not import metadata from a file of that format using DataStage. You can, however, create the table definition manually.

As a Suite Administrator open Web Console for Information Server. Under Session Management is there an active session with session ID '73965DC5-D89E-49D7-86DE-79D66796E38B' ? If so, you might try disconnecting it to release the lock.

The metadata repository does contain job design data. The design data are also still stored in the local project repository. It's not committed to the metadata repository till you actually save the job.

For the +-+ pattern, for example, load all three into PrimaryName1, probably without leading spaces and using original form (not standard abbreviation).

You have duplicates in your reference data set. Either enable return of more than one row from the reference input link in the Lookup stage, or ensure that you have no duplicates in the reference data set.

How about I re-phrase the expression slightly less efficiently? From that you might generalize to right space padding.

Search DSXchange for "vertical pivot" in server jobs. There are at least three ways, all of which have been published here.

ds_dwh wrote:how to rename multile job names.

One at a time.

The short answer is yes. They perform different tasks. One sets options to be used when compiling, the other sets options to be used when linking the compiled code. If you don't know what these terms mean, I suggest you do some research.

would have been so much easier. But you're in a parallel job, and this forum is for server jobs.

The client only runs on Windows. However you can export from the server using istool. (I don't have access to DataStage this week, but I'd also look in the DSEngine/bin directory for anything with "export" in its name.)

The error code has been returned from the Match Designer database. Check the test configuration. Check that the ODBC connectivity has been properly set up both from the client and from the QualityStage server. Research the meaning of the error code.

Quite possible (that there's a challenge). Latest versions tend to need latest versions. However, do try it - the Oracle 10 client is known to work satisfactorily with Oracle 11 database server (apart from the "new", or 11-only, functionality), so you never know.