home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT06599 Status: Closed

DB2 VARCHAR_BIT_FORMAT ALLOWING ODD LENGTH INPUT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 function HEXTORAW (VARCHAR_BIT_FORMAT) does not accept odd 
length input. 
 
Note the HEXTORAW function is a synonym for the 
VARCHAR_BIT_FORMAT 
function with a single argument. 
 
 
The documentation states: 
"the length must be an even number of characters" 
 
And the following call produces an error: 
 
db2 "select VARCHAR_BIT_FORMAT('ABC') from sysibm.sysdummy1" 
 
1 
----- 
SQL0171N  The statement was not processed because the data type, 
length or 
value of the argument for the parameter in position "1" of 
routine 
"SYSIBM.VARCHAR_BIT_FORMAT" is incorrect. Parameter name: 
"character-expression".  SQLSTATE=42815 
 
This APAR will allow for the this function to accept odd length 
input with the output having a 
zero appended to it, optionally enabled by a registry variable. 
 
eg: 
 
db2 "select VARCHAR_BIT_FORMAT('ABC') from sysibm.sysdummy1" 
 
1 
------- 
x'ABC0' 
 
  1 record(s) selected. 
 
To enable this functionality, set the following registry 
 
DB2_RUNTIME_DEBUG_FLAGS=DISABLE_BLANK_TOLERANCE 
 
Under SAP workloads, this is enabled by default 
 
Setting DB2_WORKLOAD=SAP will set 
DB2_RUNTIME_DEBUG_FLAGS=DISABLE_BLANK_TOLERANCE.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 V10.5.FixPack7                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 V10.5.FixPack7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.01.2015
19.01.2016
19.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList