Yes, it is. The question is what a "timestamp" actually comprises. In database logs, it could be just a counter, possibly provided by a sysplex timer, or a CPU internal clock, a real-world timestamp, or something else. Since DB2 provides the capability to roll-forward through logs to a specific point in time, a real-world timestamp is needed at least for COMMIT/ROLLBACK to decide whether a transaction completed before the desired PIT.