List:Commits« Previous MessageNext Message »
From:jon Date:April 27 2007 12:36am
Subject:svn commit - mysqldoc@docsrva: r6236 - trunk/ndbapi
View as plain text  
Author: jstephens
Date: 2007-04-27 02:35:59 +0200 (Fri, 27 Apr 2007)
New Revision: 6236

Log:

Reformat.



Modified:
   trunk/ndbapi/ndb-internals.xml


Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml	2007-04-27 00:35:14 UTC (rev 6235)
+++ trunk/ndbapi/ndb-internals.xml	2007-04-27 00:35:59 UTC (rev 6236)
Changed blocks: 4, Lines Added: 1265, Lines Deleted: 804; 89746 bytes

@@ -765,358 +765,356 @@
 
   </section>
 
-  
-
   <section id="ndb-internals-ndb-protocol">
 
-  <title>The NDB Protocol</title>
+    <title>The NDB Protocol</title>
 
-  <abstract>
+    <abstract>
 
-    <para>
-      This document discusses the protocol used for communication
-      between data nodes and API nodes in an NDB Cluster to perform
-      various operations such as data reads and writes, committing and
-      rolling back transactions, and handling of transaction records.
-    </para>
+      <para>
+        This document discusses the protocol used for communication
+        between data nodes and API nodes in an NDB Cluster to perform
+        various operations such as data reads and writes, committing and
+        rolling back transactions, and handling of transaction records.
+      </para>
 
-  </abstract>
+    </abstract>
 
-  <section id="ndb-internals-ndb-protocol-overview">
+    <section id="ndb-internals-ndb-protocol-overview">
 
-    <title><literal>NDB</literal> Protocol Overview</title>
+      <title><literal>NDB</literal> Protocol Overview</title>
 
-    <para>
-      MySQL Cluster data and API nodes communicate with one another by
-      passing messages to one another. The sending of a message from one
-      node and its reception by another node is referred to as a
-      <firstterm>signal</firstterm>; the <literal>NDB</literal> Protocol
-      is the set of rules governing the format of these messages and the
-      manner in which they are passed.
-    </para>
+      <para>
+        MySQL Cluster data and API nodes communicate with one another by
+        passing messages to one another. The sending of a message from
+        one node and its reception by another node is referred to as a
+        <firstterm>signal</firstterm>; the <literal>NDB</literal>
+        Protocol is the set of rules governing the format of these
+        messages and the manner in which they are passed.
+      </para>
 
-    <para>
-      An <literal>NDB</literal> message is typically either a
-      <firstterm>request</firstterm> or a
-      <firstterm>response</firstterm>. A request indicates that an API
-      node wants to perform an operation involving cluster data (such as
-      retrieval, insertion, updating, or deletion) or trsansactions
-      (commit, roll back, or to fetch or relase a transaction record). A
-      request is, when necessary, accompanied by key or index
-      information. The response sent by a data node to this request
-      indicates whether or not the request succeeded and, where
-      appropriate, is accompanied by one or more data messages.
-    </para>
+      <para>
+        An <literal>NDB</literal> message is typically either a
+        <firstterm>request</firstterm> or a
+        <firstterm>response</firstterm>. A request indicates that an API
+        node wants to perform an operation involving cluster data (such
+        as retrieval, insertion, updating, or deletion) or trsansactions
+        (commit, roll back, or to fetch or relase a transaction record).
+        A request is, when necessary, accompanied by key or index
+        information. The response sent by a data node to this request
+        indicates whether or not the request succeeded and, where
+        appropriate, is accompanied by one or more data messages.
+      </para>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Request types</title>
+        <title>Request types</title>
 
-      <para>
-        A request is represented as a <literal>REQ</literal> message.
-        Requests can be divided into those handling data and those
-        handling transactions:
+        <para>
+          A request is represented as a <literal>REQ</literal> message.
+          Requests can be divided into those handling data and those
+          handling transactions:
 
-        <itemizedlist>
+          <itemizedlist>
 
-          <listitem>
-            <formalpara>
+            <listitem>
+              <formalpara>
 
-              <title>Data requests</title>
+                <title>Data requests</title>
 
-              <para>
-                Data request operations are of three principal types:
+                <para>
+                  Data request operations are of three principal types:
 
-                <orderedlist>
+                  <orderedlist>
 
-                  <listitem>
-                    <formalpara>
+                    <listitem>
+                      <formalpara>
 
-                      <title>Primary key lookup operations</title>
+                        <title>Primary key lookup operations</title>
 
-                      <para>
-                        These are performed through the exchange of
-                        <literal>TCKEY</literal> messages.
-                      </para>
+                        <para>
+                          These are performed through the exchange of
+                          <literal>TCKEY</literal> messages.
+                        </para>
 
-                    </formalpara>
-                  </listitem>
+                      </formalpara>
+                    </listitem>
 
-                  <listitem>
-                    <formalpara>
+                    <listitem>
+                      <formalpara>
 
-                      <title>Unique key lookup operations</title>
+                        <title>Unique key lookup operations</title>
 
-                      <para>
-                        These are performed through the exchange of
-                        <literal>TCINDX</literal> messages.
-                      </para>
+                        <para>
+                          These are performed through the exchange of
+                          <literal>TCINDX</literal> messages.
+                        </para>
 
-                    </formalpara>
-                  </listitem>
+                      </formalpara>
+                    </listitem>
 
-                  <listitem>
-                    <formalpara>
+                    <listitem>
+                      <formalpara>
 
-                      <title>Table or index scan operations</title>
+                        <title>Table or index scan operations</title>
 
-                      <para>
-                        These are performed through the exchange of
-                        <literal>SCANTAB</literal> messages.
-                      </para>
+                        <para>
+                          These are performed through the exchange of
+                          <literal>SCANTAB</literal> messages.
+                        </para>
 
-                    </formalpara>
-                  </listitem>
+                      </formalpara>
+                    </listitem>
 
-                </orderedlist>
+                  </orderedlist>
 
-                Data request messages are often accompanied by
-                <literal>KEYINFO</literal> messages,
-                <literal>ATTRINFO</literal> messages, or both sorts of
-                messages.
-              </para>
+                  Data request messages are often accompanied by
+                  <literal>KEYINFO</literal> messages,
+                  <literal>ATTRINFO</literal> messages, or both sorts of
+                  messages.
+                </para>
 
-            </formalpara>
-          </listitem>
+              </formalpara>
+            </listitem>
 
-          <listitem>
-            <formalpara>
+            <listitem>
+              <formalpara>
 
-              <title>Transactional requests</title>
+                <title>Transactional requests</title>
 
-              <para>
-                These may be divided into two categories:
+                <para>
+                  These may be divided into two categories:
 
-                <orderedlist>
+                  <orderedlist>
 
-                  <listitem>
-                    <para>
-                      Commits and rollbacks, which are represented by
-                      <literal>TC_COMMIT</literal> and
-                      <literal>TCROLLBACK</literal> request messages,
-                      respectively.
-                    </para>
-                  </listitem>
+                    <listitem>
+                      <para>
+                        Commits and rollbacks, which are represented by
+                        <literal>TC_COMMIT</literal> and
+                        <literal>TCROLLBACK</literal> request messages,
+                        respectively.
+                      </para>
+                    </listitem>
 
