DSXchange

There aren't any.

DataStage will report the number of rows it sends along a link, and the number of records rejected. You might be able to perform arithmetic on these numbers to deduce the number of loaded records.

Nah. I've often worked with string[max=4000] and sometimes even larger.

If you're asking about the maximum size of a CHAR data type in a database, the answer to that is that different databases have different rules, but 255 is a common limit. That's why they have the LONG... data types.

If they're still in use, no. If they're not still in use, yes.

Probably be next week before I get a chance to play with it. This week's work is on AIX, and in my copious free time I'm taking a class in the 8.1 Foundation Tools.

These are the weights you see in reports and in the Match Design tool.

is it good way to delete the log files from (/opt/IBM/InformationServer/Server/Scratch) to readuce the space issue i.e we get the error message Operator terminated abnormally: received signal SIGBUS No. They are unrelated. Do an Internet search for SIGBUS. But it IS a good idea to keep the scratchd...

Lots. How much memory do you have?

The message text associated with message ID CONN-NGBR-00002 can not be found. That DSHOME is set should be sufficient. It may simply be that this message is not in the resource table. Not all messages are in the resource table. Are you using English or Portuguese? Time to annoy your support provider.

I'm still curious. Would you be so kind as to post the previous iteration of CompareFiles routine?

Seeing this in an 8.1 brand new installation (on AIX). Trying to track down which of the "-s" entries in ds.rc is causing the error.

It may not be possible. It depends on your data. For example if there are many records with same birth month and first name, then you will tend to get overflow used in pass 4. There's a similar argument for pass 7. Match will still work when there is overflow - it just won't be as efficient. If the ...

Examine the aggregate weights and set your cutoff values accordingly.

The job is running - it started at 23:25:04.

At 23:25:14 an attempt is made to start the job again. This attempt fails, throwing (correctly) "job not in correct state" error.

The job that is still running finishes at 23:26:33 and it's that one whose successful completion is reported.

I don't know whether U (one of our posters can get you the solution). Why not send U an email or private message? The format string "%hh:%nn:%ss" expects two digits in the hour component. I mentioned that before. Your data only has one. You need to handle that with a different format strin...

Download ETLstats from Kim Duke's website rather than contemplating reinventing the wheel.