DSXchange

Beware of doing that. DataStage will insert a tsort operator that may thwart your best-laid plans. Always use a Sort stage to specify "don't sort, previously sorted" if that's what you need to do.

Ditto - the Informix days, if I recall correctly!
:D

When you perform a normal (not sparse) lookup with a Lookup stage - with any other stage type than Lookup File Set providing the reference data - the entire reference data set must be read into memory and an index created on it (LUT_CreateOp operator) before any lookup can be performed. Populating a...

Version 8 doesn't always reliably record CLASS. Try with

If the incoming date is in external format with alphabetic month, you can use the Matches operator.

DS.REINDEX will not help; it indexes the local repository, not the unified (XMETA) repository. Clearly the problem in in XMETA.

Place this processing into the Input_Modifications subroutine and I think you'll find it works.

Does your command use any quote characters and, if so, of what kind? Can you post the complete command and parameters fields from your Execute Command activity?

Vista is not a supported operating system for the server.

Did you install the required C++ compiler before installing DataStage?

You probably need to delete the entry for the project from UV.ACCOUNT, repair the UniVerse system tables using VERIFY.SQL, and remove the entry for the project from the relevant table in the XMETA repository (the table with PROJECT in its name).

That's because it's not for a stage, it's for an inserted buffer operator.
This is an example of an alert message that it's safe to demote to informational using a message handler.

See my earlier post about DataStage roles.

... or use a server job, which avoids the overheads of a parallel job.

It means precisely that.

It's a cat command on Unix, type command on Windows.