DSXchange

I'm curious how that is "not good for the design". Or how putting a zero in a CHAR(40) is an appropriate represention of an empty string field. :? In my opinion, what you did is not a workaround but rather the solution. The fact that the warning is now gone should be a big clue, a 'workaro...

If you're going to quote people or otherwise make use of the [tags] that are available here, make sure you do not check the "Disable BBCode in this post" option or they won't work... as you can see in your reply.

However, when I try to load the single character into the database, it rejects the reject. Rejects how, exactly? Can you post the entire message? Yes, UTF-8 is a "multi-byte encoding" character set. Certain things like your umlaut can cause it to need two (and other things even three) byt...

Sometimes known as an "O-with-dots", the dots are a diacritic mark known as an umlaut or diaeresis or trema as well, it seems. So "O-umlaut".

Is your install "NLS enabled"? Assuming yes, but need to double-check. Also what stage are you using with DB2?

True. The "separate line" part could be handled in DataStage by converting the Field Marks to nothing which would pull all the lines up into one and the last delimiter could be sub-stringed off. You could probably do the same thing with multiple invocations of 'sed'... or you could write a...

You don't "run" it like that, you're missing a "dot space" in front:
That's how you "source" the file, btw.

How much UNIX experience do you have? Or any other command line O/S for that matter? You either need to make sure the directory the command is in is in your $PATH or that you fully path the command or (in this case) since you're parked in the same directory it lives in, stick a "dot slash"...

Silly thought, but why not use sed to add a comma (or whatever) to the end of each line?
Results would go to stdout and thus easily picked up in your UserVariables stage.

However, the message 'table not found' indicates that either your hashed file doesn't exist or your environment variable isn't resolving itself properly. If you're certain about the former, check the latter.

Both issues are addressed in this post:

viewtopic.php?t=117081

Search the forums for "ParamValue/Limitvalue is not appropriate", this has been discussed here quite a bit.

Actually, you'll need to create new entries there for this.

Please mark the topic as Resolved using the button at the top of the sreen.

What have you tried? And for the example that you posted, can you please also post the expected output, showing us what each file would need to look like after all the shenanigans?