A fix is available
APAR status
Closed as program error.
Error description
After migration to DB2 10, SQLCODE -180 is issued for an unsupported timestamp string. Previous releases may not have correctly issued the -180 SQLCODE for some unsupported timestamp strings. SQLCODE -181 is issued incorrectly for a timestamp string with trailing blanks, which is valid format. Additional keywords: SQLCODE180 SQLCODE181 INCORROUT
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 users of timestamp strings * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -180 after migration to DB2 * * 10 for an unsupported timestamp string. * * Previous releases may not have * * correctly issued the -180 SQLCODE for * * some unsupported timestamp strings. * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem 1. If the DB2 subsystem parameter BIF_COMPATIBILITY is set to V9, DB2 will write an IFCID 366 trace record with QW0366FN = 3 for applications that are using unsupported timestamp strings where DB2 did not correctly issue -180 in a previous release. This trace record can be used to identify applications that need to be modified to use a correctly formatted timestamp string as documented in the DB2 for z/OS SQL Reference. Problem 2. This apar also fixes an incorrect SQLCODE -181 for the following timestamp format where there are trailing blanks. For example, SELECT 1 FROM T1 WHERE TIMESTAMPCOL <= :HV The host variable has the value '2012-05-09-00.00.00. '. Note the trailing blanks. This format is valid and an SQLCODE -181 is incorrectly returned. Note the BIF_COMPATIBILITY zparm value does not affect this result. This fix is independent of the BIF_COMPATIBILITY fix in problem 1.
Problem conclusion
DB2 has been modified to write the IFCID 366 record with new function type 3 (QW0366FN = 3) to indicate unsupported timestamp string. Please see PM29124/UK67578 for details on the BIF_COMPATIBILITY system parameter and IFCID 366. Additional keywords : SQLMIGRATION IFCID366 SQLTIMESTAMP
Temporary fix
Comments
APAR Information
APAR number
PM48741
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-26
Closed date
2011-12-13
Last modified date
2012-05-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74765
Modules/Macros
DSNDQW05 DSNXOLTD DSNXRDEC DSNXRGPL DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 DSNXRITV DSNXRIT9 DSNXRLET DSNXRSBC DSNXRSB9 DSNXRSPL DSNXRTIM DSNXVDTT DSNXVDT2
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK74765
UP11/12/28 P F112
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:
09 May 2012