DSXchange

You could write the XML data to a temporary file and parse using Perl, Java, C++ application to extract the data you need. But why go to that much trouble. Just obtain the patch from IBM support so you can use the XML input stage.

Definately as you have posted in your blog, change the join to a lookup stage. I would also go with a 1 node configuration as well. I have had a look at the other parallel job designs and have no idea why they have chosen to use a join stage which requires a sorted input, given the number of rows in...

I think you need to identify the bottleneck first before looking for possible solutions. What is your job doing? Are you connecting to any remote databases? What is your network configuration?

Use a join stage to link it back to the main customer details. Have a look at the document XML Pack Best Practices. Particularly section 3.2 BUILDING AN XML DOCUMENT WITH MULTIPLE REPEATED ELEMENTS, courtesy of Kim Duke: http://www.duke-consulting.com/Download ... ctices.zip

Looks like you will need to construct the contact detail XML section separately. This involves creating a flow that creates just the <contactDetail> XML fragment. Then join this back with the other customer details to create the final XML output. Therefore you will have two XML output stages. One fo...

Works ok for me. In the function field i am using FIELD1 : FIELD2 without the table qualifier.

The installation tool will prompt you to enter the username and password for each of the domain and repository layers. I am assuming here that you have just installed the server components. The installation manual on page 31-32 gives you a sample list of these users for each layer. To login initiall...

There are three compilers supported. Have a look at the the following link under the section Engine software requirements (Windows): http://www-01.ibm.com/support/docview.w ... eswwindows