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 IC77956 Status: Closed

CLI0118E INVALID SQL SYNTAX WHEN PARAMETER LISTING CONTAINS NEW LINE
CHARACTER

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When a stored procedure is called from a CLI based application 
and the parameter listing has a new line character separating 
parameters, such as after PARAM1 in the following: 
 
CALL SYSPROC.DSNTPSMP('PARAM1', 
'PARAM2') 
 
 
The following error may occur: 
CLI0118E  Invalid SQL syntax. SQLSTATE=37000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CLI0118E  INVALID SQL SYNTAX WHEN PARAMETER LISTING CONTAINS * 
* NEW LINE CHARACTER                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9                        * 
****************************************************************
Local Fix:
Remove the new line character and separate the parameters by 
spaces instead.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5 Fix Pack 9
Workaround
Remove the new line character and separate the parameters by 
spaces instead.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.08.2011
12.03.2012
26.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList