DSXchange

It's set by the Quote Character on the Format tab. Make sure it is set to an acceptable 'quote' character (like ") rather than "000" which means "no quotes". That or strip the pipes from the data if that's allowed / acceptable.

Then you''ve got a delimiter issue. For example, your file is comma delimited, there are commas in your data and you are not quoting strings. That or you're wrong about the metadata.

OK. Clarify for us what "improper and junk data" means. Post examples of what you think you are writing out and what "junk" you are finding. Also check from UNIX rather than DataStage, how does it look there?

Assuming you can. We still don't know the reasoning behind 'needing' three separate stages or the serial processing.

Two problems with your "conversion". First, no "toDate", leave it as a string to play this game. That or use a StringToTimestamp() with the proper mask after adding the zeroes. Second, just cat on the " 00:00:00" in once piece, no need for everything to be separate like...

So... you have this error reading the file you just wrote? First triple-check and make sure your file pathnames, options and column metadata match. And undo your 'Incomplete Column' attribute change, it doesn't work that way.

ps. It's not urgent.

No, they will always run in parallel. Again, why three separate stages? Is the metadata different? Can you not read all three in a single stage using a File Pattern?

No. It might help to know what's in these three input stages, however, to determine a best course of action for you.

And... you've tripled-checked the 'connect identifier specified' and are positive that all is good there?

Sure, you never know what people have or haven't seen before, so it's always worth a shot.

Thanks Andy, I had to get out the door and have zero internet access during the day, so figured someone would have my back.

Terrible requirement. What exactly is this script doing that it needs to run for every row?

This is old enough I don't really remember what I was thinking of when I said I've "seen this". :? Regardless, please start your own post. This lets us know your version of the product and your O/S and gives you the ability to proclaim the issue 'Resolved' if we get that far. When you do, ...

OK, with that I would suggest taking it to your official support provider. Perhaps this is a known change in behaviour with a known resolution or patch.

... and yet you need to get output? Hmmm...