APAR status |
Closed as documentation error.
| Error description
datasources.xml is only way to change the CURSORHOLD option
when using WAS datasource. but there is no clear documentation
for this.
UDB default is CURSORHOLD=1. however WAS datasource create a
connection with CURSORHOLD=0 by the default.
This deference made confusion to customer.
Specific application was working fine under JDBC direct
connection with setAutoCommit(true) (jdbc default) mode.
but failed with CLI0125E sequence error, if switch to using WAS
datasource because CURSORHOLD is set to 0.
require clear documentation way to change CURSORHOLD option
in WAS datasource and The technical reason why WAS using
CURSORHOLD=0 by the default. Local fixProblem summary
Datasources.xml is only way to change the CURSORHOLD option
when using WAS datasource, but there is no clear documentation
for this. Document in info center / release notes for 3.5
that this value can be modified in the datasources.xml.
Also.. please doc that WAS sets the DATASOURCE=0 as default. Problem conclusionTemporary fixComments
APAR information | APAR number | PQ49737 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-06-19 | Closed date | 2001-07-05 | Last modified date | 2001-07-05 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|