A fix is available
APAR status
Closed as program error.
Error description
When SQL statement gets SQLERROR (e.g. SQLCODE330), an improper SQLCA processing may happen, which results in incorrout for sequential case, or parent loop in DSNXPSRD for //ism case.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * * of queries containing predicates. * **************************************************************** * PROBLEM DESCRIPTION: Improper SQL error processing can occur * * for a query involving predicates when * * the query is being executed * * sequentially. If the query is executed * * with parallelism, a loop can occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** Improper SQL error processing can occur for a query involving predicates. When DB2 is processing a query with predicates and an SQLCODE -330 (SQLCODE330) or -332 (SQLCODE332) error is expected, the error message may not be properly formatted when the query is running sequentially. Additionally, if the query is executed with parallelism, a loop can occur. There are many reasons that DB2 will issue an SQLCODE -330 or -332. One scenario is when converting a UNICODE string into an EBCDIC string and the resulting string is not a valid EBCDIC string. In this case, DB2 is supposed to issue an SQLCODE. But, due to the processing error, no SQLCODE is formatted for certain cases.
Problem conclusion
The code in DB2 has been modified to process SQL errors properly so that the error will be externalized as expected. So, the correct SQL code will be issued which will prevent the incorrect result from being returned for the sequential case or the looping condition for the parallel case. Additional Keywords: SQLCODE330 SQLCODE332 SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K DB2PARALL/K PARALLELISM SQLPARALLELISM
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM81500
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-28
Closed date
2013-06-19
Last modified date
2013-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK95252 UK95253
Modules/Macros
DSNXRFC DSNXRFC9
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 August 2013