DSXchange

What is your workaround?

Numeric value out of range usually indicates a metadata mismatch, for example you are trying to retrieve a six-digit number using a column defined as SmallInt.

Actually, Windows has far fewer licensing issues when using BCI functions because you can make the calls via the free ODBC drivers one tends to get on/for Windows systems.

Welcome aboard.

Did registering the plug-in complete successfully? Can you see your plug-in stage in the Repository?

What did your official support provider advise?

No.

One site at which I worked edited the log entry in an after job subroutine to mask the clear password.

The exception handler has two or three activity variables that report, for example, an error code and the name of the activity that failed. I'm travelling at the moment so can't check, but you can find them in the manual.

Substantial client differences, and substantial under the cover differences. Beginning in version 8.0, DataStage and QualityStage share the same Designer. There is no separate QualityStage engine; QualityStage stages become DataStage operators and these run in DataStage jobs (in line, rather than ne...

Curious. Was there any other activity in the database at the time?

None of that is relevant until you can successfully READ the Japanese characters. You need to establish how these are encoded in your source table, and set the mapping in DataStage to correspond to that. Based on your opening question, the target already uses UTF-8, but I'd check that anyway.

Tough. You specify 5000 records per transaction then your 90000 records will have been committed. You need to design your job differently, perhaps providing a "run identifier" that would allow you to undo the committed changes.

Start by correcting anything with a ##E token.

Also ensure that your APT_CONFIG_FILE environment variable contains the pathname of a valid configuration file (use the Configurations editor to check the file's validity).

Code page 1252 (US English) will not handle Japanese characters. You need to find out how the Japanese characters are encoded and specify the same mapping for DataStage to use. In this case, and provided that the source is encoded using UTF-8, you need to vary the source metadata.

Welcome aboard. The safest answer is "your mileage may vary". As a general rule best throughput is achieved by separating the data stream into insert-only and update-only streams, even though they're both into the same table. Consider making separate load modules for each, so that you can ...

I'd prefer to use one of the lookup functions in a Modify stage, for example lookup_int16_from_string().

It can be achieved exactly by DataStage. In addition to protection using separate group for each project, associate the Developer role in each project with that group. Then be careful who you put in each group.