DSXchange

Most databases impose a limit. From memory Oracle's is also 31 characters; ODBC's is 18. Sometimes this is a configurable default; sometimes it is a hard default. DataStage uses imported metadata and theoretically has no limit but, in practice, the category and table name must be smaller than MAXKEY...

1. Whatever you like. It describes target from source mapping at an individual target column level.

2. Whatever you like. It describes what needs to be run, and when, and whether there are any dependencies.

You must also ensure that the 32-bit libraries are found by DataStage processes - this means either removing the 64-bit libraries from the shared library search path (environment variable LD_LIBRARY_PATH, SHLIB_PATH or LIBPATH) for DataStage processes, or at least guaranteeing that the 32-bit librar...

Whenever a library can not be found it is probably your shared library search path (environment variable LD_LIBRARY_PATH, SHLIB_PATH or LIBPATH) that is the problem.

What did you do that was different, and fixed the problem?

You don't even need set - the second event in the job log shows all environment variables being used.

It's only greyed out when Immediate Purge option is selected.

You also need to prove that the timeout occurs in DataStage and not in one of the databases to which it is connecting.

In theory yes, in practice no. The internal structure of the table that contains table definitions is not documented, so you would need to figure that out before writing your routine. There can be more than 216 fields in this record, so it's not something for the faint-hearted to undertake. Further,...

HFC is indeed on the installation CD (DataStage clients), in the Utilities\Unsupported folder.

However, as Arnd says, don't concern yourself with this yet. Get the default hashed file populated, then see what tuning might be possible.

And please start calling them hashed files.

Search the forum for a server version of the IsValid() function.

Susbtituting what?

You never answered this question on your other post relating to this issue.

Please post the entire error message.

The repository for version 8.0 is no longer "DataStage Engine" - instead it is somewhere in the Information Server repository (DB2, Oracle or SQL Server). Anything you find in DS_JOBOBJECTS can no longer be guaranteed to be up to date or accurate. In version 7.5, DS_JOBOBJECTS and the other reposito...

Welcome aboard.

To process Chinese characters you must have an NLS map installed that can handle them; for example BIG5 or GB2312. And you must set the stage that is processing these data to use this map.