-                  <listitem>
-                    <para>
-                      Transaction record requests &mdash; that is,
-                      transaction record acquisition and release. These
-                      requests are handled through the use of,
-                      respectively, <literal>TCSEIZE</literal> and
-                      <literal>TCRELEASE</literal> request messages.
-                    </para>
-                  </listitem>
+                    <listitem>
+                      <para>
+                        Transaction record requests &mdash; that is,
+                        transaction record acquisition and release.
+                        These requests are handled through the use of,
+                        respectively, <literal>TCSEIZE</literal> and
+                        <literal>TCRELEASE</literal> request messages.
+                      </para>
+                    </listitem>
 
-                </orderedlist>
-              </para>
+                  </orderedlist>
+                </para>
 
-            </formalpara>
-          </listitem>
+              </formalpara>
+            </listitem>
 
-        </itemizedlist>
-      </para>
+          </itemizedlist>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Response types</title>
+        <title>Response types</title>
 
-      <para>
-        A response indicates either the success or the failure of the
-        request to which it is sent in reply:
+        <para>
+          A response indicates either the success or the failure of the
+          request to which it is sent in reply:
 
-        <itemizedlist>
+          <itemizedlist>
 
-          <listitem>
-            <formalpara>
+            <listitem>
+              <formalpara>
 
-              <title>Response indicating success</title>
+                <title>Response indicating success</title>
 
-              <para>
-                This type of response is represented as a
-                <literal>CONF</literal> (confirmation) message, and is
-                often accompanied by data, which is packaged as one or
-                more <literal>TRANSID_AI</literal> messages.
-              </para>
+                <para>
+                  This type of response is represented as a
+                  <literal>CONF</literal> (confirmation) message, and is
+                  often accompanied by data, which is packaged as one or
+                  more <literal>TRANSID_AI</literal> messages.
+                </para>
 
-            </formalpara>
-          </listitem>
+              </formalpara>
+            </listitem>
 
-          <listitem>
-            <formalpara>
+            <listitem>
+              <formalpara>
 
-              <title>Response indicating failure</title>
+                <title>Response indicating failure</title>
 
-              <para>
-                This type of response is represented as a
-                <literal>REF</literal> (refusal) message.
-              </para>
+                <para>
+                  This type of response is represented as a
+                  <literal>REF</literal> (refusal) message.
+                </para>
 
-            </formalpara>
-          </listitem>
+              </formalpara>
+            </listitem>
 
-        </itemizedlist>
-      </para>
+          </itemizedlist>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <para>
-      These message types and their relationship to one another are
-      discussed in more detail in
-      <xref linkend="ndb-internals-ndb-protocol-message-names-structure"/>.
-    </para>
+      <para>
+        These message types and their relationship to one another are
+        discussed in more detail in
+        <xref linkend="ndb-internals-ndb-protocol-message-names-structure"/>.
+      </para>
 
-  </section>
+    </section>
 
-  <section id="ndb-internals-ndb-protocol-message-names-structure">
+    <section id="ndb-internals-ndb-protocol-message-names-structure">
 
-    <title>Message Naming Conventions and Structure</title>
+      <title>Message Naming Conventions and Structure</title>
 
-    <para>
-      This section describes the <literal>NDB</literal> Protocol message
-      types and their structures.
-    </para>
+      <para>
+        This section describes the <literal>NDB</literal> Protocol
+        message types and their structures.
+      </para>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Naming Conventions</title>
+        <title>Naming Conventions</title>
 
-      <para>
-        Message names are constructed according to a simple pattern
-        which should be readily apparent from the discussion of request
-        and response types in the previous section. These are shown in
-        the following matrix:
+        <para>
+          Message names are constructed according to a simple pattern
+          which should be readily apparent from the discussion of
+          request and response types in the previous section. These are
+          shown in the following matrix:
 
-        <informaltable>
-          <tgroup cols="4">
-            <colspec colwidth="25*"/>
-            <colspec colwidth="25*"/>
-            <colspec colwidth="25*"/>
-            <colspec colwidth="25*"/>
-            <tbody>
-              <row>
-                <entry><emphasis role="bold">Operation Type</emphasis></entry>
-                <entry><emphasis role="bold">Request (<literal>REQ</literal>)</emphasis></entry>
-                <entry><emphasis role="bold">Response/Success
-                  (<literal>CONF</literal>)</emphasis></entry>
-                <entry><emphasis role="bold">Response/Failure
-                  (<literal>REF</literal>)</emphasis></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Primary Key Lookup
-                  (<literal>TCKEY</literal>)</emphasis></entry>
-                <entry><literal>TCKEYREQ</literal></entry>
-                <entry><literal>TCKEYCONF</literal></entry>
-                <entry><literal>TCKEYREF</literal></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Unique Key Lookup
-                  (<literal>TCINDX</literal>)</emphasis></entry>
-                <entry><literal>TCINDXREQ</literal></entry>
-                <entry><literal>TCINDXCONF</literal></entry>
-                <entry><literal>TCINDXREF</literal></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Table or Index Scan
-                  (<literal>SCANTAB</literal>)</emphasis></entry>
-                <entry><literal>SCANTABREQ</literal></entry>
-                <entry><literal>SCANTABCONF</literal></entry>
-                <entry><literal>SCANTABREF</literal></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Result Retrieval
-                  (<literal>SCAN_NEXT</literal>)</emphasis></entry>
-                <entry><literal>SCAN_NEXTREQ</literal></entry>
-                <entry><literal>SCANTABCONF</literal></entry>
-                <entry><literal>SCANTABREF</literal></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Transaction Record Acquisition
-                  (<literal>TCSEIZE</literal>)</emphasis></entry>
-                <entry><literal>TCSEIZEREQ</literal></entry>
-                <entry><literal>TCSEIZECONF</literal></entry>
-                <entry><literal>TCSEIZEREF</literal></entry>
-              </row>
-              <row>
-                <entry><emphasis role="bold">Transaction Record Release
-                  (<literal>TCRELEASE</literal>)</emphasis></entry>
-                <entry><literal>TCRELEASEREQ</literal></entry>
-                <entry><literal>TCRELEASECONF</literal></entry>
-                <entry><literal>TCRELEASEREF</literal></entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable>
+          <informaltable>
+            <tgroup cols="4">
+              <colspec colwidth="25*"/>
+              <colspec colwidth="25*"/>
+              <colspec colwidth="25*"/>
+              <colspec colwidth="25*"/>
+              <tbody>
+                <row>
+                  <entry><emphasis role="bold">Operation Type</emphasis></entry>
+                  <entry><emphasis role="bold">Request (<literal>REQ</literal>)</emphasis></entry>
+                  <entry><emphasis role="bold">Response/Success
+                    (<literal>CONF</literal>)</emphasis></entry>
+                  <entry><emphasis role="bold">Response/Failure
+                    (<literal>REF</literal>)</emphasis></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Primary Key Lookup
+                    (<literal>TCKEY</literal>)</emphasis></entry>
+                  <entry><literal>TCKEYREQ</literal></entry>
+                  <entry><literal>TCKEYCONF</literal></entry>
+                  <entry><literal>TCKEYREF</literal></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Unique Key Lookup
+                    (<literal>TCINDX</literal>)</emphasis></entry>
+                  <entry><literal>TCINDXREQ</literal></entry>
+                  <entry><literal>TCINDXCONF</literal></entry>
+                  <entry><literal>TCINDXREF</literal></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Table or Index Scan
+                    (<literal>SCANTAB</literal>)</emphasis></entry>
+                  <entry><literal>SCANTABREQ</literal></entry>
+                  <entry><literal>SCANTABCONF</literal></entry>
+                  <entry><literal>SCANTABREF</literal></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Result Retrieval
+                    (<literal>SCAN_NEXT</literal>)</emphasis></entry>
+                  <entry><literal>SCAN_NEXTREQ</literal></entry>
+                  <entry><literal>SCANTABCONF</literal></entry>
+                  <entry><literal>SCANTABREF</literal></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Transaction Record Acquisition
+                    (<literal>TCSEIZE</literal>)</emphasis></entry>
+                  <entry><literal>TCSEIZEREQ</literal></entry>
+                  <entry><literal>TCSEIZECONF</literal></entry>
+                  <entry><literal>TCSEIZEREF</literal></entry>
+                </row>
+                <row>
+                  <entry><emphasis role="bold">Transaction Record Release
+                    (<literal>TCRELEASE</literal>)</emphasis></entry>
+                  <entry><literal>TCRELEASEREQ</literal></entry>
+                  <entry><literal>TCRELEASECONF</literal></entry>
+                  <entry><literal>TCRELEASEREF</literal></entry>
+                </row>
+              </tbody>
+            </tgroup>
+          </informaltable>
 
