Server XML Output Stage Structure

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
gsbrown
Premium Member
Premium Member
Posts: 148
Joined: Mon Sep 23, 2002 1:00 pm
Location: USA

Server XML Output Stage Structure

Post by gsbrown »

Writing a simple DS Server job using XML Output to produce this

Code: Select all

<payment>
                <jeweler_code>15498</jeweler_code>
                <invoices>
                                <invoice>
                                                <invoice_no>50000000005</invoice_no>
                                </invoice>
                                <invoice>            
                                                <invoice_no>50000000007</invoice_no>
                                </invoice>
                </invoices>
                <type>CHEC</type>
                <payment_no>123469</payment_no>
                <payment_date>2021-11-26</payment_date>
</payment>
However, it's producing this and can't figure out how to make it structure <invoice> repeated like above.
Any ideas how to specifically control that?

Code: Select all

<payment>
                <jeweler_code>15498</jeweler_code>
                <invoices>
                                <invoice>
                                                <invoice_no>50000000005</invoice_no>
                                                <invoice_no>50000000007</invoice_no>
                                </invoice>
                </invoices>
                <type>CHEC</type>
                <payment_no>123469</payment_no>
                <payment_date>2021-11-26</payment_date>
</payment>
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Re: Server XML Output Stage Structure

Post by ray.wurlod »

Have you marked invoice as a repeating element?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply