× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I haven't seen any cases where it's earlier, but I haven't been paying
attention.

I just tried SAVOBJ, SAVLIB & SAV on V5R1 and V5R3, and in all cases the
 timestamp in the first record was a few seconds later.

(I think the DSPSAVF timestamp comes from the record that contains the
CPU serial number.)

In the cases where it's earlier, is there any correlation with OS
release or SAV- command (or anything else)?

The only explanation I can think of would be if the two timestamps were
written by different LIC tasks whose relative timing was dependent on
system load.

--Dave

Gene_Gaunt@xxxxxxxxxxxxxxx wrote:
Thanks a lot.

Strange how a timestamp appears in the save file first eight bytes, which,
when converted through QWCCVTDT API, is "close to" the time of the save
command shown on the DSPSAVF panel, but sometimes it's later by 2 or 3
seconds, and sometimes it's earlier by 2 or 3 seconds.

Any guess why this would be?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.