-        <literal>CONF</literal> and <literal>REF</literal> are shorthand
-        for <quote>confirmed</quote> and <quote>refused</quote>,
-        respectively.
-      </para>
+          <literal>CONF</literal> and <literal>REF</literal> are
+          shorthand for <quote>confirmed</quote> and
+          <quote>refused</quote>, respectively.
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <para>
-      Three additional types of messages are used in some instances of
-      inter-node communication. These message types are:
+      <para>
+        Three additional types of messages are used in some instances of
+        inter-node communication. These message types are:
 
-      <orderedlist>
+        <orderedlist>
 
-        <listitem>
-          <para>
-            A <literal>KEYINFO</literal> message contains information
-            about the key used in a <literal>TCKEYREQ</literal> or
-            <literal>TCINDXREQ</literal> message. It is employed when
-            the key data does not fit within the request message.
-            <literal>KEYINFO</literal> messages are also sent for index
-            scan operations in which bounds are employed.
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              A <literal>KEYINFO</literal> message contains information
+              about the key used in a <literal>TCKEYREQ</literal> or
+              <literal>TCINDXREQ</literal> message. It is employed when
+              the key data does not fit within the request message.
+              <literal>KEYINFO</literal> messages are also sent for
+              index scan operations in which bounds are employed.
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            An <literal>ATTRINFO</literal> message contains non-key
-            attribute values which does not fit within a
-            <literal>TCKEYREQ</literal>, <literal>TCINDXREQ</literal>,
-            or <literal>SCANTABREQ</literal> message. It is used for:
+          <listitem>
+            <para>
+              An <literal>ATTRINFO</literal> message contains non-key
+              attribute values which does not fit within a
+              <literal>TCKEYREQ</literal>, <literal>TCINDXREQ</literal>,
+              or <literal>SCANTABREQ</literal> message. It is used for:
 
-            <itemizedlist>
+              <itemizedlist>
 
-              <listitem>
-                <para>
-                  Supplying attribute values for inserts and updates
-                </para>
-              </listitem>
+                <listitem>
+                  <para>
+                    Supplying attribute values for inserts and updates
+                  </para>
+                </listitem>
 
-              <listitem>
-                <para>
-                  Designating which attributes are to be read for read
-                  operations
-                </para>
-              </listitem>
+                <listitem>
+                  <para>
+                    Designating which attributes are to be read for read
+                    operations
+                  </para>
+                </listitem>
 
-              <listitem>
-                <para>
-                  Specifying optional values to read for delete
-                  operations
-                </para>
-              </listitem>
+                <listitem>
+                  <para>
+                    Specifying optional values to read for delete
+                    operations
+                  </para>
+                </listitem>
 
-            </itemizedlist>
-          </para>
-        </listitem>
+              </itemizedlist>
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            A <literal>TRANSID_AI</literal> message contains data
-            returned from a read operation &mdash; in other words, it is
-            a result set (or part of one).
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              A <literal>TRANSID_AI</literal> message contains data
+              returned from a read operation &mdash; in other words, it
+              is a result set (or part of one).
+            </para>
+          </listitem>
 
-      </orderedlist>
-    </para>
+        </orderedlist>
+      </para>
 
 <!--
     <formalpara>

@@ -1167,1139 +1165,1601 @@
     </formalpara>
 -->
 
-  </section>
+    </section>
 
-  <section id="ndb-internals-ndb-protocol-operations-signals">
+    <section id="ndb-internals-ndb-protocol-operations-signals">
 
-    <title>Operations and Signals</title>
+      <title>Operations and Signals</title>
 
-    <para>
-      In this section we discuss the sequence of message-passing that
-      takes place between a data node and an API node for each of the
-      following operations:
+      <para>
+        In this section we discuss the sequence of message-passing that
+        takes place between a data node and an API node for each of the
+        following operations:
 
-      <itemizedlist>
+        <itemizedlist>
 
-        <listitem>
-          <para>
-            Primary key lookup
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Primary key lookup
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            Unique key lookup
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Unique key lookup
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            Table scan or index scan
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Table scan or index scan
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            Explicit commit of a transaction
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Explicit commit of a transaction
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            Rollback of a transaction
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Rollback of a transaction
+            </para>
+          </listitem>
 
-        <listitem>
-          <para>
-            Transaction record handling (acquisition and release)
-          </para>
-        </listitem>
+          <listitem>
+            <para>
+              Transaction record handling (acquisition and release)
+            </para>
+          </listitem>
 
-      </itemizedlist>
-    </para>
+        </itemizedlist>
+      </para>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Primary key lookup</title>
+        <title>Primary key lookup</title>
 
-      <para>
-        An operation using a primary key lookup is performed shown in
-        the following diagram:
+        <para>
+          An operation using a primary key lookup is performed shown in
+          the following diagram:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-pk-lookup-1.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase lang="en">Messages exchanged in a primary key
-            lookup</phrase>
-          </textobject>
-        </mediaobject>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-pk-lookup-1.png" format="PNG"/>
+            </imageobject>
+            <textobject>
+              <phrase lang="en">Messages exchanged in a primary key
+              lookup</phrase>
+            </textobject>
+          </mediaobject>
 
