DSXchange

I wonder whether the Greenplum ODBC driver is compatible with the Data Direct ODBC driver manager?

TMPDIR environment variable. This is available via DataStage Administrator client.

... which suggests that a node pool may be involved. Or that the Data Set was written previously using a different configuration file (with three nodes) and this job is running using a single node configuration file.

Too complex. Field(Convert(svTab, " ", InLink.TheString), " ", 1, 1) would do it.

I'm not really sure what you're asking. The traditional way to pass multiple values via a single parameter is to use a String parameter and pass a delimited string of those values. The better way may be to use multiple parameters.

Possibly you could use grep -v ^\# as the first part of the pipeline, to eliminate lines beginning with "#".

Field() function.

Convert tab to space.

Your compiler is not set up properly, probably environment variables. There are other current threads on this issue.

Range lookups compile to transform operators, which is why the compiler is required.

Divide SellingSource using Field() function and use each field in its own lookup against DID_DLR_ORG_DATA.

All possibilities are discussed in the manuals. Not all stage types support all values.

Each stage type has its own chapter in the Parallel Job Developer's Guide. In version 8.5 and later an obvious difference is that the Transformer stage supports Loop and the BASIC Transformer stage doesn't. Another difference is the number of tabs in the stage properties dialog; in version 8.7 there...

There's only a join availabe to DS_JOBS when CLASS = '2'. In that case there is a join between DS_JOBS.NAME and DS_AUDIT.INSTANCE (In later versions class '2' includes things other than jobs, but that does not invalidate the above statement.) That said, it appears that in version 8.7 that audit info...

Maybe and possibly.

It depends whether or not that I/O is related to DataStage projects or to something else on those file systems.

You can read about DataStage BASIC match patterns in, curiously, the DataStage BASIC manual.

OK, you ran out of table space. That would certainly do it. I prefer to over-allocate table space initially, and set it for automatic growth.

That does not mean that you can miss monitoring table space. It's something you should do with ALL table spaces. DBA 101.