DSXchange

Resist stupid requirements.

Make one export and make use of DataStage's ability to perform partial import of the contents of the export file.

To reinforce Craig's remarks, you may be in a part of the world where Friday and Saturday are not work days. But where he an I am, it is Saturday and Sunday that are not work days. And, curiously perhaps, I elect to have a life outside of IT.

Check (in Adminstrator client, logged as DataStage Administrator) whether the map MS1256 has, in fact, been loaded.

Doubt it.

Create sufficient columns to handle the largest possible number of values.

The column definition collection is a property of the LINK.

Does that help your understanding?

Can't do that, as we don't have access to your environments. YOU do the comparison of environments, and let us know. Pay particular attention to the environment variables that affect the behaviour of decimal data types, though the difference may be elsewhere.

It is not possible to include NULL in a string. As soon as you use NULL as an operand, the result is necessarily NULL. What did you have in mind here?

*Topic Relocated - Content Editor*

pandujoy wrote:if u r using DS8.1 or 8.0.1 ..go to the information analyzer and import ur log file...thats pretty easy

DSXchange is NOT a mobile telephone!!! Please DO NOT use SMS-style abbreviations.

Change the stage properties from UNIX style to DOS style. The character at the end of the file is most likely a UNIX end-of-file character (Ctrl-D). You can check this with any hex editor; its value is 0x04.

I've used svMaxLen as a stage variable rather than using 10 or 500 as a constant. Set its value in the initialization step and do not include a per-row derivation for it.

Have you named a "partition table" in your stage properties? You should not need to specify the PARTITION clause in the INSERT statement.

Try using a DecimalToDecimal() conversion.

That is a particularly difficult requirement. Most joins know in advance which columns are to be compared. Your requirement, if I understand correctly, is to find a match arbitrarily in any column. Neither a Join stage nor a Lookup stage can help you here, unless you perform every possible join/look...