-        <note>
-          <para>
-            <emphasis role="bold">*</emphasis> and
-            <emphasis role="bold">+</emphasis> are used here with the
-            meanings <quote>zero or more</quote> and <quote>one or
-            more</quote>, respectively.
-          </para>
-        </note>
+          <note>
+            <para>
+              <emphasis role="bold">*</emphasis> and
+              <emphasis role="bold">+</emphasis> are used here with the
+              meanings <quote>zero or more</quote> and <quote>one or
+              more</quote>, respectively.
+            </para>
+          </note>
 
-        This process is explained is greater detail here:
+          This process is explained is greater detail here:
 
-        <orderedlist>
+          <orderedlist>
 
-          <listitem>
-            <para>
-              The API node sends a <literal>TCKEYREQ</literal> message
-              to the data node. In the event that the necessary
-              information about the key to be used is too large to be
-              contained in the <literal>TCKEYREQ</literal>, the message
-              may be accompanied by any number of
-              <literal>KEYINFO</literal> messages carrying the remaining
-              key information. If additional attributes are used for the
-              operation and exceed the space available in the
-              <literal>TCKEYREQ</literal>, or if data is to be sent to
-              the data node as part of a write operation, then these are
-              sent with the <literal>TCKEYREQ</literal> as any number of
-              <literal>ATTRINFO</literal> messages.
-            </para>
-          </listitem>
+            <listitem>
+              <para>
+                The API node sends a <literal>TCKEYREQ</literal> message
+                to the data node. In the event that the necessary
+                information about the key to be used is too large to be
+                contained in the <literal>TCKEYREQ</literal>, the
+                message may be accompanied by any number of
+                <literal>KEYINFO</literal> messages carrying the
+                remaining key information. If additional attributes are
+                used for the operation and exceed the space available in
+                the <literal>TCKEYREQ</literal>, or if data is to be
+                sent to the data node as part of a write operation, then
+                these are sent with the <literal>TCKEYREQ</literal> as
+                any number of <literal>ATTRINFO</literal> messages.
+              </para>
+            </listitem>
 
-          <listitem>
-            <para>
-              The data node then sends a message in response to the
-              request:
+            <listitem>
+              <para>
+                The data node then sends a message in response to the
+                request:
 
-              <itemizedlist>
+                <itemizedlist>
 
-                <listitem>
-                  <para>
-                    If the operation was successful, the data node sends
-                    a <literal>TCKEYCONF</literal> message to the API
-                    node. If the request was for a read operation, then
-                    <literal>TCKEYCONF</literal> is accompanied by a
-                    <literal>TRANSID_AI</literal> message, which
-                    contains actual result data. If there is more data
-                    than can be contained in a single
-                    <literal>TRANSID_AI</literal> can carry, more than
-                    one of these messages may be sent.
-                  </para>
-                </listitem>
+                  <listitem>
+                    <para>
+                      If the operation was successful, the data node
+                      sends a <literal>TCKEYCONF</literal> message to
+                      the API node. If the request was for a read
+                      operation, then <literal>TCKEYCONF</literal> is
+                      accompanied by a <literal>TRANSID_AI</literal>
+                      message, which contains actual result data. If
+                      there is more data than can be contained in a
+                      single <literal>TRANSID_AI</literal> can carry,
+                      more than one of these messages may be sent.
+                    </para>
+                  </listitem>
 
-                <listitem>
-                  <para>
-                    If the operation failed, then the data node sends a
-                    <literal>TCKEYREF</literal> message back to the API
-                    node, and no more signalling takes place until the
-                    API node makes a new request.
-                  </para>
-                </listitem>
+                  <listitem>
+                    <para>
+                      If the operation failed, then the data node sends
+                      a <literal>TCKEYREF</literal> message back to the
+                      API node, and no more signalling takes place until
+                      the API node makes a new request.
+                    </para>
+                  </listitem>
 
-              </itemizedlist>
-            </para>
-          </listitem>
+                </itemizedlist>
+              </para>
+            </listitem>
 
-        </orderedlist>
-      </para>
+          </orderedlist>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Unique key lookup</title>
+        <title>Unique key lookup</title>
 
-      <para>
-        This is performed in a manner similar to that performed in a
-        primary key lookup:
+        <para>
+          This is performed in a manner similar to that performed in a
+          primary key lookup:
 
-        <orderedlist>
+          <orderedlist>
 
-          <listitem>
-            <para>
-              A request is made by the API node using a
-              <literal>TCINDXREQ</literal> message which may be
-              accompanied by zero or more <literal>KEYINFO</literal>
-              messages, zero or more <literal>ATTRINFO</literal>
-              messages, or both.
-            </para>
-          </listitem>
+            <listitem>
+              <para>
+                A request is made by the API node using a
+                <literal>TCINDXREQ</literal> message which may be
+                accompanied by zero or more <literal>KEYINFO</literal>
+                messages, zero or more <literal>ATTRINFO</literal>
+                messages, or both.
+              </para>
+            </listitem>
 
-          <listitem>
-            <para>
-              The data node returns a response:
+            <listitem>
+              <para>
+                The data node returns a response:
 
-              <itemizedlist>
+                <itemizedlist>
 
-                <listitem>
-                  <para>
-                    If the operation was a success, the message is
-                    <literal>TCINDXCONF</literal>. For a successful read
-                    operation, this message may be accompanied by one or
-                    more <literal>TRANSID_AI</literal> messages carrying
-                    the result data.
-                  </para>
-                </listitem>
+                  <listitem>
+                    <para>
+                      If the operation was a success, the message is
+                      <literal>TCINDXCONF</literal>. For a successful
+                      read operation, this message may be accompanied by
+                      one or more <literal>TRANSID_AI</literal> messages
+                      carrying the result data.
+                    </para>
+                  </listitem>
 
-                <listitem>
-                  <para>
-                    If the operation failed, the data node returns a
-                    <literal>TCINDXREF</literal> message.
-                  </para>
-                </listitem>
+                  <listitem>
+                    <para>
+                      If the operation failed, the data node returns a
+                      <literal>TCINDXREF</literal> message.
+                    </para>
+                  </listitem>
 
-              </itemizedlist>
-            </para>
-          </listitem>
+                </itemizedlist>
+              </para>
+            </listitem>
 
-        </orderedlist>
+          </orderedlist>
 
-        The exchange of messages involved in a unique key lookup is
-        illustrated here:
+          The exchange of messages involved in a unique key lookup is
+          illustrated here:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-uk-lookup-1.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase lang="en">Messages exchanged in a unique key
-            lookup</phrase>
-          </textobject>
-        </mediaobject>
-      </para>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-uk-lookup-1.png" format="PNG"/>
+            </imageobject>
+            <textobject>
+              <phrase lang="en">Messages exchanged in a unique key
+              lookup</phrase>
+            </textobject>
+          </mediaobject>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Table scans and index scans</title>
+        <title>Table scans and index scans</title>
 
