Developer extension alternating between 2 connections prevents use of special registers & global variables
Opened this issue · 1 comments
PaulMcW commented
Development environment where the bug occurred
- Db2 Developer Extension version:
- Editor platform
- Visual Studio Code
- Eclipse Theia
- Editor platform version:
- Operating system on which your editor runs (for example, Windows 10 2004 or MacOS Catalina 10.15.7):
MacOS Sonoma - Version 14.6.1 (23G93)
- Java Version (Run
java -version
and paste the details here):java version "1.8.0_311" Java(TM) SE Runtime Environment (build 1.8.0_311-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode)
- Db2 for z/OS version (including function level for Db2 12): Db2 13 for z/OS function level V13R1M501
- Log files attached?: No
Problem description
Detailed steps for reproducing the problem:
- Connect to Db2 with SYSADM
- Issue the following following statement:
SET CURRENT SQLID = 'ADMF002';
- Select the current SQLID repeatedly (run separately):
SELECT CURRENT SQLID FROM SYSIBM.SYSDUMMY1;
Observed behavior
- Each subsequent running of SQL statements seems to return alternating SQLID values. That is, one SELECT of the CURRENT SQLID returns the new value 'ADMINF001', the next returns 'SYSADM', the next returns 'ADMINF001' again, and so forth.
- The same problem is observed for other things such as global variables.
- The problem seems to be that Db2 Developer Extension is opening two connections and alternating between them for subsequent SQL statement runs.
DSNL200I -DB2A DISPLAY LOCATION REPORT FOLLOWS-
LOCATION PRDID T ATT CONNS
::FFFF:9.52.238.50 JCC04320 S 2
L209-FUNCTIONAL LEVEL=28
::FFFF:9.61.111.242 JCC04320 S 0
L209-FUNCTIONAL LEVEL=28
DISPLAY LOCATION REPORT COMPLETE
Expected behavior
-Successive runs of the following statement should always return the same value, unless it is changed in between:
SELECT CURRENT SQLID FROM SYSIBM.SYSDUMMY1;
DilipAgnihotriIBM commented
We’re on it and will keep you updated on our progress