We have a Log Analyzer Tool running on our DB2 OLTP hosted on the z/OS - the tool captures the date/time of change to every record in every table the tool is configured to monitor.
HOWEVER!!!! the field that captures the timestamp of the change is CHAR(08) is HH:MMS - clearly a lot of times, this is not enough precision to be able to distinguish between successive changes made to the same record in a table.
Question - is there a way of bumping up the LAT TIME precision to include microseconds????