-      <para>
-        These are similar in many respects to primary key and unique key
-        lookups, as shown here:
+        <para>
+          These are similar in many respects to primary key and unique
+          key lookups, as shown here:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-table-index-scan-1.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase lang="en">Messages exchanged for a table scan or
-            index scan operation.</phrase>
-          </textobject>
-        </mediaobject>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-table-index-scan-1.png" format="PNG"/>
+            </imageobject>
+            <textobject>
+              <phrase lang="en">Messages exchanged for a table scan or
+              index scan operation.</phrase>
+            </textobject>
+          </mediaobject>
 
-        <orderedlist>
+          <orderedlist>
 
-          <listitem>
-            <para>
-              A request is made by the API node using a
-              <literal>SCAN_TABREQ</literal> message, along with zero or
-              more <literal>ATTRINFO</literal> messages.
-              <literal>KEYINFO</literal> messages are also used with
-              index scans in the event that bounds are used.
-            </para>
-          </listitem>
+            <listitem>
+              <para>
+                A request is made by the API node using a
+                <literal>SCAN_TABREQ</literal> message, along with zero
+                or more <literal>ATTRINFO</literal> messages.
+                <literal>KEYINFO</literal> messages are also used with
+                index scans in the event that bounds are used.
+              </para>
+            </listitem>
 
-          <listitem>
-            <para>
-              The data node returns a response:
+            <listitem>
+              <para>
+                The data node returns a response:
 
-              <itemizedlist>
+                <itemizedlist>
 
-                <listitem>
-                  <para>
-                    If the operation was a success, the message is
-                    <literal>SCAN_TABCONF</literal>. For a successful
-                    read operation, this message may be accompanied by
-                    one or more <literal>TRANSID_AI</literal> messages
-                    carrying the result data. However &mdash; unlike the
-                    case with lookups based on a primary or unique key
-                    &mdash; it is often necessary to fetch multiple
-                    results from the data node. Requests following the
-                    first are signalled by the API node using a
-                    <literal>SCAN_NEXTREQ</literal>, which tells the
-                    data node to send the next set of results (if there
-                    are more results). This is shown here:
+                  <listitem>
+                    <para>
+                      If the operation was a success, the message is
+                      <literal>SCAN_TABCONF</literal>. For a successful
+                      read operation, this message may be accompanied by
+                      one or more <literal>TRANSID_AI</literal> messages
+                      carrying the result data. However &mdash; unlike
+                      the case with lookups based on a primary or unique
+                      key &mdash; it is often necessary to fetch
+                      multiple results from the data node. Requests
+                      following the first are signalled by the API node
+                      using a <literal>SCAN_NEXTREQ</literal>, which
+                      tells the data node to send the next set of
+                      results (if there are more results). This is shown
+                      here:
 
-                    <mediaobject>
-                      <imageobject>
-                        <imagedata fileref="protocol-images/ndb-protocol-fetch-results-1.png" format="PNG"/>
-                      </imageobject>
-                      <textobject>
-                        <phrase lang="en">Fetching multiple result data
-                        sets following a table or index scan read
-                        operation</phrase>
-                      </textobject>
-                    </mediaobject>
-                  </para>
-                </listitem>
+                      <mediaobject>
+                        <imageobject>
+                          <imagedata fileref="protocol-images/ndb-protocol-fetch-results-1.png" format="PNG"/>
+                        </imageobject>
+                        <textobject>
+                          <phrase lang="en">Fetching multiple result
+                          data sets following a table or index scan read
+                          operation</phrase>
+                        </textobject>
+                      </mediaobject>
+                    </para>
+                  </listitem>
 
-                <listitem>
-                  <para>
-                    If the operation failed, the data node returns a
-                    <literal>SCAN_TABREF</literal> message.
-                  </para>
+                  <listitem>
+                    <para>
+                      If the operation failed, the data node returns a
+                      <literal>SCAN_TABREF</literal> message.
+                    </para>
 
-                  <para>
-                    <literal>SCAN_TABREF</literal> is also used to
-                    signal to the API node that all data resulting from
-                    a read has been sent.
-                  </para>
-                </listitem>
+                    <para>
+                      <literal>SCAN_TABREF</literal> is also used to
+                      signal to the API node that all data resulting
+                      from a read has been sent.
+                    </para>
+                  </listitem>
 
-              </itemizedlist>
-            </para>
-          </listitem>
+                </itemizedlist>
+              </para>
+            </listitem>
 
-        </orderedlist>
-      </para>
+          </orderedlist>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Committing and rolling back transactions</title>
+        <title>Committing and rolling back transactions</title>
 
-      <para>
-        The process of performing an explicit commit follows the same
-        general pattern as shown previously. The API node sends a
-        <literal>TC_COMMITREQ</literal> message to the data node, which
-        responds with either a <literal>TC_COMMITCONF</literal> (on
-        success) or a <literal>TC_COMMITREF</literal> (if the commit
-        failed). This is shown in the following diagram:
+        <para>
+          The process of performing an explicit commit follows the same
+          general pattern as shown previously. The API node sends a
+          <literal>TC_COMMITREQ</literal> message to the data node,
+          which responds with either a <literal>TC_COMMITCONF</literal>
+          (on success) or a <literal>TC_COMMITREF</literal> (if the
+          commit failed). This is shown in the following diagram:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-explicit-commit-1.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase lang="en">Messages exchanged in explicit commit
-            operation</phrase>
-          </textobject>
-        </mediaobject>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-explicit-commit-1.png" format="PNG"/>
+            </imageobject>
+            <textobject>
+              <phrase lang="en">Messages exchanged in explicit commit
+              operation</phrase>
+            </textobject>
+          </mediaobject>
 
-        <note>
-          <para>
-            Some operations perform a <literal>COMMIT</literal>
-            automatically, so this is not required for every
-            transaction.
-          </para>
-        </note>
+          <note>
+            <para>
+              Some operations perform a <literal>COMMIT</literal>
+              automatically, so this is not required for every
+              transaction.
+            </para>
+          </note>
 
-        Rolling back a transaction also follows this pattern. In this
-        case, however, the API node sends a
-        <literal>TCROLLBACKTREQ</literal> message to the data node.
-        Either a <literal>TCROLLACKCONF</literal> or a
-        <literal>TCROLLBACKREF</literal> is sent in response, as shown
-        here:
+          Rolling back a transaction also follows this pattern. In this
+          case, however, the API node sends a
+          <literal>TCROLLBACKTREQ</literal> message to the data node.
+          Either a <literal>TCROLLACKCONF</literal> or a
+          <literal>TCROLLBACKREF</literal> is sent in response, as shown
+          here:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-rollback-1.png" format="PNG"/>
-          </imageobject>
-          <textobject>
-            <phrase lang="en">Messages exchanged when rolling back a
-            transaction</phrase>
-          </textobject>
-        </mediaobject>
-      </para>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-rollback-1.png" format="PNG"/>
+            </imageobject>
+            <textobject>
+              <phrase lang="en">Messages exchanged when rolling back a
+              transaction</phrase>
+            </textobject>
+          </mediaobject>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
-    <formalpara>
+      <formalpara>
 
