suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT29195 Status: Closed

CLPPLUS DOES NOT RUN THE LOGIN.SQL SCRIPT DURING STARTUP.

product:
DB2 CONNECT / DB2CONNCT / B10 - DB2
Problem description:
CLPPlus does not run the login.sql script during startup. Hence
could not use the variables defined in the connect command

Documentation reference:

https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com
.ibm.swg.im.dbclient.clpplus.doc/doc/r0053952.html


Fix related information
=================
The APAR IT29195 was supposed to deliver in v11.1m4fp5 but due
to some reason it failed and new delivery will be to v11.5m4fp0
=================
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* 2                                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Please upgrade to  V11.5m4fp0                                *
*                                                              *
*                                                              *
* The APAR IT29195 was supposed to deliver in v11.1m4fp5 but   *
* due to some reason it failed and new delivery will be to     *
* v11.5m4fp0                                                   *
****************************************************************
Local Fix:
NA
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2019
22.05.2020
22.05.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)