DSXchange

I don't think 'plain' UTF-8 supports the Euro symbol. However Unicode UTF-8 does, I believe, and there seems to be a 'Greek UTF-8' as well:

http://docs.hp.com/en/5187-0701/ch09s08.html

A google of "utf-8 euro symbol" turned up alot of chatter on the subject.

"then prompt got changed in one box and throwing the above error in other box"

Sorry, but I have no idea what that means.

Sounds like you need to "source" dsenv first to make sure your environment is setup correctly:

Group change detection using stage variables in a transformer, constrain to only the first element in each group.

[first answer was more min() than first() unfortunately]

Magic post unhider.

You have an Oracle problem, not a aggregator problem.

We are still unclear as to the where and what. Is this coming from a script, custom routine, TCL command, something else entirely?? Can you post it, whatever it is?

[sigh] That cannot be the only error or warning your job logged. Also, when you Reset it is there a 'From previous run...' log entry added? If so, post it as well.

Then it seems to me you have a couple of choices. You can post the code so that someone who knows SQL Server (I don't) can perhaps spot an issue with the code or changes that may need to be made to support its use in DataStage. That or involve your official support provider. Or I guess wait and see ...

Exactly - they will need to write the changes out a new (updated) version of the flat file and then perhaps rename the new name back to the old name.

Zero isn't an error. What happens if you try it with just "-6" rather than a list like that?

Have you tried to use the (don't recall exactly) the "error handling" tab in the stage to let it know that should be a fatal error?

Sorry, but the proper thing to do is start a new post as this is completely unrelated to your original post, "special characters" or not.

"Since the abort is frequent" I too would suggest that simply automating the restart is not the answer but rather you need to rethink the Sequence job to run fewer jobs at the same time so it doesn't abort.

Define 'fails'. What does the proc do when there is a problem, does it raise an error or just log some error text?