-      <title>Handling of transaction records</title>
+        <title>Handling of transaction records</title>
 
-      <para>
-        Acquiring a transaction record is accomplished when an API node
-        transmits a <literal>TCSEIZEREQ</literal> message to a data node
-        and receives a <literal>TCSEIZECONF</literal> or
-        <literal>TCSEIZEREF</literal> in return, depending on whether or
-        not the request was successful. This is depicted here:
+        <para>
+          Acquiring a transaction record is accomplished when an API
+          node transmits a <literal>TCSEIZEREQ</literal> message to a
+          data node and receives a <literal>TCSEIZECONF</literal> or
+          <literal>TCSEIZEREF</literal> in return, depending on whether
+          or not the request was successful. This is depicted here:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-trx-acquisition-1.png" format="PNG"/>
-          </imageobject>
-          <textobject lang="en">
-            <phrase>Signals used in transaction record
-            acquisition</phrase>
-          </textobject>
-        </mediaobject>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-trx-acquisition-1.png" format="PNG"/>
+            </imageobject>
+            <textobject lang="en">
+              <phrase>Signals used in transaction record
+              acquisition</phrase>
+            </textobject>
+          </mediaobject>
 
-        The release of a transaction record is also handled using the
-        request-response pattern. In this case, the API node's request
-        contains a <literal>TCRELEASEREQ</literal> message, and the data
-        node's response uses either a <literal>TCRELEASECONF</literal>
-        (indicating that the record was released) or a
-        <literal>TCRELEASEREF</literal> (indicating that the attempt at
-        release did not succeed). This series of events is illustrated
-        in the next diagram:
+          The release of a transaction record is also handled using the
+          request-response pattern. In this case, the API node's request
+          contains a <literal>TCRELEASEREQ</literal> message, and the
+          data node's response uses either a
+          <literal>TCRELEASECONF</literal> (indicating that the record
+          was released) or a <literal>TCRELEASEREF</literal> (indicating
+          that the attempt at release did not succeed). This series of
+          events is illustrated in the next diagram:
 
-        <mediaobject>
-          <imageobject>
-            <imagedata fileref="protocol-images/ndb-protocol-trx-release-1.png" format="PNG"/>
-          </imageobject>
-          <textobject lang="en">
-            <phrase>Signals used in releasing a transaction
-            record</phrase>
-          </textobject>
-        </mediaobject>
-      </para>
+          <mediaobject>
+            <imageobject>
+              <imagedata fileref="protocol-images/ndb-protocol-trx-release-1.png" format="PNG"/>
+            </imageobject>
+            <textobject lang="en">
+              <phrase>Signals used in releasing a transaction
+              record</phrase>
+            </textobject>
+          </mediaobject>
+        </para>
 
-    </formalpara>
+      </formalpara>
 
+    </section>
+
   </section>
 
-  </section>
-  
   <section id="ndb-internals-kernel-blocks">
+
     <title><literal>NDB</literal> Kernel Blocks</title>
-    
+
     <para>
       This section lists and describes the major kernel blocks found in
       the <literal>NDB</literal> source code, under the directory
       <filename>storage/ndb/src/kernel/blocks/</filename>.
     </para>
-    
+
     <remark role="note">
       [js] Using an itemizedlist for now, may want to promote list items
       to (sub)sections as more information is added?
     </remark>
-    
+
     <remark role="note">
       [js] I've omitted makefiles and SCCS subdirectories from the
-      kernel block file listings. 
+      kernel block file listings.
     </remark>
-    
+
     <remark role="todo">
       [js] Possibly remove .txt files from listings and incorporate
       their content directly into this doc?
     </remark>
-    
+
     <remark role="todo">
       Alphabatise file listings within each block; add descriptions of
       the code in each one and what it does.
     </remark>
-    
+
     <itemizedlist>
+
       <listitem>
         <formalpara>
+
           <title><literal>BACKUP</literal></title>
+
           <para>
-            This block is responsible for handling online backups. It
-            it is found in
+            This block is responsible for handling online backups. It it
+            is found in
             <filename>storage/ndb/src/kernel/blocks/backup/</filename>,
             and contains the following files:
-            
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Backup.cpp</filename></para>
-                </listitem><listitem>
-                <para><filename>BackupFormat.hpp</filename></para>
-                  </listitem><listitem>
-                <para><filename>Backup.hpp</filename></para>
-                    </listitem><listitem>
-                      <para><filename>BackupInit.cpp</filename></para>
-                    </listitem><listitem>
-                      <para><filename>Backup.txt</filename></para>
-                    </listitem><listitem>
-                      <para><filename>FsBuffer.hpp</filename></para>
-                    </listitem><listitem>
-                <para><filename>read.cpp</filename></para>
-                
+                <para>
+                  <filename>Backup.cpp</filename>
+                </para>
               </listitem>
+
+              <listitem>
+                <para>
+                  <filename>BackupFormat.hpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Backup.hpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>BackupInit.cpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Backup.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>FsBuffer.hpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>read.cpp</filename>
+                </para>
+              </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>CMVMI</literal></title>
+
           <para>
             This block is responsible for configuration management
             between the kernel blocks and the <literal>NDB</literal>
-            virtual machine. It is found in <filename>storage/ndb/src/kernel/blocks/cmvmi</filename>, and
-            contains these files:
+            virtual machine. It is found in
+            <filename>storage/ndb/src/kernel/blocks/cmvmi</filename>,
+            and contains these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Cmvmi.cpp</filename></para>
+                <para>
+                  <filename>Cmvmi.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Cmvmi.hpp</filename></para>
+                <para>
+                  <filename>Cmvmi.hpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBACC</literal></title>
+
           <para>
             This is the access control and lock management module, found
             in <filename>storage/ndb/src/kernel/blocks/dbacc</filename>.
             It contains the following files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Dbacc.hpp</filename></para>
-                </listitem><listitem>
-                  <para><filename>DbaccInit.cpp</filename></para>
-                </listitem><listitem>
-                <para><filename>DbaccMain.cpp</filename></para>
+                <para>
+                  <filename>Dbacc.hpp</filename>
+                </para>
               </listitem>
+
+              <listitem>
+                <para>
+                  <filename>DbaccInit.cpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>DbaccMain.cpp</filename>
+                </para>
+              </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBDICT</literal></title>
+
           <para>
             This block, found in
             <filename>storage/ndb/src/kernel/blocks/dbdict</filename>,
             manages metadata such as table and index definitions. This
             block contains these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>CreateIndex.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>Dbdict.cpp</filename></para>
