DSXchange

DataStage is not, and never will be, a scheduling tool. It has a GUI interface to the operating system scheduler and that's all it will ever have. You can use the (documented) command line interface with any third party scheduler.

CFF stage can have an input in version 7.5. Time to upgrade?

Insufficient information. What is your source? How are these data partitioned? Clearly a Sequential File stage (which operates in sequential mode) can not preserve partitioning. You should not be expecting it to. Exactly why the Lookup stage is choosing to override your "preserve partitioning" setti...

Do you have the Ascential DataStage XP SP2 patch installed?

The original statement of the problem specified that a BASIC Transformer stage was being used, where both Change() and Ereplace() might legally be used. This is not the problem. The problem is that something, somewhere, is locking. Can you please explain exactly what you mean by "the processes are g...

The configuration file used/reported is whatever is currently pointed to by the APT_CONFIG_FILE environment variable.

Put the logic in a routine, invoke the routine from a Routine activity, and use its $ReturnValue activity variable to supply the value to the Job activity as a job parameter value.

Is there any additional error message (specifically a DB2 error code) in the job log? If you reset the aborted job, is there an event logged "from previous run..." containing diagnostic information?

How long between the stage starting and the error message appearing? How busy is DB2 doing other things? How busy is the DataStage machine?

A good search topic would be vertical pivot. Several techniques exist.

You can read "311205" as string[6] then in a Modify stage use a date_from_string function specifying "%dd%mm%yy" as the date picture. You will then have a date. It can be fed into any database table as a date, or you can convert it back to a string with a different picture if that's what you want.

Curiously a search for (all terms) "player terminated" got 26 hits. Of those this one is probably the most relevant. Take the actions suggested therein and post what you find.

Are you aware what conductor, section leader and player processes are in parallel jobs?

Only parallel jobs have player processes.

The "line feeds" lead me to suspect that, somehow, you have (illegal) "mark characters" (value mark, field mark, etc.) in the key. Check whether this is the case.

If you use a Complex Flat File stage you can specify exactly how the repeating group is to be handled - in your case normalized.