In release 7.2 timestamps (RPG and SQL) can be defined with 0 to 12 micro
seconds.
The missing microseconds are simply not populated.
DDS is not enhanced, so if you are still defining files with DDS timestamps
are restricted to 6 micro seconds.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Dan
Gesendet: Friday, 17.4 2015 18:40
An: Midrange Systems Technical Discussion
Betreff: Re: TimeStamp Problem
We're still on v7r1 here. How does the new 12 digit precision affect
timestamp fields in tables defined prior to v7r2? With the additional 6
digits, I presume that more space is needed to store them than before.
Also, because when you absolutely, positively must have a unique key but
can't rely on a timestamp (even with 12 digit precision for the second!) to
provide it, what was the impetus to increase the precision? Curious
mind(s?) wants to know.
(Interesting story about GM and the COBOL compiler, Jon!)
- Dan
On Thu, Apr 16, 2015 at 5:42 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
At 7.2 the timestamp precision has been increased - you can now go up
to
12 digits in the fraction of seconds.
We're not yet on 7.2, so it'd interesting to hear the experience of
others in this.
Vern
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
