Retrieving timestamp with the Universal Driver

[klh]

I am working with my developer group to switch from the type 2 to the
type 4 (Universal Driver).

Our set up is:
Host Data Base - DB2 z/os v7.1 (mainframe).
Client - DB2 Admin Client V8 FP8 (Windows 2003 advanced server)
The applications are Java based.

They are reporting that when a timestamp column ends with a zero, it
gets truncated when they retrieve it from the database. For instance,
they have a column defined as a timestamp containing a timestamp of
2005-11-30-15.34.08.110140

When they use rs.getString("colname") or rs.getTimestamp("colname")
they get
2005-11-30 15:34:08.11014 (no zero at the end).

Has anyone else experienced this behavior?

Does a timestamp need to be retrieved using a different method for the
type 4 driver?

Thanks for any help,
klh

[Mark A]

"klh" <kh******@yahoo.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I am working with my developer group to switch from the type 2 to the
type 4 (Universal Driver).

Our set up is:
Host Data Base - DB2 z/os v7.1 (mainframe).
Client - DB2 Admin Client V8 FP8 (Windows 2003 advanced server)
The applications are Java based.

They are reporting that when a timestamp column ends with a zero, it
gets truncated when they retrieve it from the database. For instance,
they have a column defined as a timestamp containing a timestamp of
2005-11-30-15.34.08.110140

When they use rs.getString("colname") or rs.getTimestamp("colname")
they get
2005-11-30 15:34:08.11014 (no zero at the end).

Has anyone else experienced this behavior?

Does a timestamp need to be retrieved using a different method for the
type 4 driver?

Thanks for any help,
klh

If you are using the type 4 java, I would try the latest version (comes with
FP10). If that does not work, you probably need to open a PMR with IBM
support.

[klh]

And the answer is ...

I opened up a PMR with IBM. They showed me where this behavior is the
expected behavior for the JDBC drivers. Here is a link to where it is
documented.

http://publib.boulder.ibm.com/infoce...n/r0008474.htm
It was just a surprise to us that the drivers would display the
timestamps in a different format. In the end it wasn't a big deal.
The developers just had to reformat the date in some places.

Hopefully this will help someone else as they convert to the Universal
Drivers.

klh