DSXchange

Your input is an unbounded string. DataStage is alerting you to the fact that this may (theoretically) contain more than 255 characters. That's all.

It's read 100,000 bytes without finding the first "|" character. It's assumed that your data don't match your metadata, and given up.

Maybe 365.249 as the divisor?

SwathiCh wrote:The column "Code" has the metadata defined as BigInt(19) at both the source and target.

Please check this assertion again. DataStage seems to believe that the target is defined as Integer.

There's a value (either a literal "?" or an untranslatable character) in the record type field, which the CFF stage does not know what to do with as it's not a value you have nominated as identifying a record type.

Yes, and you have paid for and licensed that part of it that supports communication between the engine and services tiers.

There wasn't much more, so I've unblocked it.

The client is called "DataStage and QualityStage Designer" (or Director or Administrator) whether you buy DataStage, QualityStage or both. The two products share the same set of clients. You should not have installed Information Analyzer, Business Glossary or any other products unless you ...

The NYSIIS() function is not supplied for the Transformer stage. But it is documented (on the web) and would not be difficult to construct as a parallel routine that could be called from a Transformer stage.

Instead of "DB2 UDB" put in the actual name of the database against the "Database =" entry in .odbc.ini.

Welcome to DSXchange. The short answer is yes, you can create rule sets for any purpose at all. The answer to the "how" question is, alas, rather longer.

So, to help future searchers, what was the resolution?

(It doesn't matter if it's something silly.)

Contact your official support provider. Can you create reports within Information Analyzer?

It's very unusual that, if the server was truly down, locks can continue to be held. Was it only the DataStage server that was down, not the Information Server? You may be able to find the defunct session using Web Console for Information Server (Administration tab, Sessions menu) and disconnect it....

Runtime Column Propagation should look after most of that for you provided that the target column names are the same as the source column names. And if they're not maybe you can create alias column names in the target table.