DB2 - Problem description
Problem IC89366 | Status: Closed |
CLPPLUS SHOULD NOT GET INTO INTERACTIVE MODE WHEN USER SPECIFIES INCORRECT CREDENTIALS IN THE CONNECT STRING GIVEN WHILE LAUNCHI | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Currently when a user launches CLPPlus (Windowed or Non Window mode) specifying the connection parameters, and due to some reason, the connection fails to establish, CLPPlus launches and connection parameters are requested: CLPPlus: Version 1.6 Copyright (c) 2009, 2011, IBM CORPORATION. All rights reserved. [jcc][t4][2043][11550][4.16.8] Exception java.net.ConnectException: Error opening socket to server regrlnxamd07.torolab.ibm.com/9.26.93.154 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499, SQLSTATE=08001 Enter DATABASE NAME [Sample]: The user wants the behavior to be changes such that: When connection fails to establish, the user CLPPlus should be launched and error message should be displayed and a message prompt should be displayed which requests the user to press ENTER key in order to exit the winodw: CLPPlus: Version 1.6 Copyright (c) 2009, 2011, IBM CORPORATION. All rights reserved. [jcc][t4][2043][11550][4.16.8] Exception java.net.ConnectException: Error opening socket to server regrlnxamd07.torolab.ibm.com/9.26.93.154 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499, SQLSTATE=08001 Connection failed to be established. Press enter to Exit. | |
Problem Summary: | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Comment | |
This APAR is to correct the default behavior of CLPPlus window, such that CLPPlus window is not launched when user gives incorrect connect string while launching CLPPlus. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91752 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.01.2013 01.04.2013 01.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |