DSXchange

Actually, I thought you need to do the exact same thing in DataStage... did you try it? What happened?

Convert(",","",YourField)

Replaces all occurances of the first argument with the second, in this case commas with an empty string.

Spamming my personal email isn't going to help you out here, I've already added my two cents. Everything else is up to the people that actually run/own this website.

Have you tried using the 'Contact' link at the top of any page? Sent anything to any of the people listed there?

What is the target field's data type? Again, if it is any kind of "integer" as you've said then commas are not possible.

Since they're just character strings, substring. Or take the long way home and use StringToDate() followed by DateToString() with appropriate masks.

For a "registration" problem like that, I'd suggest uninstalling and then reinstalling the client.

No need for an intermediate file/table, simply use your command of choice in the Filter property of the stage.

Exactly... why not dump the proc and use that SQL 'like normal' in your DataStage job?

ray.wurlod wrote:Note that this limit is imposed by your mail client, not by DataStage.

Which is exactly what I meant, should have been a teensy bit more specific it would seem.

By which I meant you just simply convert them to integers and load them. Don't worry about the commas part, that's all about how they get selected back later as a character string, all about the external format.

Search the forums here for a significant portion of your error, like " the source decimal has even precision, but non-zero in the leading nybble" and you'll find 14 other times people have seen this one. Some are even marked as resolved, check those first.

We know that - post the actual derivation. That way we can see if/how you are trimming out the formatting characters, our guess right now is that you are not.

I'm assuming it is more complicated than that. Laura, are you saying that you need to check all values for a key and then you can decide what values to assign to the second column? Almost like two passes through the data? If so, seems to me some kind of 'fork join' design would work here where one s...

OK... 65 is nothing. &PH& is the phantom directory and 'phantom' means background process. Every job creates files there that it uses to communicate its status back to the engine, so having them there is perfectly normal. Now, if you had 65,000 files in there I'd be worried that writing to t...

Also tell us how many files are in your &PH& directory.