-              </listitem><listitem>
-                <para><filename>DictLock.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>printSchemaFile.cpp</filename></para>
-              </listitem><listitem>
-                <para><filename>Slave_AddTable.sfl</filename></para>
-              </listitem><listitem>
-                <para><filename>CreateTable.new.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>Dbdict.hpp</filename></para>
-              </listitem><listitem>
-                <para><filename>DropTable.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>CreateTable.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>Dbdict.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>Event.txt</filename></para>
-              </listitem><listitem>
-                <para><filename>Master_AddTable.sfl</filename></para>
-              </listitem><listitem>
-                <para><filename>SchemaFile.hpp</filename></para>
+                <para>
+                  <filename>CreateIndex.txt</filename>
+                </para>
               </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Dbdict.cpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>DictLock.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>printSchemaFile.cpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Slave_AddTable.sfl</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>CreateTable.new.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Dbdict.hpp</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>DropTable.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>CreateTable.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Dbdict.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Event.txt</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>Master_AddTable.sfl</filename>
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <filename>SchemaFile.hpp</filename>
+                </para>
+              </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBLIH</literal></title>
+
           <para>
             This block provides data distribution management services.
             It is responsible for maintaining data fragments and
             replicas, handling of local and global checkpoints, and
             manages system restarts. It contains the following files,
             all found in the directory
-            <filename>storage/ndb/src/kernel/blocks/dbdih</filename>: 
+            <filename>storage/ndb/src/kernel/blocks/dbdih</filename>:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Dbdih.hpp</filename></para>
+                <para>
+                  <filename>Dbdih.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbdihMain.cpp</filename></para>
+                <para>
+                  <filename>DbdihMain.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>printSysfile/printSysfile.cpp</filename></para>
+                <para>
+                  <filename>printSysfile/printSysfile.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbdihInit.cpp</filename></para>
+                <para>
+                  <filename>DbdihInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>LCP.txt</filename></para>
+                <para>
+                  <filename>LCP.txt</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>printSysfile.cpp</filename></para>
+                <para>
+                  <filename>printSysfile.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Sysfile.hpp</filename></para>
+                <para>
+                  <filename>Sysfile.hpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBLQH</literal></title>
+
           <para>
             This is the local query handler block, which manages data
             and transactions local to the cluster's data nodes. It
             ismade up of the following files, found in
             <filename>storage/ndb/src/kernel/blocks/dblqh</filename>:
-            
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Dblqh.hpp</filename></para>
+                <para>
+                  <filename>Dblqh.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DblqhInit.cpp</filename></para>
+                <para>
+                  <filename>DblqhInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DblqhMain.cpp</filename></para>
+                <para>
+                  <filename>DblqhMain.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>redoLogReader/records.cpp</filename></para>
+                <para>
+                  <filename>redoLogReader/records.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>redoLogReader/records.hpp</filename></para>
+                <para>
+                  <filename>redoLogReader/records.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>redoLogReader/redoLogFileReader.cpp</filename></para>
+                <para>
+                  <filename>redoLogReader/redoLogFileReader.cpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBTC</literal></title>
+
           <para>
             This is the transaction coordinator block, which handles
             distributed transactions and other data operations on a
             global level. In the source code, it is located in the
             directory
-            <filename>storage/ndb/src/kernel/blocks/dbtc</filename>, which contains these files:
+            <filename>storage/ndb/src/kernel/blocks/dbtc</filename>,
+            which contains these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Dbtc.hpp</filename></para>
+                <para>
+                  <filename>Dbtc.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtcInit.cpp</filename></para>
+                <para>
+                  <filename>DbtcInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtcMain.cpp</filename></para>
+                <para>
+                  <filename>DbtcMain.cpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBTUP</literal></title>
+
           <para>
             This is the tuple manager, which manages the physical
             storage of cluster data. It consists of the the following
             files found in the directory
-            <filename>storage/ndb/src/kernel/blocks/dbtup</filename>: 
+            <filename>storage/ndb/src/kernel/blocks/dbtup</filename>:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>AttributeOffset.hpp</filename></para>
+                <para>
+                  <filename>AttributeOffset.hpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupDiskAlloc.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupDiskAlloc.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupIndex.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupIndex.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupScan.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupScan.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>tuppage.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>tuppage.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupAbort.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupAbort.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupExecQuery.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupExecQuery.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupMeta.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupMeta.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupStoredProcDef.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupStoredProcDef.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>tuppage.hpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>tuppage.hpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupBuffer.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupBuffer.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupFixAlloc.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupFixAlloc.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupPageMap.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupPageMap.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupTabDesMan.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupTabDesMan.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>Notes.txt</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>Notes.txt</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>Undo_buffer.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>Undo_buffer.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupCommit.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupCommit.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupGen.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupGen.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupPagMan.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupPagMan.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupTrigger.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupTrigger.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>Undo_buffer.hpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>Undo_buffer.hpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupDebug.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupDebug.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>Dbtup.hpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>Dbtup.hpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupRoutines.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupRoutines.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>DbtupVarAlloc.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>DbtupVarAlloc.cpp</filename>
+                </para>
               </listitem>
-              <listitem><para><filename>test_varpage.cpp</filename></para>
+
+              <listitem>
+                <para>
+                  <filename>test_varpage.cpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBTUX</literal></title>
+
           <para>
             This kernel block handles the local management of ordered
             indexes. It consists of the the following files found in the
             <filename>storage/ndb/src/kernel/blocks/dbtux</filename>
-            directory: 
+            directory:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>DbtuxCmp.cpp</filename></para>
+                <para>
+                  <filename>DbtuxCmp.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxGen.cpp</filename></para>
+                <para>
+                  <filename>DbtuxGen.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxMaint.cpp</filename></para>
+                <para>
+                  <filename>DbtuxMaint.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxNode.cpp</filename></para>
+                <para>
+                  <filename>DbtuxNode.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxSearch.cpp</filename></para>
+                <para>
+                  <filename>DbtuxSearch.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxTree.cpp</filename></para>
+                <para>
+                  <filename>DbtuxTree.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Times.txt</filename></para>
+                <para>
+                  <filename>Times.txt</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxDebug.cpp</filename></para>
+                <para>
+                  <filename>DbtuxDebug.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Dbtux.hpp</filename></para>
+                <para>
+                  <filename>Dbtux.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxMeta.cpp</filename></para>
+                <para>
+                  <filename>DbtuxMeta.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxScan.cpp</filename></para>
+                <para>
+                  <filename>DbtuxScan.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbtuxStat.cpp</filename></para>
+                <para>
+                  <filename>DbtuxStat.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>tuxstatus.html</filename></para>
+                <para>
+                  <filename>tuxstatus.html</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>DBUTIL</literal></title>
+
           <para>
             This block provides internal interfaces to transaction and
             data operations. It is found in
             <filename>storage/ndb/src/kernel/blocks/dbutil</filename>,
             and includes these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>DbUtil.cpp</filename></para>
+                <para>
+                  <filename>DbUtil.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbUtil.hpp</filename></para>
+                <para>
+                  <filename>DbUtil.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>DbUtil.txt</filename></para>
+                <para>
+                  <filename>DbUtil.txt</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>NDBCNTR</literal></title>
+
           <para>
             This is a cluster management block that handles block
             initialisation and configuration. It is located in
             <filename>storage/ndb/src/kernel/blocks/ndbcntr</filename>,
