DSXchange

Sounds like your VPN connections might be trashing each other's memory. I can't think of any other explanation. Viewing Log files does not (should not) perform writes of any kind on the server, unless server side logging is enabled.

Another thing that can cause start-up delays is a very full &PH& directory. You should regularly purge &PH& of old entries.

Good catch. Of course I know that the function says, internally, "if not specified use 0", but not everyone else does.

Use Full Outer Join

You have the alternative of accessing through SQL Server, for which there are UNIX-based drivers that ship with DataStage.

You also have the alternative of running DataStage on a Windows server rather than UNIX.

Wolfgang's design is sound. Don't forget that you may need to wait 110 years for the Cartesian product to deliver its result. Depending on the database you may also need to set an option to allow you to perform cross joins. For example in Red Brick you would use the SET CROSS JOIN ON; command.) This...

Well you'd better take on board the INTERNAL keyword for these commands, which captures the output into a dynamic array - no need to parse. I always SETFILE to my directory-based hashed files, so this (and other things) will work ok. And O/S files don't get locked by and large (except by OpenSeq), s...

Just "DMDY" means that the date's in month-day-year order, and Iconv can figure out anything else (delimiters, alpha or numeric month, two or four digit year, and so on).

Only if you explain in what way your post relates to the topic of this thread.

We do not answer questions posted on hijacked threads. Start a new thread.

The fail to match here is not about data - it didn't get that far. An Entire partitioning must always match if the key exists. The error message is "fail to match node". Did you create the lookup File Set with one configuration file then try to use it with a different one? It's probably not anything...

ProfileStage was formerly a product called MetaRecon that Ascential acquired. Its purpose is to look at your data without necessarily believing what the metadata define, in order to determine what's really there (hence "profiling"). It's tedious/tricky to get set up right, but once this is in place ...

There's no theoretical limit.

However, your job might rapidly become unwieldy and difficult to maintain if there are too many stages - irrespective of their type.

What do you consider to be "many"? Why do you think you need that many? Is there a smarter solution?

Don't use them where they're useless (like to connect to Oracle)?
Does that count as a "limit"?

Fix(number, precision, mode)

Mode rounds excess digits if 0, truncates if non-zero.

All this and more is in the DataStage BASIC manual.

Welcome aboard! :D Start by defining precisely what you mean by "performance", the metrics you use to measure it, what values you got, what values you expected (and why you expected them). Inspect the generated COBOL. It's not too bad, and in my experience reasonably efficient. Have you isolated the...