DSXchange

No. As I stated earlier there are no data types. You need to convert to the appropriate numeric units (for example days or seconds) and subtract those.

No. SQL is always sequential unless selecting from a partitioned table. I believe (without proof) that user-defined SQL is always sequential.

DataStage clients invoke COM objects for communication with the server. It is somewhere within the OLE server that exposes these objects that the failure has occurred. It might be something as simple as Windows losing track of a handle, or it may be much more complex. Alas, the message itself provid...

To use a job sequence create a loop that executes a large number of times and test the size of the file within the loop exiting from the loop if the file is empty. Or write a job control routine that uses an uncounted loop that exits on the same condition.

There are no data types in server jobs, therefore an attempt to subtract two timestamps is undefined. You need to convert them to some numeric format (for example seconds) and subtract those. In what units should C be?

There's nothing in DataStage that will make this any easier. Create a script (shell script or BTEQ) to do this task.

What empties the file?

Why not just leave it as a server job? The startup overhead is much less, which means that the output would arrive sooner.

Final delimiter is not the same thing as the record terminator. Final delimiter is a special property in case there is an extra delimiter between the final field and the end of the line. I may have mislead you by using that word. What I meant to ask was whether the last line in the file has its own ...

Is the FINAL line properly terminated? DataStage is complaining that end of file was encountered unexpectedly.

First problem: you need a C++ compiler, not a C compiler. Do you have one?

Second problem: have you given any thought to what happens when your command runs multiple copies in parallel? Will it work properly?

Isolate the Warning messages and read them carefully. They contain everything you need to know.

Do you really need to be running in debug mode?

DataStage does NOT generate an executable file. DataStage parallel jobs generate an osh script. When the job is run, a new osh script (called the "score") is written, taking into account the currently selected configuration. The score is executed within an Orchestrate shell - not by the operating sy...

The Transformer stage output link must have only one column (name). It must not output the id column. That way, name will align with the :1 parameter marker (the first parameter).

There are many ways. One is to invoke DSLogFatal() from a routine. But, if you only generate the right number of values, there is NO NEED to abort. This is definitely the preferred approach.