-            and contains these files: 
+            and contains these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Ndbcntr.hpp</filename></para>
+                <para>
+                  <filename>Ndbcntr.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>NdbcntrInit.cpp</filename></para>
+                <para>
+                  <filename>NdbcntrInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>NdbcntrMain.cpp</filename></para>
+                <para>
+                  <filename>NdbcntrMain.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>NdbcntrSysTable.cpp</filename></para>
+                <para>
+                  <filename>NdbcntrSysTable.cpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>NDBFS</literal></title>
+
           <para>
             This block provides the <literal>NDB</literal> filesystem
             abstraction layer, and is located in the directory
             <filename>storage/ndb/src/kernel/blocks/ndbfs</filename>,
             which contains the following files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>AsyncFile.cpp</filename></para>
+                <para>
+                  <filename>AsyncFile.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>CircularIndex.cpp</filename></para>
+                <para>
+                  <filename>CircularIndex.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Filename.hpp</filename></para>
+                <para>
+                  <filename>Filename.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>MemoryChannelTest/MemoryChannelTest.cpp</filename></para>
+                <para>
+                  <filename>MemoryChannelTest/MemoryChannelTest.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>OpenFiles.hpp</filename></para>
+                <para>
+                  <filename>OpenFiles.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>VoidFs.cpp</filename></para>
+                <para>
+                  <filename>VoidFs.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>AsyncFile.hpp</filename></para>
+                <para>
+                  <filename>AsyncFile.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>CircularIndex.hpp</filename></para>
+                <para>
+                  <filename>CircularIndex.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>MemoryChannel.cpp</filename></para>
+                <para>
+                  <filename>MemoryChannel.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Ndbfs.cpp</filename></para>
+                <para>
+                  <filename>Ndbfs.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Pool.hpp</filename></para>
+                <para>
+                  <filename>Pool.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>AsyncFileTest/AsyncFileTest.cpp</filename></para>
+                <para>
+                  <filename>AsyncFileTest/AsyncFileTest.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Filename.cpp</filename></para>
+                <para>
+                  <filename>Filename.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>MemoryChannel.hpp</filename></para>
+                <para>
+                  <filename>MemoryChannel.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Ndbfs.hpp</filename></para>
+                <para>
+                  <filename>Ndbfs.hpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>QMGR</literal></title>
+
           <para>
             This is the logical cluster management block, and handles
             node membership in the cluster. It contains the following
             files, found in
-            <filename>storage/ndb/src/kernel/blocks/qmgr</filename>; 
+            <filename>storage/ndb/src/kernel/blocks/qmgr</filename>;
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Qmgr.hpp</filename></para>
+                <para>
+                  <filename>Qmgr.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>QmgrInit.cpp</filename></para>
+                <para>
+                  <filename>QmgrInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>QmgrMain.cpp</filename></para>
+                <para>
+                  <filename>QmgrMain.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>timer.hpp</filename></para>
+                <para>
+                  <filename>timer.hpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>SUMA</literal></title>
+
           <para>
             The cluster subscription manager, which handles event
             logging and reporting functions. It consists of the
             following files, found in the directory
             <filename>storage/ndb/src/kernel/blocks/suma/</filename>:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Suma.cpp</filename></para>
+                <para>
+                  <filename>Suma.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Suma.hpp</filename></para>
+                <para>
+                  <filename>Suma.hpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>SumaInit.cpp</filename></para>
+                <para>
+                  <filename>SumaInit.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Suma.txt</filename></para>
+                <para>
+                  <filename>Suma.txt</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
       <listitem>
         <formalpara>
+
           <title><literal>TRIX</literal></title>
+
           <para>
             This kernel block is responsible for the building of unique
             indexes. It is found in the directory
             <filename>storage/ndb/src/kernel/blocks/trix</filename>, and
             includes these files:
+
             <itemizedlist>
+
               <listitem>
-                <para><filename>Trix.cpp</filename></para>
+                <para>
+                  <filename>Trix.cpp</filename>
+                </para>
               </listitem>
+
               <listitem>
-                <para><filename>Trix.hpp</filename></para>
+                <para>
+                  <filename>Trix.hpp</filename>
+                </para>
               </listitem>
+
             </itemizedlist>
-            
           </para>
+
         </formalpara>
-        
       </listitem>
+
     </itemizedlist>
-    
+
     <para>
       In addition, the following files are found in the
       <filename>storage/ndb/src/kernel/blocks</filename> directory:
-      
+
       <itemizedlist>
+
         <listitem>
           <para>
             <filename>diskpage.cpp</filename>
           </para>
         </listitem>
-              <listitem>
-                <para>
-                  <filename>pgman.cpp</filename>
-                </para>
-              </listitem>
+
         <listitem>
           <para>
+            <filename>pgman.cpp</filename>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <filename>restore.cpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>SystemRestart.new.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>diskpage.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>pgman.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>restore.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>SystemRestart.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>ERROR_codes.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>NodeRestart.new.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>print_file.cpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>lgman.cpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>mutexes.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>NodeRestart.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>Start.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>tsman.cpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>lgman.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>OptNR.txt</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>record_types.hpp</filename>
           </para>
         </listitem>
+
         <listitem>
           <para>
             <filename>tsman.hpp</filename>
           </para>
         </listitem>
+
       </itemizedlist>
-      
     </para>
-    
+
   </section>
-  
-  
+
   <section id="ndb-internals-glossary">
-    
+
     <title><literal>NDB</literal> Internals Glossary</title>
-    
+
     <para>
       This section contains terms and abbreviations that are found in or
       useful to understanding the <literal>NDB</literal> source code.
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">ACC</emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">ACC</emphasis>elerator or
           <emphasis role="bold">ACC</emphasis>ess manager. Handles hash
           indexes of primary keys, providing fast access to records.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">DBTC</emphasis>
         </para>
-        
+
         <para>
           The transaction coordinator.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">DIH</emphasis>
         </para>
-        
+
         <para></para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">LQH</emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">L</emphasis>ocal
           <emphasis role="bold">Q</emphasis>uery
           <emphasis role="bold">H</emphasis>andler.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold"><literal>SUMA</literal></emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">SU</emphasis>bscription
           <emphasis
             role="bold">MA</emphasis>nager.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">TC</emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">T</emphasis>ransaction
           <emphasis role="bold">C</emphasis>o-ordinator
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold"><literal>Tsman</literal></emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">T</emphasis>able<emphasis
             role="bold">s</emphasis>pace

@@ -2307,18 +2767,18 @@
             role="bold">m</emphasis>anager.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">TUP</emphasis>
         </para>
-        
+
         <para>
           <emphasis role="bold">TUP</emphasis>le. Unit of data storage.
         </para>
       </listitem>
-      
-      <!--      
+
+<!--      
         <listitem>
         <para>
         <emphasis role="bold"></emphasis>

@@ -2329,8 +2789,9 @@
         </para>
         </listitem>
       -->
-      
+
     </itemizedlist>
-    
+
   </section>
+
 </chapter>


Thread
svn commit - mysqldoc@docsrva: r6236 - trunk/ndbapijon27 Apr