DSXchange

Exact means exactly that. In SQL terms, the exact value of a column is its entire contents.

Take a look at the file RT_BP38/JOB.1510815895.DT.1582836700.TRANS1 in your project. The error may not actually be in the DEFFUN statement - it may be one or two lines prior. Line 0028 is merely the point at which the compiler gave up.

You might do better with a LIKE query, for example CATEGORY LIKE '%coverage_performance%'.

Fault types are documented in an appendix of the UniVerse Administration manual.

Have you successfully compiled your routine?

Nothing changes in DS_JOBS or DS_JOBOBJECTS when you compile. On import, jobs get new numbers - it may be this that leads to your "seems not updated". These two hashed files contain design time information - if your export contained only job executables, of course, they would not affect DS...

Then the DataStage job - that is, something in your job design - is doing something to convert these characters into Ctrl-Z. You will need to be the detective - it's not something we can do without access to your data.

This really belongs in a different thread.

DEFFUN declarations must precede any executable statement in the code.

Don't believe anything View Data shows you except for ASCII7 characters.

Try writing the data to a text file and looking at that, both with a regular view then, if that's "funny", with a hex viewer.

DataStage has a CDC stage that can receive the output from the Change Data Capture product. DataStage also has Slowly Changing Dimension stage in which you can treat updates as Type 1 or Type 2, or you can build your own logic using other stages.

Almost certainly not available in version 7.5, since it's not available in version 8.0.1.

Missed that. I'm more used to using Monitor to look at %CPU.

That'll happen, given your design, with the default (Round Robin) partitioning. No other partitioning algorithm, other than a key-based algorithmn based upon a unique key, will guarantee even distribution of records over nodes.

Why do you want to? 160% is an average of 80% each across two CPUs, or 40% each across four CPUs.

A signed zero is a very unusual thing.