DSXchange

As Stuart notes, the zero indicates the number of times the pattern-action is to be repeated. It must be followed immediately by an action that refers to operand [1]. So, in your example, the pattern is *Z (scan for the next class Z operand (delimiter)). If one is found, it will be operand [1] and t...

Are there #include declarations in any of the explicit header files you've named?

This is almost certainly because you have NLS enabled and Oracle is reporting the byte size (not the character size) for its VarChar2 and Char storage. If you just leave things as they are imported it will work fine.

Check that everything about the hashed file stages is the same in both environments, particularly the "lock for update" and cache settings.

And, if that's the case, it might be that you mis-spelled or mis-cased the project name. Project names are case-sensitive.

You would need a Transformer to calculate the intervals, then you could use a Pivot stage.

Use a fork join design, as already indicated. Search DSXchange for details about how to do fork join designs.

Do you need to escape the "%" signs?

What is the actual error message from the compiler?

Why does it matter what order the columns are named in?

For example, in some databases, best performance is had by physically placing all VarChar/VarBinary columns at the end of the record, irrespective of the order in which columns are named in the DDL.

OK, so you also use the environment variable to have DataStage write the schemas into the log file. This is a minor, but important, part of your solution.

What exactly do you want? A union, row-by-row concatenation, cross join, something else?

Are there any error messages in SystemOut.log that might suggest a failure to connect to the LDAP user registry?

Pivot Enterprise would seem to me to be the correct stage to use. What's your actual problem? Without creating a custom (Build) stage, you might be able to leverage the looping capability in the Transformer stage. In all of the above, I assume you are processing after the event. What you seem to be ...

My current site is running on POWER7 etc. However, the systems are managed by IBM and not by us, and they're very secretive about what they do. So we may or may not be benefiting from AME.