DSXchange

The new tool in 8.1 (Information Server Manager, command line istool) does not change the job version. It can be changed manually in Designer.

The version number is stored in the ROOT record for the job in DS_JOBOBJECTS. Do not ever change the first component!

(I guessed that the OP knew the command.)

API stage does not run in parallel.

Of course it's possible. IF you know the structure of these tables. The structure of these tables (a) is undocumented and (b) is different in different record types.

We've been able to tease out some of the more critical items of information but definitely not all of it.

EXACTNUMERIC can be set up to - from memory - 57. It's safe to do. The default comes from the days when UniVerse was first created (1984) and computer memory was an issue.

Since the largest unsigned BigInt is 18,446,744,073,709,551,616 (20 digits) then your value should be at least 20.

Find out which variable is not being set in the script. Use echo statements in the script.

Surely re-inventing something in the public domain is wasting your client's money?

You can go about it any way you'd like. I'd use a server job that traversed the repository (DS_JOBS table) and used DataStage function DSGetJobInfo() in a routine to yield the required timestamps.

Not really. DS_AUDIT shows the date/time modified. Compiled does not count as modified. The Compiled status is recorded in the individual RT_STATUSnnn table for each separate job.

DS_AUDIT remains extant in version 8, but it seems that CLASS is no longer recorded correctly.

You can use a delimited string, but would need some mechanism within the job to parse it.

Complete detail is available in the export file if you make sure to export properties that have default values and read-only components.

I doubt that U can help - he's working on an all-Oracle site.

The second person personal pronoun in English is spelled "you".

You might like to perform an internet search for the SQLSTATE value.

Check that services for all three tiers are running.

1. Separate the inserts and updates into separate streams.
2. Upgrade to version 8 and prefer DB2 Connector or DB2 Enterprise stage.
3. Execute in parallel mode if possible.

Once upon a time DataStage was created and used UniVerse (UV) for its engine and repository. At version 6.0 DataStage and UniVerse split, but each maintained the code base. They have diverged since then, though they retain a great deal of similarity. The DataStage engine was - quite creatively - cal...

You will need 21 output columns.