The yearcutoff option is pretty serious. By default version 6.12 would treat 00 as 1900, which is a textbook example of the Y2k problem.

Tim Vorce (248) 586-1999 tvorce@trilliumteam.com Trillium Teamologies SAS. It's not just an attitude

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of Robert Andrew Bowell Jr. Sent: Wednesday, June 30, 1999 3:01 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Y2K stuff

Hey, My understanding was that the only Y2K worries for SAS were the YEARCUTOFF= option. A user of mine had read the details of the Y2K class SAS offers, and seemed to feel differently. So what's the verdict here? What does one have to do besides inform people of the YEARCUTOFF= option in order to make their SAS files Y2K compliant? Our environment has SAS 6.09 (UNIX only), 6.10 (UNIX only), 6.11 (UNIX only) and 6.12 (UNIX and Windows), as well as a very select few users of 7.0 (Windows only). Some users may have files created under SAS 3-5. Is there a problem with Y2K compliance with such files? I would think not, but perhaps others are aware of something I'm not.

Y'obt., Rob Bowell ------------------------------------------------- Programmer/Analyst, RUCS User Services Group Hill Center, Room 209 Phone: 732-445-0481/Fax: 732-445-5539 -------------------------------------------------