DSXchange

It is not a bug.

You have supplied an XML document that does not begin and end with the same entity (that is, matching top-level beginning and ending tags).

This can not be parsed in any sensible way. So the job aborts. If I were the XML parser I'd give up too.

A Monitor on the job will show individual node row counts if Show Instances is selected.

Read the final few pages of Chapter 2 of the Parallel Job Developer's Guide

All complaints to billg@microsoft.com then. DataStage engineers can not be responsible for differences between the way the two Microsoft products work.

Learn patience.

You posted at 3am and 6am my time.

Penalty for impatience: 24 hours before I read the post.

If you require urgent support sign up for premium service with your support provider and learn the true cost of "urgent".

Luxury!!! We never had ones, and sometimes there weren't enough zeroes so we had to use capital O's.

You need to get a new authorization code for your existing serial number - otherwise you would need to completely re-install, and you don't need to.

When you performed a Search for the error text, what did you find?

Does the job in question use IPC, Link Partitioner or Link Collector stages?
Is inter-process row buffering enabled?

While your approach would work, there is a limit to the number of links that a Transformer stage can support - from memory I think it's 127. Plus you still have the problem about what to do to determine whether the Nth occurrence exists. Presumably you will have a constraint based on the value of PA...

Welcome aboard. There are (potentially) two passwords that have to be right - the deployment domain password (for IBM Information Server) and the DataStage password. Have you checked whether you need two, and whether they're both right? I agree that the observed behaviour is strange, but then you ne...

Welcome aboard, and thank you for making that offer to the participants here.

Given that the error message came from the BAT file itself, you really should be looking for the "culprit" there. For example are there any exit statements that generate an ERRORLEVEL value? One workaround would be to call this BAT file from another, which intercepts the non-zero exit status and exi...

Welcome aboard.

What, precisely, is the issue that you are facing? What is right for one system may not be right for yours.

Have you re-started the UNIX machine? If not, please try this, to clear structures from memory. Make sure, too, that your shared library search list set up in the dsenv scripts refers to the version 9 libraries for Oracle. Do your jobs use OCI (version 7), OCI8 or OCI9 stage types? You may need to m...

They are not stored on the DataStage server.