Re: TimeStamp Problem

Updated for more SQL...
DCL-S ts1 TIMESTAMP(12);
ts1 = %timestamp(*sys : 12); // ignores precision, documented
dsply ts1; // 2015-04-17-10.04.22.888000000000
ts1 = %timestamp('2015-04-17-08.56.13.123456789012' : *iso : 12);
dsply ts1; // 2015-04-17-08.56.13.123456789012
exec sql values current_timestamp into :ts1;
dsply ts1; // 2015-04-17-10.04.22.913524000000
exec sql values current_timestamp(12) into :ts1;
dsply ts1; // 2015-04-17-10.04.22.932533985351
*inlr=*on;
return;


Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: rob@xxxxxxxxx To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 04/17/2015 09:14 AM Subject: Re: TimeStamp Problem Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> Vern, Is that for both RPG and SQL? Well, kinda sorta. I'm at 7.2 DCL-S ts1 TIMESTAMP(12); ts1 = %timestamp(*sys : 12); dsply ts1; ts1 = %timestamp('2015-04-17-08.56.13.123456789012' : *iso : 12); dsply ts1; *inlr=*on; return;

>call rob/timestamp

DSPLY 2015-04-17-09.12.19.392000000000
DSPLY 2015-04-17-08.56.13.123456789012


Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 04/16/2015 05:43 PM Subject: Re: TimeStamp Problem Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> 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