DSXchange

And? DataStage produces the information, you can post-process it into FIX format. There is nothing out-of-the-box in DataStage to do so.

When a parallel job is run opportunities are sought to run more than one adjacent operator in the one process, thereby to run the job in fewer processes. This is called operator combination, and can occur if the operators are adjacent, share the same degree of parallelism, and are combinable. Operat...

Yes, I think so. The FIX format may require more information than the default reporting from DataStage provides, which is why I pointed out the environment variable. And I don't believe initial logging format can be modified, which is why I mentioned post-processing of the job log.

It can be set, but not set correctly. You can't say DataStage is not correctly set up in this case; jobs without Transformer or Build stages will compile and run quite happily.

Still Yes.

You can even start job sequences or other batch jobs.

Determine the byte value of this character. It will be easier to guide you then. Do you, in fact, have NLS enabled? I don't believe it's an NLS issue; rather that the data browser (written in America) does not know how to display this particular character.

Define "performance" in an ETL context. Each parallel job will generate a process (or more than one) for every stage in the job design, if operator combination is prevented. So chances are that all six of your CPUs would become involved, even with only three nodes defined in your configuration file....

Read the Parallel Job Advanced Developer's Guide about the environment variable APT_ERROR_CONFIGURATION, which allows you to specify what components of error messages get reported (by default only about 40% of the available information is reported). This does not allow the format of error reporting ...

An operator is a piece of executable code that performs a specific task. For example an import operator can read a sequential file, a copy operator makes one or more copies of its input, and so on. Each stage in a DataStage job generates one (or sometimes more than one) operator in the generated OSH...

Then switch to the Define tab (which is what enables the OK button) and correct the data types guessed by DataStage and add data elements and descriptions for the columns. Click OK to save, then open the newly-imported table definition and add a meaningful short description and any useful additional...

This is usually due to a configuration error, such as not having the Orchestrate install directory properly mounted on all nodes, rsh permissions not correctly set (via /etc/hosts.equiv or .rhosts), or running from a directory that is not mounted on all nodes. Look for error messages in the precedi...

Check to see whether the individual columns have a Null Field Value property set. Sometimes this is set to "", which will override any global value given on the Format tab. Select any nullable column in the Columns grid and either double-click its row number or right click on the field name and choo...

Provided, of course, that APT_COMPILER has been correctly set.

MetaBag is a name used to indicate a collection. In your post there is a collection of metadata properties (the CMetaProperty tag indicates this). There is only one metadata property in the collection - the name of the property is Advanced Runtime Options and its value is the job parameter reference...

"Failed" for jobs is Aborted only. (Or Validation Failed if running a validation.)

"Failed" for a routine activity is a return value other than zero, for an execute command activity is an exit status other than zero, unless explicitly handled with a trigger.