DB2 FOR LUW / DB2FORLUW / A10 - DB2

In a DB2DBDFT environment implicit  CONNECT RESET unsets session
variables. See the following example:

    db2set DB2DBDFT=repro
    db2 create db repro
    db2 connect to db repro
    db2 "create procedure test.proc(OUT a CHAR(32)) begin set a
= application_id(); end"
    db2 terminate
    # repeat the following steps
    db2 "values(substr(application_id(),1,32))"
    db2 "call test.proc(?)"
    db2 "values(substr(application_id(),1,32))"
    db2 terminate

While using here the CALL statement there is a a new connection
and reset made to an already existing connection. What happens
is the implicit CONNECT RESET when in a DB2DBDFT environment. In
this demonstration the application ID changes as evidence of the
CONNECT RESET.

This reset has ramifications for SESSION variables - they change
because the session has changed.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* This is currently a limitation                               *
****************************************************************

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.03.2017
08.05.2017
08.05.2017