|
Problem IC61417
|
Status: Closed |
11.50.XC4W1: DRDA CLIENTS DO NOT RECOGNIZE SETTINGS IN SYSDBOPEN |
| product: |
IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50 |
| Problem description: |
With 11.50.xC4W1 the settings in sysdbopen are not recognized
when a client connects via Data Server Driver.
CREATE PROCEDURE "public".sysdbopen()
SET LOCK MODE TO WAIT;
SET ENVIRONMENT USELASTCOMMITTED 'COMMITTED READ';
SET ISOLATION TO COMMITTED READ RETAIN UPDATE LOCKS;
END PROCEDURE;
IBM Informix Dynamic Server Version 11.50.FC4W1 -- On-Line --
Up 13:33:46 -- 174820 Kbytes
Sess SQL Current Iso Lock SQL
ISAM F.E.
Id Stmt type Database Lvl Mode ERR
ERR Vers Explain
68 SELECT mydb CR Not Wait 0
0 - Off
The same works in 11.50.FC4:
IBM Informix Dynamic Server Version 11.50.FC4 -- On-Line --
Up 00:01:00 -- 166628 Kbytes
Sess SQL Current Iso Lock SQL
ISAM F.E.
Id Stmt type Database Lvl Mode ERR
ERR Vers Explain
9 SELECT mydb LCU Wait 0
0 - Off |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of SYSDBOPEN() procedure *
****************************************************************
* PROBLEM DESCRIPTION: *
* SYSDBOPEN() is not executed with DRDA clients. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.50.xC5 and above. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem first fixed in IDS 11.50.xC5. . DRDA client was
included into the list of clients capable of executing
sysdbopen() routine |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.06.2009
19.01.2010
19.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
11.50.xC5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 11.50.xC5
|
 |
