The table that is being accessed in this sample has four fields. Each row appears one at a time from the iterator. Two rows are shown. The first and the ninth, and the type codes are JDBC. This is the standard field form output documented in the RDBMS listener and SQL service.

The first row is shown below:

<root>
   <row row="1">
      <Name type="12">Mr. One</Name>
      <Id type="2">2</Id>
      <Dept type="12">ss</Dept>
      <Company type="12">ss</Company>
   </row>
</root>

The following instance shows the ninth row:

<root>
   <row row="9">
      <Name type="12">Mr. Jay</Name>
      <Id type="2">99</Id>
      <Dept type="12">jj</Dept>
      <Company type="12">jj</Company>
   </row>
</root>

If the user requested that the SQL service format be used, then the first row would have looked as follows:

<iway>
   <response>
      <cncresult>
         <result format="field">
            <row row="1">
               <Name type="12">ss</Name>
               <Id type="2">2</Id>
               <Dept type="12">ss</Dept>
               <Company type="12">ss</Company>
            </row>
         </result>
      </cncresult>
      <timestamp>2009-11-27T18:48:26Z</timestamp>
   </response>
</iway>

On EOS (end of select), the status document is emitted to the EOS service (the one past the bottom of the loop). Note that the number of batches may be greater than one, if sub-batches are used. This example has no failures.

<batcheos rowsread="13" batches="1" failures="0" omits="0" /> 

If failures were encountered, then these would have been denoted in a failure section, as shown in the following example:

<batcheos rowsread="13" batches="1" failures="2" omits="3">
     <failures>
        <failure row='5' key='Mr. Eee'/>
        <failure row='7' key='Mr. Gee'/>
     </failures>
  </batcheos>

An actual error (possibly because of the inability to reach a destination) will result in an error document.