Date: Fri, 6 Mar 1998 10:08:06 -0500
Reply-To: Victor Kamensky <kamensky@AECOM.YU.EDU>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Victor Kamensky <kamensky@AECOM.YU.EDU>
Subject: Re: Y2000 problem ?
Content-Type: text/plain; charset="us-ascii"
> If you need to keep the automatic macro variable sysdate, you have to
> write some code:
> rundate = "&sysdate"d ;
I am doing exactly this!
But recently I loaded and installed
experimental SASXDTU (from www.sas.com)
prepared by Rick Langston to check for
2-digit year. And the statement above: rundate = "&sysdate"d ;
produces the following messages:
WARNING: TWO DIGIT YEAR CHECK (zmdy): MONTH=3 DAY=6 YEAR=98
- called from <unknown>
To avoid these messages one can use the following code(tested):
length mvar $ 30;
call symput('rundate', compress(mvar));
Or a %sysfunc substitute can be written.
But are these solutions really good?
What is SI going to do about &sysdate?
Albert Einstein College of Medicine
> So we all need to stay anxious about year 2000 issues all over the
> Nothing is completely, 100% year 2000 compliant...