DB2 CONNECT / DB2CONNCT / A10 - DB2

The following error may occur from a CLI/ODBC application when 
calling a stored procedure with a timestamp supplied as a 
literal value for an output parameter: 
CLI0113E  Invalid date/time format 
 
This works fine when when the implicit cast feature is enabled 
but when it is disabled (via DB2 for z/OS APAR PM77180), and 
any datatype mismatch, server hit -301 error and cli will retry. 
while retrying validation is being done on the timestamp literal 
value that is supplied for the output parameter.  If the value 
supplied is not a valid timestamp value (For example, an empty 
string '') the CLI0113E error will occur. 
 
This APAR will replace the output literal value to a null 
indicator even when the parameter is not bound but has the 
values supplied during call.  This will avoid the CLI0113E error

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 CLI Users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.1.4 or later                                   * 
****************************************************************

As a workaround, supply a value for the timestamp output 
parameter that has a valid timestamp format.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Upgrade to 10.1.4 or later

not known / see Local fix

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

14.10.2013
26.06.2014
26.06.2014