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


  1.  Home
  2. RPG400-L
  3. February 2022

Re: %TIMESTAMP question

On 2022-02-03 5:15 p.m., DEnglander--- via RPG400-L wrote:
I have a table defined using DDL with a 12 position timestamp
[TIMESTAMP(12)].

I am writing to it via RPGLE. When I populate the field using '=
%timestamp(*SYS : 12)' and write the record, the resulting field always
contains six zeros as the last digits in the timestamp.

We are at TR 11 on V7R3.

Am I doing something wrong, or will I always get the last six as zeros?


%TIMESTAMP only returns microsecond precision.

For %TIMESTAMP(*UNIQUE), the last 6 digits of a timestamp(12) are non-zero, but they only serve to make the timestamp unique from the previous one. The timestamp still only has microsecond precision.

For %TIMESTAMP without *UNIQUE, the last 6 digits os a timestamp(12) will always be zero.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.