Date: Thu, 30 Sep 2010 10:49:15 -0500
Reply-To: Joe Matise <snoopy369@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Joe Matise <snoopy369@GMAIL.COM>
Subject: Re: Datetime displays incorrectly
In-Reply-To: <FA0550A1D186FF49BB0748CD711B17ED7E790F720B@SDPSMSX.QUALNET.ORG>
Content-Type: text/plain; charset=ISO-8859-1
Like this one?
http://support.sas.com/kb/15/924.html
It claims to be fixed in hotfix E9BB78 .
-Joe
On Thu, Sep 30, 2010 at 10:32 AM, Bian, Haikuo <HBian@flqio.sdps.org> wrote:
> Jim and Marty,
>
> My workstation is running winxp pro , version 2002, sp3. Hardware: CPU
> intel core duo E6850, 3Ghz, 4G Ram (well, uses 3.23G due to the 32bit
> system), SAS 9.1.3.
>
> The result seems normal:
>
> 511 data _null_;
> 512 dt="28SEP10:16:44:00.672"dt;
> 513 format dt 15.3;
> 514 put dt datetime19.2;
> 515 put dt datetime20.3;
> 516 put dt datetime21.4;
> 517 put dt datetime22.5;
> 518 put dt datetime23.6;
> 519 put dt datetime24.7;
> 520 put dt datetime28.5;
> 521 run;
>
> 28SEP10:16:44:00.67
> 28SEP10:16:44:00.672
> 28SEP10:16:44:00.6720
> 28SEP10:16:44:00.67200
> 28SEP10:16:44:00.672000
> 28SEP10:16:44:00.6719999
> 28SEP2010:16:44:00.67200
>
>
>
> Our IS team is very good at applying updates and hot-fix for SAS. Maybe it
> is a bug that can be fixed by one of hundreds of hot-fixes?
>
> Just my 2 cents.
>
> Haikuo
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Jim
> Groeneveld
> Sent: Thursday, September 30, 2010 4:27 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: Datetime displays incorrectly
>
> Hi Art,
>
> My laptop has Windows XP Pro, vs 2002, sp3 and both SAS 9.1.3 and 9.2.
> I fed the following program into SAS:
>
> data _null_;
> dt="28SEP10:16:44:00.672"dt;
> format dt 15.3;
> put dt datetime19.2;
> put dt datetime20.3;
> put dt datetime21.4;
> put dt datetime22.5;
> put dt datetime23.6;
> put dt datetime24.7;
> put dt datetime28.5;
> run;
>
> It shows from SAS 9.1.3:
>
> 28SEP10:16:44:00.67
> 28SEP10:16:44:00.672
> 28SEP10:16:44:00.6720
> 29SEP10:00:00:00.00000
> 29SEP10:00:00:00.000000
> 28SEP10:16:44:00.6719999
> 29SEP2010:00:00:00.00000
>
> and from SAS 9.2:
>
> 28SEP10:16:44:00.67
> 28SEP10:16:44:00.672
> 28SEP10:16:44:00.6720
> 28SEP10:16:44:00.67200
> 28SEP10:16:44:00.672000
> 28SEP10:16:44:00.6719999
> 28SEP2010:16:44:00.67200
>
> It seems to me that it concerns some bug with SAS 9.1.3.
>
> Regards - Jim.
> --
> Jim Groeneveld, Netherlands
> Statistician/SAS consultant
> http://jim.groeneveld.eu.tf
>
> My computer, my wife and I will attend PhUSE 2010 in Berlin.
>
>
>
> On Wed, 29 Sep 2010 19:26:32 -0400, Arthur Tabachneck <art297@NETSCAPE.NET
> >
> wrote:
>
> >Proc Me,
> >
> >Most definitely appreciated! Now I'd like to see some results from others
> >who, like me, are on some version of 9.1.3.
> >
> >Art
> >---------
> >On Wed, 29 Sep 2010 18:57:16 -0400, Proc Me <procme@CONCEPT-DELIVERY.COM>
> >wrote:
> >
> >>Art, Dan,
> >>
> >>Two "lower powered" systems, one my 32bit XP desktop and the other a
> >>remotely submitted job to a 32bit Win 2k3 R2 Ent Ed server. Both return
> >the
> >>results I would anticipate:
> >>
> >>32bit Win XP Pro, SAS 9.2 (TS2M0)
> >>
> >>1 data _null_;
> >>2 dt="28SEP10:16:44:00.672"dt;
> >>3 format dt 15.3;
> >>4 put dt datetime19.2;
> >>5 put dt datetime21.4;
> >>6 put dt datetime22.5;
> >>7 put dt datetime23.6;
> >>8 put dt datetime24.7;
> >>9 put dt datetime28.5;
> >>10 run;
> >>
> >>28SEP10:16:44:00.67
> >>28SEP10:16:44:00.6720
> >>28SEP10:16:44:00.67200
> >>28SEP10:16:44:00.672000
> >>28SEP10:16:44:00.6719999
> >>28SEP2010:16:44:00.67200
> >>
> >>32bit Win2k3 R3 Server Enterprise Edition, SAS 9.2 (TS2M2)
> >>
> >>28 data _null_;
> >>29 dt="28SEP10:16:44:00.672"dt;
> >>30 format dt 15.3;
> >>31 put dt datetime19.2;
> >>32 put dt datetime21.4;
> >>33 put dt datetime22.5;
> >>34 put dt datetime23.6;
> >>35 put dt datetime24.7;
> >>36 put dt datetime28.5;
> >>37 run;
> >>
> >>28SEP10:16:44:00.67
> >>28SEP10:16:44:00.6720
> >>28SEP10:16:44:00.67200
> >>28SEP10:16:44:00.672000
> >>28SEP10:16:44:00.6719999
> >>28SEP2010:16:44:00.67200
> >>
> >>I hope this helps,
> >>
> >>Proc Me
> -----------------------------------------
> Email messages cannot be guaranteed to be secure or error-free as
> transmitted information can be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses. The
> Centers for Medicare & Medicaid Services therefore does not accept
> liability for any error or omissions in the contents of this
> message, which arise as a result of email transmission.
>
> CONFIDENTIALITY NOTICE: This communication, including any
> attachments, may contain confidential information and is intended
> only for the individual or entity to which it is addressed. Any
> review, dissemination, or copying of this communication by anyone
> other than the intended recipient is strictly prohibited. If you
> are not the intended recipient, please contact the sender by reply
> email and delete and destroy all copies of the original message.
>
|