A fix is available
APAR status
Closed as program error.
Error description
IFCID376 trace record for incompatibilities can contain an unexpected SQL query.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 11 for z/OS users of the CHAR9 and * * VARCHAR9 scalar functions with the IFCID 366 * * or IFCID 376 trace. * **************************************************************** * PROBLEM DESCRIPTION: The IFCID376 trace record for * * incompatibilities can contain an * * unexpected SQL query or incorrect * * information when using the CHAR9 or * * the VARCHAR9 scalar functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** The IFCID376 trace record for incompatibilities can contain unexpected or incorrect information when running a query that includes the CHAR9 or VARCHAR9 scalar function. The following scenario shows how the problem can occur. Step 1. Setup or start an IFCID376 Trace. -START TRACE(P) CLASS(32) IFCID(376) DEST(SMF) DB2 writes a single trace record for each SQL statement that is incompatible with the subsequent DB2 release. Step 2. Execute a query (such as these) which can invoke tracing after setting the application compatibility special register. SET CURRENT APPLICATION COMPATIBILITY = 'V11R1'; SELECT VARCHAR9(DEC(1.5) ) FROM SYSIBM.SYSDUMMY1; SELECT CHAR9(CURRENT TIMESTAMP - (CURRENT TIMESTAMP - 5 DAYS)) FROM SYSIBM.SYSDUMMY1; Step 3. Stop or terminate the trace. -STOP TRACE(P) CLASS(32) IFCID(376) DEST(SMF) Step 4. Review the trace data. The trace data may contain unexpected information. For example, for the particular SQL statement, it could mention that the CHAR9 or the VARCHAR9 functions are incompatible when they are not. Please note: A similar problem can occur when using an IFCID366 trace.
Problem conclusion
The code in DB2 has been modified to correct the condition when issuing an IFCID376 (or IFCID366) trace record. Additional Keywords: IFCID376 IFCID366
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI64321
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-15
Closed date
2016-10-05
Last modified date
2016-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI68141 UI41440
Modules/Macros
DSNXRSBC
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI41440
UP16/10/24 P F610
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 November 2016