HEX timestamp in AS/400 QHST

[draves]

I wrote the following page against the QHST History Log files on the AS/400. When I don't have a WHERE clause the extraction of the timestamp ends up in the 1870s but the calculation in ColdFusion seems right. When I limit the records selected as below both seem to give dates that match each other to the second but are off by up to half a minute from looking at the output of the DSPLOG program . Is there a better way to do the Hex conversions and get high numeric precision?

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/qwccvtdt.htm
http://publib.boulder.ibm.com/tividd/td/TWS/SC32-1266-00/en_US/HTML/Eqqn1mst175.htm
http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/com.ibm.etools.iseries.orxw....
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r00008...

[draves · Accepted solution]

Had to do a dummy select to preset the variable types to stop the bad extraction of the timestamps in the 1870s. The microseconds have to be added separately if that much precision is desired.