DSXchange

Do you have automatic error handling enabled in the sequence? Do you have a Failure trigger on the Execute Command activity?

Once you're logged in using Director, can you run Designer from the Tools menu?

While it's a data quality question, it's not a QualityStage question. However, it's a mixed DataStage/IA question, so General is probably the best forum.

Read with a Sequential File stage with First Line is Column Names set to True. Read the whole row into a single column, whose data type is a sufficiently large VarChar.

Parse the data using a Column Import stage or a Transfomer stage using Field() functions.

Welcome aboard.

The Transformer stage is probably the simplest way.

If you have an Information Analyzer licence you could also use the Data Rules stage in DataStage.

Do get fix pack 1. It corrects a number of minor annoyances.

Is this a parallel job (as marked) or a server job (as posted)?

Do you have "first line is column names" set in the Sequential File stage?

The derivations and target columns are to be found in the DS_JOBOBJECTS record for the output link from a Transformer stage. To determine that a link is an output link from a Transformer stage you will need to determine its source stage repository identifier (for example V0S7) and query DS_JOBOBJECT...

Can you compile a parallel job that does not have a Transformer stage? If so, your C++ compiler licensing may have expired.

If you have a licence you can download from IBM Passport Advantage.

Then I suggest you need to undertake a bit more detective work. Clearly something has changed. Does compilation throw any error message? Does the status of the job in Director change?

What has changed on your Engine server since "a few days ago"?

Not sure what you mean by "accept" here. Reading your question at face value I would have suggested the ISD Input stage, and don't understand how job parameters come into the picture at all.

That, in turn, really depends on whether the database specifies characters or bytes for storage. If bytes, then a multiplier is definitely indicated, and will usually occur automatically when the table definition is imported. We found with most encodings of Japanese data that a factor of 3 was corre...