× 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.



 

Have a problem with TimeStamp resolution. Have a conversion program that is
using an Audit File to record events of the processing. The DDS for this
file defines it as a unique keyed file with a TimeStamp type field as the
unique key value. The conversion program extracts the current TimeStamp
value using op code TIME. As you all know this returns a TimeStamp value
with seconds down to only three places while the format allows for six. The
processing in this program can generate audit records at a rate which faster
then the resolution of the TIME timestamp and resulted in "Duplicate Record"
messages. A work around using a save timestamp value last used and a check
to see if the current timestamp gets around the problem.

 

My question - is there a method by which I can extract the timestamp value
to its full definition value?

 

Jack Derham

Direct Systems, Inc.

 

 

 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.