DSXchange

For less than 30c per day you can have premium membership which, among other things, allows you to read the entire contents of premium posters' contributions. Premium membership revenue is 100% devoted to the hosting and bandwidth costs incurred by DSXchange; by purchasing premium membership you ar...

Can you please post the exact error message? Don't transcribe - use copy/paste. The rtl part of the error message refers to "run time library" so I guess the error is being thrown by the XMLInput stage. But without the actual error message it's difficult to say more.

Create a parallel routine that mimics some or all of the functionality of the Fmt() function - at least that subset that you require.

And stop thinking like a server job developer! Parallel jobs are a totally different product (formerly Orchestrate).

You have not specified any disk pools.

You should always specify at least a default disk pool (the one with "" as its name). Otherwise there's a lot of use of /tmp that could be avoided. And /tmp typically is not large enough, particularly on Solaris.

There is a pseudo-map called NONE. Might be worth trying that.

Ask the COBOL developers to generate a file that lacks these headers and footers.
All they need to do is to comment out some statements.

The .odbc.ini file is usually located in the DataStage engine directory. It is (usually) also referred to by the ODBCINI environment variable. Therefore, if you execute the command echo $ODBCINI you would get the pathname of the .odbc.ini file. Edit the .odbc.ini file to set up the DSNs that DataSta...

Can you be a bit more precise about exactly how you are going about this, so that we don't have to read your mind? It's too difficult at this distance!

Did you look on your installation media (the DVD or CD shipped from IBM)?

The largest possible TinyInt is 127. Check the data type again. Select (outside of DataStage) the MAX value from this field. Try setting the Extended property of the field to Unsigned. That is, change the data type from TinyInt to Unsigned TinyInt (or from int8 to uint8). The largest possible uint8 ...

Examine the log entries for DS-SEQ1 in each case. There are entries pertaining to setting and clearing of checkpoints. Are these the same?

Recompiling will destroy checkpoints. Does MSTR-DS-SEQ "reset if required, then run" DS-SEQ1? If so, change the rules so that it only runs DS-SEQ1.

The unqualified Trim() function (see my earlier post) will remove all leading and trailing white space characters and reduce any internal multiple white space characters to single.

Why do you think that?

Did you uninstall everything, including cleaning out the Registry, first?