DSXchange

There is also the "unit of work" MQ stage.

There is no builtin stage, so your connectivity will be through ODBC. As you are on UNIX the connectivity will not be automatic so you will need to install an appropriate driver. I think you can download drivers at Postgresql.org

There are more than one MQ stage, with differing functionalities and capabilities. The classic MQ Series stage and the (newer) WebSphere MQ Connector. You can do all sorts of nifty things in DataStage with MQ including processing "waves" and grouping transactions. But the functionality is all in MQ ...

My first guess is that a project file corruption might lead dsjob to abort. You can use the DS.TOOLS menu option 2 and then option 4. This can be called from the uv shell or the command line in the admin tool and has been discussed here in DSXchange.

RStone wrote:If I could get this code posted by Arndw to work...

Since I neglected the last parameter it won't compile and run, as Craig has posted.

The "%" characters need to be removed. Plus your "(" and ")" are not matched.

This is a NLS issue, the character 00xFC cannot be mapped from the DB2 to the database character set.

That is a very vague question. In the simplest case you can map straight from text file to XML. Could you post what you have tried already and which problem you have encountered?

A Date type column has no format. You need to give a format when converting a string to a date and a format to display a date. Are your input and your output columns of type string?

Most likely this has to do with view data, what happens if you write this column to a sequential file and look at that from Windows or to a peek stage?

There is a chapter in the administration manual telling you what needs to be done. I have V8 here so can't give you the page numbers.

Deleting any DataStage files at the UNIX or OS level is a big no-no. If the log is too big, use the director to clear the log (this might take some time, but is better than potentially breaking the project).

Justification only applies to text fields. In order to left just try:

where MaxLen is the length of your left-padded string and In.Column is the text right-padded input column.

No, rejects in PX come from the passive stages.

The -lstages option doesn't like you specifying a stage name. Remove "Sequential_File_2" from the command line and retry