Author: kwsutter
Date: Mon Aug 25 13:07:28 2008
New Revision: 688856
URL: http://svn.apache.org/viewvc?rev=688856&view=rev
Log:
OPENJPA-702. Update documentation for the DESCSTAT parameter for DB2 on z/OS.
Modified:
openjpa/branches/1.2.x/openjpa-project/src/doc/manual/supported_databases.xml
Modified:
openjpa/branches/1.2.x/openjpa-project/src/doc/manual/supported_databases.xml
URL:
http://svn.apache.org/viewvc/openjpa/branches/1.2.x/openjpa-project/src/doc/manual/supported_databases.xml?rev=688856&r1=688855&r2=688856&view=diff
==============================================================================
---
openjpa/branches/1.2.x/openjpa-project/src/doc/manual/supported_databases.xml
(original)
+++
openjpa/branches/1.2.x/openjpa-project/src/doc/manual/supported_databases.xml
Mon Aug 25 13:07:28 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>
