DSXchange

You may find that it's a hidden file (that is, the first character of its name is a ".", that is ".odbc.ini"). Usually the pathname of this file is also available via the ODBCINI environment variable.

Inspect the SQL then supply the missing expression. It might be the WHERE clause in an UPDATE.

By using a job parameter. Or two.

The command line interface dsjob can be used to execute a job sequence. This command is fully documented in the Server Job Developer's Guide (which you have in your Docs folder on the machine where DataStage client software is installed). Search the forum for some good examples of how to use dsjob f...

Terminology: it wasn't a deadlock, it was merely correct behaviour of the locking mechanism. The waiting job would have started once the first job (the one that holds the lock) finished and released the lock. Examine the code to see that a job invoking KeyMgtGetNextValue continues to hold the lock o...

Default values are probably in the child table DSProperties or a similarly-named table. (I don't have access to DataStage at the moment, so can't check.) Be warned that every job parameter has two default values; a "design time" default, set by the developer, and a "run time" default, set by an Admi...

It's probably easier to create a CFD manually (in Notepad perhaps), import that, and proceed with using a CFF stage.

Resetting or recompiling the job should correct any wave synchronization problems. A wave number is simply an internal DataStage mechanism for keeping track of unique runs - for example, resetting a job uses a new wave number because it can't be certain that the previous wave is in a runnable state ...

Hashed files do not have data types. You can store any value in any column in a hashed file (irrespective of the hashed file's table definition) if you're using a Hashed File stage or if you're using DataStage BASIC. Therefore, your only possibility is to access the hashed file's table definition to...

Not possible. You will always need two SELECT operations in order to be able to perform a join. Further, DataStage server jobs do not directly support UNION as a join type without using intermediate text files or tables.

Archive using a before-job subroutine, but only events prior to the current run's start timestamp (which can be obtained via DSGetJobInfo() with DSJ.ME as the job handle). Note that this approach needs modification if multi-instance jobs are involved. Notwithstanding that suggestion, a well-written ...

Is the fact that I have 10 flows all accessing the same informix database simultaneously possibly going to cause some sort of contention problem ? Should I split the flows out into smaller separate jobs and run them sequentially ? I suspect that you've nailed it here. The contention does appear to ...

Don't rely on UniVerse unless you have a UniVerse licence. The next release of DataStage does not use a UniVerse-like repository.

Create a job sequence. This runs a small job to test the connection, then branches appropriately (your points 1.1 and 1.2). After the job containing the stored procedure invocation has run, test its exit status and again use Routine activity and Notification activity. Which stage to use really depen...

You can use a Transformer stage or a Modify stage. As well as any "pass through" columns, you have the single column generated earlier on the input link, and multiple columns on the output link. Use appropriate function (probably the Field() function) to decompose the various pieces from the input c...