Date: Thu, 30 Dec 1999 09:48:58 +0100
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE>
Subject: Re: datetime16 informat on sashelp.vtable ver6.12 ts60
in V6.12 / Windows I see only DATETIME. However, that should be no problem. Such
things could be a problem, if you enter data in a dataset and use such a
informat for your input mask. In the SASHELP - views you cannot enter anything.
For the formatting of any output it could be a problem, because someone could
think, your datasets are 100 years old. For that you can superseed the format by
your own. Important is, that the internal values are ok and that seems to be ok!
Have a nice start into 2000!
"Stetz, Cynthia (PCM - NJ)" <CStetz@NA2.US.ML.COM> on 29.12.99 19:01:01
Bitte antworten an "Stetz, Cynthia (PCM - NJ)" <CStetz@NA2.US.ML.COM>
Kopie: (Blindkopie: DeTeCSM HellriegelG/D/ExternalStaff/WLB)
Thema: datetime16 informat on sashelp.vtable ver6.12 ts60
Doing some housekeeping, and noticed that in the sashelp.vtable (one of
those infamous dictionary tables we've all come to know and love!) the date
fields for created and modified dates use an informat and format of
datetime16, which only allows for a 2 digit year. I am running SAS version
6.12, ts060 on Solaris UNIX 2.6, which I was under the impression was fully
Y2K compliant. Am I off base here, or won't this informat cause the vtable
to have bad dates asof Jan 1, 2000, if my yearcutoff is still set to 1900?
I fully plan to set it to 1920, before any of my users can log on and use
SAS, but isn't this a problem waiting to bite us?
Couldn't find anything on this in the notes, so I thought I'd throw it out
there to you guys.
Mit freundlichen Grüßen
Gerhard Hellriegel, DeTeCSM
D - 40217 Duesseldorf
Tel.: +49211 826 6173
Fax: +49211 826 5393