|
Problem IC64705
|
Status: Closed |
COMMAND EDITOR FAIL TO EXPORT TIMESTAMP IN ISO FORMAT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The DB2 Command Editor version 8.1.13 running against DB2 UDB
for z/OS
version 8.1 has an export function, where we can specify that
dates are
exported in ISO format. That works for DATE data types but not
for
TIMESTAMP.
If we use the date format ISO in the export, the DATE datatype
is in the
format:
2006-10-09
But the TIMESTAMP datatype is still exported as:
Oct 9, 2006 8:42:16 AM 998309 |
| Problem Summary: |
|
| Local Fix: |
|
| 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 |
|
| Workaround |
not known / see Local fix |
| Comment |
Using Close code ISV as CAN is not working with closed
defects.The APAR was opened not knowing that it will be merged
from v95fp5 to v97fp1 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.11.2009
24.02.2010
24.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
