DB2 FOR LUW / DB2FORLUW / A50 - DB2

Using SYSPROC.MON_GET_CONNECTION (and MON_GET_CONNECTIONS) to 
try to differentiate between secure and non-secure connections 
to a 
database. 
 
The definition of the client_protocol API element (in sqlmon.h) 
shows this should be possible. 
 
But the following example SQL returns TCPIP4 for both SSL & 
non-SSL connections. 
 
select client_protocol from 
table(sysproc.mon_get_connection(sysproc.mon_get_application_han 
dle(), -1)); 
 
REPRO: 
 
db2 update dbm cfg using svcename 50000 
db2set DB2COMM=TCPIP 
db2stop 
db2start 
db2sampl -sql -xml 
db2 catalog TCPIP node loopback REMOTE localhost SERVER 50000 
db2 catalog db sample as RSAMPLE at NODE loopback 
 
db2 connect to rsample user <USERID> using <Password> 
db2 "select client_protocol from 
table(sysproc.mon_get_connection(sysproc.mon_get_application_han 
dle(), -1))" 
 
Then need to setup and configure SSL as per: 
 
Configuring Secure Sockets Layer (SSL) support in a DB2 instance 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com. 
ibm.db2.luw.admin.sec.doc/doc/t0025241.html?lang=en 
 
Configuring Secure Sockets Layer (SSL) support in non-Java DB2 
clients 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com. 
ibm.db2.luw.admin.sec.doc/doc/t0053518.html 
 
Then repeat the above or create a new connection using the SSL 
port. 
 
db2 update dbm cfg using ssl_svcename 50010 
db2set DB2COMM=SSL,TCPIP 
db2stop 
db2start 
db2 catalog TCPIP node ssldb REMOTE localhost SERVER 50010 
db2 catalog db sample as SSAMPLE at NODE ssldb 
db2 connect to ssample user <USERID> using <Password> 
db2 "select client_protocol from 
table(sysproc.mon_get_connection(sysproc.mon_get_application_han 
dle(), -1))"

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 7 or Later.                 * 
****************************************************************

First Fixed in DB2 LUW v10.5 Fixpack 7.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

24.04.2015
21.01.2016
21.01.2016