DSXchange

Yes, what about the 'Universe' repository? Does that not need to stay in sync with XMETA?

Why did you feel the need to change the sql? What happened when you ran it with the generated sql?

Visual Studio 2008 is not supported - 2003 and 2005 are, from what I recall. Check your documentation.

Where is this output data and how are you looking at it? That "dot" may very well just be an artifact of the View Data option and not actually in your data.

SIGSEGV is a Segmentation Violation signal, more of a coding than a resource issue. Did you try search here for that message? What is your job design?

The invalid character is noted in the message - a hex FD.

You'll be fine simply clearing the hashed files.

Yes, over and over and over.

Details, please - did you install a supported compiler? What are your compiler and linker APT variables set to? Is this a problem with any job with a Transformer stage or just this particular job?

It's a utility that you call from the "command line" - meaning the O/S level - to run scripts in your database. For Oracle it would be sqlplus but no clue what it is for Informix. As noted, have a chat with your DBA, they should be able to get you all squared away.

That's really a question for your Informix DBA. What command line utility do they provide for this?

Check the Transaction Handling tab.

Yes, in a transformer. And there's no reason to avoid the transformer for "performance reasons", those days are long ago.

Preserve Type exists as an option in the 7.5.2 release. You also have the Default to Decimal Output option that may help as well.

I don't believe so. Check upstream using the IsValid function and reject them before the Modify.

Temp as in "temp" or temp as in "tmp"?