DSXchange

Are you sure you're referring to the correct procedure? After all, the one you posted does not contain "OFF".

The new migration tool, initially supplied through the Concierge service but now generally available, also picks up environment variables.

No real limit. Try it. It works.

Why aren't your friends asking these questions?

I believe that, properly tuned, a hashed file will always be more efficient at performing lookups than any other method available to server jobs.

There are two uvodbc.config files, one in DSEngine, the other in ANALYZERPROJECT. Have you mentioned the DSN in both?

It's not usual.

Resist stupid requirements. You can't do it without sorted data. And that implies properly partitioned data.

Full outer join, set flag to 'Y' if both key values are not null.

The right approach is not to touch DSParams programatically.

If you feel you really must (why?), make sure that the routine preserves the previous (last known good) version.

Same place(s). If the ANALYZERPROJECT project has a uvodbc.config file make sure that the DSNs are mentioned in there.

I received an email from my ADMIN team as above yesterday. is it true? We believe you. So it is true (for some value of true anyway) that you received an email from your ADMIN tram yesterday. As to its assertion, I would be asking for proof. Surely it would depend on who wrote the routine. A well-c...

How are your triggers set? What caused Job3 to run in reset mode?

Set up a unique sort on the input link to the Transformer stage.

But it's a silly requirement to want to do this in the Transformer stage.

It uses whichever configuration file is pointed to by the currently set value of the APT_CONFIG_FILE environment variable.

Until you can document a business rule that unambiguously can identify dates of different formats (such as how James suggested) there's nothing more I can add. 12150615 and 15061215 are both valid, but maybe your data don't deal with dates that old.