DSXchange

Add extra file systems to resource scratchdisk.

Is the record delimiter (that you have shown as "Z") also a linefeed?

Then the routine is not the cause. Is your compiler licence still valid?

Suddenly we're talking Wrapped rather than Build stage? Does a Wrapped stage even need separate compilation?

It's all too much. Use a simple test command, and create both OK and Failure triggers from the Execute Command activity.

The value that represents null must, for certain data types and for fixed-width format records, have the same number of characters as defined for the column. For example, for a date in %yyyy-%mm-%dd format (ten characters) the null-equivalent value must have ten characters, though it does not have t...

Without understanding your definition of "performance" in an ETL context your question is impossible to answer.

Is opt/SUNWspro/bin/CC installed and licensed?

Not necessarily. But it does incur overheads in translating to and from the typeless environment of BASIC.

Why not just write all the results to one file, then use a UNIX (MKS Toolkit) split command to divide it into separate files each with the appropriate number of lines, which you can process with script to load into Siebel?

Actually it's tmp (not Temp) that has to exist, but only if UVTEMP or TEMP environment variables refer to /tmp. And it has to exist on the drive on which DataStage was installed, which may not be the C: drive.

... and, indeed, the APT_ORCHHOME environment variable.

Can you change the ReadOnly setting in the export file before importing the routine?

You have no columns defined on the input link.

But you have one parameter marker in the SQL.

This is not a correct combination, which is what the error message is telling you.