DSXchange

Craig meant to link to this thread.

Try using an EXISTS test on col1

The CD command does not "carry through" - you need both commands in a single Execute Command activity with either a ";" or a "&&" between them.

What does "not working" mean here? Depending on the data type, both of the expressions you provided are valid.

For the HASH values Trim the leading zeroes and the trailing sign.

For the FIN values divide the HASH values by 100.00.

If you have the score from a recent execution you can re-build the job design in its entirety.

It would appear that the problem is coming when the Lookup stage is preparing the reference data set or the index on it though I confess to some confusion about the word "export" in the message. What are the data types of the key column(s) on both the stream input and reference input links?

You could always contact your official support provider. DSXchange is all volunteers, who post if and when they have something useful to add. Sometimes "think time" is required.

Basically you have to be a detective, and work out what's changed.

Indeed, the Data Rules stage is available in version 8.7.

Check whether the password to the XMETA database has expired, and whether the WebSphere Application Server instance (server1) is running.

Why not use either the old XML Input stage or the new XML stage?

You could use Before/SQL to issue a DELETE statement (or even TRUNCATE if the database supports that).

Use arithmetic (including Int() and Mod() functions) to extract the "year", month and day, add 1900 to the "year", then use DateFromComponents() function to re-assemble them.

No you don't. If you have pipe-delimited then at best it would be CLOB.