DSXchange

The system variable @NULL.STR is the "string representation of null" using which would avoid needing to evaluate Char(128) in every row processed.

The output "table or file" is the source table ODBC1. User-defined SQL is of the form DELETE FROM tablename WHERE keycol = ? You might like to use an intermediate text file so that all rows are selected from ODBC1 before you start deleting rows, and therefore don't get locking issues. The file needs...

"collate sequence" or "collation sequence"

Like any UNIX machine, you must have created your DSN definitions in .odbc.ini and in uvodbc.config files. Have you done both of these?

There are techniques you can use, but you need to specify exactly what you want to do. For example, the DSGetParamInfo function can return a list of all the legal values in a List type parameter.

Surely you can wrap a loop around it (StartLoop and EndLoop activities) with a Sleep command in it?

No, but you can write your own Routine and call it from a Routine activity. Look at the supplied test routine as a start point.

Provided you've been diligent preserving the connections between table definitions in the Repository and in your jobs, you can do a Usage Analysis on the table definition in which the column occurs. This should reveal all the jobs in which it is used.

You must use separate Hashed File stages for reading and writing.

Add an Annotation to the job to indicate that both stages refer to the same hashed file.

The first area is one of politics or expectation management. At the really bad site of which I posted, the business analysts took 17 months of procrastination and prevarication before announcing that "we do not write specifications - we write business requirements". It would have been good to know t...

You can not use write cache, because the results have to be available immediately.
You can not use read cache, because the hashed file is cached when the stage opens and doesn't change subsequently in memory.
And you must specify "lock for update" - that is, "Disabled, lock for update".

kduke wrote:The review commitee covered the employee.

What did they cover the employee with?!!

Wrap the "picture" in Code tags, then use Preview to get it right. You could use a Routine activity to test whether the job is running, and only fire its trigger if the job is not. FUNCTION IsJobRunning(JobName) Equate RoutineName To "IsJobRunning" $IFNDEF JOBCONTROL.H $INCLUDE DS...

If you enable inter-process row buffering for this job it will allow (force?) the Transformer stages to run in separate processes.

Unless, of course, you use a UniVerse stage!