Kbase P185925: How to identify the Data Direct Driver created package on the AS/400?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/04/2011 |
|
Status: Unverified
GOAL:
How to identify the Data Direct Driver created package on the AS/400?
GOAL:
How to identify the Data Direct driver packages created by ODBC DSN when ODBC DSN is created on Windows and test connected to verify if the DSN is successfully created?
FACT(s) (Environment):
Windows
AS/400 iSeries Server
OpenEdge 10.x
ODBC DataServer
FIX:
Package usage is based on the isolation level and the cursor behavior configured and used for the driver. Likewise, the package names are based on isolation level, cursor behavior, and a few other factors:
The Package Naming Convention is:
DDpiVRMx
This name is derived as follows:
DD -> Static identifier indicating a DataDirect product
p -> product identifier
(A) = ADO .NET
(J) = JDBC
(O) = ODBC
i -> isolation level used (C,S,R,U,N)
(C)ommited Read (ANSI): DB2 CS ==> DRDA ISOLLVL CS
(S)erializable (ANSI): DB2 RR ==> DRDA ISOLLVL RR
(R)epeatable Read (ANSI): DB2 RS ==> DRDA ISOLLVL ALL
(U)ncommited Read (ANSI): DB2 UC ==> DRDA ISOLLVL CHG
(N)ot committed: DB2 NC (only applies to DB2 on AS400, iSeries) ==> DRDA ISOLLVL NC
VRM -> VersionReleaseModification e.g 210
This is the package version. This does not correspond to the version of the product using the packages.
x -> Package suffix ( a letter from A-Z ) that differentiates between the packages:
A - Package with cursors closed at commit
B - Package with cursors held over commit
C - Package used for non-prepared stored procedure execution (not created on AS/400)
D-Z - Saved for future use. (Static SQL, system queries, etc)
The initial isolation configuration can be found in the DSN configuration for "DefaultIsolationLevel", however, the cursor behavior and isolation levels are subject to change based on what the ODBC application does.