Re: save file (was) C version of ADDLC on very long variables

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-GDFlLPZ4eRKEK/[email protected] 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?
> 
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.