|
Problem IC62187
|
Status: Closed |
DB2LSNTOSTRING RETURNING ERROR 'OSS_PRI16X64' : UNDECLARED IDENTIFIER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When attempting to use the db2LsnToString() API routine in a
user created program, the compilation of the program will fail
with an error stating that OSS_PRI16X64 is an undeclared
identifier. The actual text of the error message will vary
according to the compiler and platform used. The following is a
Windows example produced by the Microsoft Visual Studio C
compiler:
error C2065: 'OSS_PRI16X64' : undeclared identifier
Currently, db2LsnToString() API routine is defined in db2ApiDf.h
in the following way:
#define db2LsnToString(_inLsn, _outStr) \
sprintf(_outStr, OSS_PRI16X64, (_inLsn).lsnU64)
The problem is that 'OSS_PRI16X64' is an internal DB2 symbol
whose definition is not shipped. |
| Problem Summary: |
see APAR |
| Local Fix: |
Redefine db2LsnToString() in the following way:
#define db2LsnToString(_inLsn, _outStr) \
sprintf(_outStr, "%016X", (_inLsn).lsnU64) |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 UDB 9.7 FixPak 1 |
| Workaround |
see APAR |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.07.2009
22.12.2009
22.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
