Re: %TIMESTAMP renders only milliseconds?

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Alan

Seems no matter the granularity, RPG returns only milliseconds.

Cheers
Vern

On 12/6/2019 9:21 PM, Alan Campin wrote:
> With V7R2 I believe you can go from 1 to 12 digits of granularity.  Before
> V7R2, it was 6
>
> Dsply (%Timestamp(*SYS:12));
>
> DSPLY  2019-12-06-21.44.26.819000000000
>
> dcl-s Start Tiimestamp(12);
> dcl-s Duration Packed(15:0);
>
> Start = %TimeStamp(12);
> // some action
> Duration = %Diff(%Timestamp(*SYS:12)):Start:*MSeconds);
>
>
> On Fri, Dec 6, 2019 at 8:15 PM Javier Sánchez <
> javiersanchezbarquero@xxxxxxxxx> wrote:
>
> > Hi there!
> >
> > Sorry for asking if there is already something around on this.  Is the
> > %TIMESTAMP built-in function already able to render microseconds
> > granularity?
> >
> > Of course most of you know, %TIMESTAMP returns three trailing zeros after
> > the timestamp's last period.
> >
> > I had solved this inconvenient with instructions calling DB2 like:
> >
> > EXEC SQL SET :myTimeStamp = CURRENT_TIMESTAMP;
> >
> > For what I have seen, it looks like calling DB2 could be more expensive to
> > call the QWCCVTDT API to get an expression of the system's clock timestamp
> > which includes microsecond granularity instead of milliseconds.
> >
> > Please provide your comments.
> >
> > Thank you.
> >
> > JS.
> > --
> > This is the RPG programming on IBM i (RPG400-L) mailing list
> > To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> > or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/rpg400-l.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate
> > link: https://amazon.midrange.com