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

THE DB2_ALL COMMAND MAY FAIL WITH A KSH SYNTAX ERROR WHEN SINGLE QUOTES
APPEAR IN THE COMMAND.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Problem Description: 
In DPF environment the db2_all command may fail with a ksh 
syntax error when a single quote appears within single quotes. 
For example : 
 
db2_all "db2 'values(current DBPARTITIONNUM)' " 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. 
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF environment.                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fix Pack 10.                          * 
****************************************************************
Local Fix:
Possible workarounds are : 
1. db2_all "db2 values\(current DBPARTITIONNUM\) "  or 
2. db2_all 'db2 "values(current DBPARTITIONNUM)" '
Solution
Fixed in Version 9.5 Fix Pack 10.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC81994 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2011
31.08.2012
31.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList