DSXchange

VarChar(1) is a waste of space. Why not use Char(1) ?

If you're running 8.7 or later, capture this information into the DataStage Operational Database (DSODB) which IS fully documented in its manual, and you can create your own queries against it. (On 8.7 you need to create and configure DSODB; in version 9.x and later it's installed automatically.)

Try taking another export. Make sure (if you need them) that design data is included in the export.

Back in the day (when 8KB was a LOT of memory) I was taught always to complete multiplications before doing any divisions. Multiplication apparently suffers less precision loss than division.

As to whether you have a "solution" - only time will tell.

Welcome aboard.

Try enabling some of the reporting environment variables, particularly APT_STARTUP_STATUS and APT_PM_SHOW_PIDS, to get information logged about what's happening.

Yes, it can. But it's overkill, and jobs in the debugger run (necessarily) far more slowly than not in the debugger. You can also set the "compile in Trace mode" option in job properties. This effectively puts a Peek stage on every link in the job. This works whether or not the job is runn...

Version 6 - first version to include parallel jobs - support ended in April 2010.

Reminisce here.

Perhaps (for example) the parameter is a List type that accepts only A or B as its value.

I doubt it. It might get close, if your engine, services and repository tiers share the same machine. But a state file is right there in the file system.

You didn't answer my question. What's different between the environments? (Tip: the answer is not "nothing". Clearly.) Might there be a difference in the data, for example? The "" value does not occur in the file in dev but does in the new environment. Also, reading a single colu...

Or, to go completely overboard Then you get control of the rounding to some extent.

System generated block size should be OK unless you have some particular reason for differing. There is no convenient way to maintain state information in XMETA. (And that's not what XMETA is for.) Updating the state file from two different jobs is, at the very least, dangerous. But you can read (bl...

You can find ETLStats here when you're ready.

Use a server job, or a BASIC Transformer stage in a parallel job, to invoke the appropriate DataStage macros to retrieve the information in which you're interested. If there's no DataStage macro, use a DataStage API function.