DSXchange

OK, as long as your runtime environments are identical I could see that. Here, I would think a recompile and repromotion are in order.

Make sure all the Folder is picking up is the filename (not the contents) and set the XML Input stage to the URL/Filepath option. It will do a better job of reading the contents than the folder will, but there is still a size limit regardless.

AFAIK, both 'occurs' and 'redefines' are not supported.

How can we from so little information? Perhaps you got bad information from your client. Posting the actual errors would help. Also, verify you have connectivity to this 'preprod' database from dev outside of DataStage as well..

As noted many times here, 8.x does more stringent checking on things like this. Post your data and syntax, you'll need to correct it to avoid that warning.

Lots of discussions here on the Aggregator and floating point issues. One such example is here.

You are doing a good job of working through your issues... keep it up.

Let us know what IBM comes back with.

Out of all that, the first message seems to be the important one: Type: Warning Event: DB2_TbName,0: *** glibc detected *** /opt/IBM/InformationServer/Server/PXEngine/bin/osh: free(): invalid next size (fast): 0x09ddafd0 *** And a Google search for "invalid next size fast free" gets over 6...

Floating point.

So this message is from "sequence 1" or "the master sequence"? Does it only happen when the routine returns a 1?

What other error message are logged in any of the jobs? Post them complete and unedited, please. Also, what does the routine do and does it always return a '0'? A non-zero return is considered a failure in some cases.

And? Which issue would that be, exactly? There's more than one mentioned here. Not to mention that it is kind of hard to help you if you haven't given us any details of what you are seeing and what you have tried.

You've already done it. You 'modify DSParams file' 'in the Environment Variable window using DS Administrator Client'. He wasn't suggesting any sort of manual editing.

Sorry, don't know squat about Teradata but that U_TRUNCATED_CHAR_FOUND message we've seen here before from what I recall. Have you searched for it here? Did any of them help at all?