DSXchange

No, it's not. Each action should be a separate link from the transformer to a single (not multiple) target database stage, each link with its own discrete action and table. No need for any silly user-defined shenanigans. This assumes all target tables are in the same database 'instance', of course, ...

Why go back and query the repository every record, which is what the macro does, when you've already got the value you need in a system variable local to the transformer?

(if it starts with '@' it is a system variable, check the online help)

What activity? What message? This is how you pull (possible) additional diagnostic information from the phantom directory into the job's log. Saves having to go fish it out yourself. If this is Resolved please mark it so using the big button at the top of the page and let us know what the heck the a...

... and without the grep:

ls *Data*

Ok, thanks for letting us know.

Is your response in XML? If so, there should be an option to convert those nulls to an empty element rather than exlude them, I believe.

Please answer the second question.

But would there really be a character with a value of 2019? Base anything?

Hmmm... I guess so, from googling around a hex 2019 (dec 8217) is the Unicode character name: RIGHT SINGLE QUOTATION MARK.

I'm sorry but how is "12,65,16,54,66,361" any kind of an integer? How did you select this value?

You may not have properly identified the character - and the CHAR() function needs the decimal value, not the hex so that's probably the issue now that I think about it.

No clue as you haven't let us know what database you are using for XMETA storage, nor provided any samples of what they look like.

You have to either convert it to a 64bit hashed file, search here for the RESIZE command, that or create it as one manually with the -64BIT option. It cannot be done through the GUI.

Is that different from the characterset of the source DB2 database? How are you determining that they are wrong in the target, how exactly are you checking? Something outside of 'view data' I hope.

You wait and they clear themselves in a few minutes. If one is well and truly hung, an SA would need to do something.

You can't inline them like that. Try something more like:
Note the five spaces in the 'convert to' list.