there won't be any statements missing: no longer available.
my memories are of having problems w/UPCASE/lowcase
of variable names in output data sets created by sas procedures
you will have to sanitize your comments:
no special characters, like ampersand or percent and s- or d-quotes
/* don't have this */
* %dothis ;
%* A&B nor this;
Ron Fehd the macro maven CDC Atlanta GA USA RJF2 at cdc dot gov
> -----Original Message-----
> From: Shanks N [mailto:email@example.com]
> Sent: Wednesday, December 16, 2009 10:43 AM
> To: Fehd, Ronald J. (CDC/CCHIS/NCPHI)
> Subject: Re: FW: Summary of the differences of Base SAS 9.1.3
> and SAS 9.2
> Thanks Ron,
> At least with respect to Data, there is PROC migrate and if that does
> not work XPORT, COPY. What about the SAS code? Is there a chance for
> the program to go down in flames or whether the compiler will warn of
> deprecated features and such?
> This is all I have
> >> -----Original Message-----
> >> From: Michael Raithel
> >> Sent: Monday, October 19, 2009 7:59 PM
> >> Subject: RE: Summary of the differences of Base SAS 9.1.3
> and SAS 9.2
> >> Dear SAS-L-ers,
> >> Jerry posted the following:
> >> > Anyone have the release notes (or a summary of it?) On what
> >> the major
> >> > differences to expect from Base SAS 9.1.3 and 9.2?
> >> >
> >> > From what I heard, there aren't that many differences
> besides a new
> >> > installer that helps with upgrades.
> >> Jerry, yea; I've got them right here:
> >> http://support.sas.com/documentation/whatsnew/index.html
> >> With a simple click of the old mouse, you can check out the
> >> differences between (8.2) and (9.0, 9.1, 9.1.2, 9.1.3) or
> >> between the aforementioned and SAS 9.2. I've gotta warn you
> >> there is more verbiage in there than in ten of my posts
> >> concatenated together; so wipe off your glasses, pour
> >> yourself a big cup of coffee, and settle into your chair for
> >> a nice long read:)
> >> Jerry, best of luck in all of your SAS endeavors!
> >> I hope that this suggestion proves helpful now, and in the future!
> >> Of course, all of these opinions and insights are my own, and
> >> do not reflect those of my organization or my associates. All
> >> SAS code and/or methodologies specified in this posting are
> >> for illustrative purposes only and no warranty is stated or
> >> implied as to their accuracy or applicability. People
> >> deciding to use information in this posting do so at their
> own risk.
> >> Michael A. Raithel