Return-Path: 
 <commits-return-3316-apmail-openjpa-commits-archive=openjpa.apache.org@openjpa.apache.org>
Delivered-To: apmail-openjpa-commits-archive@www.apache.org
Received: (qmail 41138 invoked from network); 25 Aug 2008 20:03:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 25 Aug 2008 20:03:15 -0000
Received: (qmail 25890 invoked by uid 500); 25 Aug 2008 20:03:13 -0000
Delivered-To: apmail-openjpa-commits-archive@openjpa.apache.org
Received: (qmail 25882 invoked by uid 500); 25 Aug 2008 20:03:13 -0000
Mailing-List: contact commits-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@openjpa.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@openjpa.apache.org>
List-Post: <mailto:commits@openjpa.apache.org>
List-Id: <commits.openjpa.apache.org>
Reply-To: dev@openjpa.apache.org
Delivered-To: mailing list commits@openjpa.apache.org
Received: (qmail 25873 invoked by uid 99); 25 Aug 2008 20:03:13 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2008 13:03:13 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2008 20:02:24 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
	id 19A4A2388970; Mon, 25 Aug 2008 13:02:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r688855 -
 /openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
Date: Mon, 25 Aug 2008 20:02:23 -0000
To: commits@openjpa.apache.org
From: kwsutter@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20080825200224.19A4A2388970@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: kwsutter
Date: Mon Aug 25 13:02:23 2008
New Revision: 688855

URL: http://svn.apache.org/viewvc?rev=688855&view=rev
Log:
OPENJPA-702.  Update documentation for the DESCSTAT parameter for DB2 on z/OS.

Modified:
    openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml

Modified: openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml?rev=688855&r1=688854&r2=688855&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Mon Aug 25 13:02:23 2008
@@ -429,20 +429,30 @@
 extending <classname>DB2Dictionary</classname>.
                     </para>
                 </listitem>
-                <listitem>
-                    <para>
-Explicit creation of indexes specified by the OpenJPA @Index annotation will 
-fail on DB2 for iSeries if the default schema used by the JDBC driver does not 
-exist.  If a default schema is not specified on the connection, the iSeries 
-will default to the user profile name.  If a schema of that name does not 
-exist, DB2 on iSeries will not create the schema, resulting in a failure when 
-creating the index.  The failure message will look similar to: "[SQL0204] 
-USERNAME in QSYS type *LIB not found."  To work around this issue, specify a 
-default schema on the JDBC URL or data source property and make sure that 
-schema exists or create a schema which matches the user profile of the 
-connection.
-                    </para>
-                </listitem>
+                <listitem>
+                    <para>
+Explicit creation of indexes specified by the OpenJPA @Index annotation will 
+fail on DB2 for iSeries if the default schema used by the JDBC driver does not 
+exist.  If a default schema is not specified on the connection, the iSeries 
+will default to the user profile name.  If a schema of that name does not 
+exist, DB2 on iSeries will not create the schema, resulting in a failure when 
+creating the index.  The failure message will look similar to: "[SQL0204] 
+USERNAME in QSYS type *LIB not found."  To work around this issue, specify a 
+default schema on the JDBC URL or data source property and make sure that 
+schema exists or create a schema which matches the user profile of the 
+connection.
+                    </para>
+                </listitem>
+                <listitem>
+                    <para>
+Use of DB2 on z/OS with the IBM JCC driver requires the DESCSTAT subsystem 
+parameter value to be set to 'YES'.  If this parameter is set to 'NO', the 
+mapping tool will fail with a persistence exception containing this text: 
+"Invalid parameter: Unknown column name TABLE_SCHEM".  After changing the value 
+of DESCSTAT, DB2 metadata tables must be recreated by running the DSNTIJMS job. 
+See DB2 for z/OS documentation for additional information.
+                    </para>
+                </listitem>
             </itemizedlist>
         </section>
     </section>
@@ -1004,19 +1014,19 @@
 procedure.</literal> ".
                     </para>
                 </listitem>
-                <listitem>
-                    <para> 
-Applications performing update/insert data of the BigDecimal java type may fail 
-with OptimisticException if the data exceeds the scale or precision of the
-column on Sybase. To avoid this problem, applications can specify the precision
-and scale for the numeric type by setting numericTypeName='NUMERIC(p,s)' for
-the column type mapped by the BigDecimal java type. See
-<link linkend="openjpa.jdbc.DBDictionary">openjpa.jdbc.DBDictionary</link> for
-more detail. Alternatively, application can set the precision and scale using
-the standard <classname>Column</classname> annotation, described in
-<xref linkend="jpa_overview_mapping_column"/>.
-                    </para>
-                </listitem>
+                <listitem>
+                    <para> 
+Applications performing update/insert data of the BigDecimal java type may fail 
+with OptimisticException if the data exceeds the scale or precision of the
+column on Sybase. To avoid this problem, applications can specify the precision
+and scale for the numeric type by setting numericTypeName='NUMERIC(p,s)' for
+the column type mapped by the BigDecimal java type. See
+<link linkend="openjpa.jdbc.DBDictionary">openjpa.jdbc.DBDictionary</link> for
+more detail. Alternatively, application can set the precision and scale using
+the standard <classname>Column</classname> annotation, described in
+<xref linkend="jpa_overview_mapping_column"/>.
+                    </para>
+                </listitem>
             </itemizedlist>
         </section>
     </section>