Date:         Tue, 16 Jun 2009 15:51:23 -0400
Reply-To:     Fatos Simsek <fatosus@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Fatos Simsek <fatosus@GMAIL.COM>
Subject:      Re: .sd2 extension
Comments: To: Ya Huang <ya.huang@amylin.com>
In-Reply-To:  <200906161826.n5GGjAZj031866@malibu.cc.uga.edu>
Content-Type: text/plain; charset=ISO-8859-1

too bad! it is not working.. any other ideas?
thank  you so much
f

On Tue, Jun 16, 2009 at 3:26 PM, Ya Huang <ya.huang@amylin.com> wrote:

> *.sd2 is pc sas v6 version, you need to add v6 option in the libname
> statement, so that SAS can recognize it:
>
> libname birth v6 "c:\pr\bdata";
>
> On Tue, 16 Jun 2009 14:32:53 -0400, Fatos Simsek <fatosus@GMAIL.COM>
> wrote:
>
> >My problem is with the sas data set extensions. The data sets I have were
> >sas data sets until the 9.1.3 version upgrade was performed. I am guessing
> >that after the upgrade datasets have received .sd2 extension???  State99
> >data below, for example, was a sas data set but now it is state99.sd2.
>  How
> >can I resolve a problem such as this:
> >
> >977  libname birth 'c:\pr\bdata';
> >
> >NOTE: Libname BIRTH refers to the same physical library as BDATA.
> >
> >NOTE: Libref BIRTH was successfully assigned as follows:
> >
> >      Engine:        V9
> >
> >      Physical Name: C:\PR\BData
> >
> >978
> >
> >979  options fmtsearch=(pr2.format99);
> >
> >980
> >
> >981  data pr99;
> >
> >982  set  pr99.state99;
> >
> >ERROR: File PR99.state99.DATA is not a SAS data set.
> >
> >.
> >
> >.
> >
> >.
> >
> >.
> >
> >NOTE: The SAS System stopped processing this step because of errors.
> >WARNING: The data set WORK.PR99 may be incomplete.  When this step was
> >stopped there were 0 observations and 2 variables.
>



--
               \\  - -  //
             (  @ @  )
+------oOOo-(_)-oOOo----------+---------------------------------+

"Be who you are and say how you feel.
Because those who mind don't matter,
and those who matter don't mind."
--Dr. Seuss