Did you know that there is an option/data step option that causes notes to
be treated as errors?
Datanull suggested the option to someone on the SAS Forum's discussions,
yesterday, as a way to get SAS to not accept a data step with a
first.whatever statement, but no by statement.
The solution: note2err
The undocumented DSOPTIONS may be useful.
if first.name then;
or (from Peter Crawford after crediting DN)
data your.data/note2err ;
On Thu, 2 Nov 2006 13:17:55 -0500, Michael Raithel
>This is it! This is _YOUR_ chance to help make SAS-L history! You can
>do so by joining me in making this the longest thread that has ever
>existed in the storied history of this happy medium that we call:
>SAS-L. In doing so, you will not only help to make SAS-L history, you
>will also be an integral part of it!
>All that you have to do is contribute a single SAS tip to this thread.
>It doesn't necessarily have to be something profound; just solid and
>This opportunity is good for prolific posters, for occasional posters,
>for once-in-a-blue-moon posters, and especially for lurkers who have
>never posted before. Everybody on this list knows _SOMETHING_ about
>SAS. So, pick your best tip and post it--even if you are sure that
>others already know it. It could be that somebody doesn't know it, or
>that you refresh somebody's memory.
>So, here is how this will work. You simply write: "Did you know that:
>" and follow it up with your brief SAS tip. It couldn't be any easier,
>Okay, so I'll get the ball rolling. Here goes:
>Did you know that: you can increase the page size of SAS indexes when
>they are first created by using the IBUFSIZE option? The default
>IBUFSIZE is 4096 bytes. You can change that setting by specifying
>IBUFSIZE=xxxxx. The author of a recent book on SAS indexes recommends
>setting IBUFSIZE=32767 (the maximum) on all SAS platforms except for
>z/OS, where he recommends setting it to 27648. (However, he presents
>the caution that this has not been rigorously tested on SAS data sets of
>varying sizes on _ALL_ of the operating systems that SAS is run on. So,
>your mileage may vary).
>Hey, that was easy. Now, it is your turn!
>If you need more incentive to participate, then consider these inspiring
>From this day to the ending of the world,
>But we in it shall be remember'd;
>We few, we happy few, we band of brothers (and sisters);
>For he (or she) to-day that posts with me Shall be my brother (or
>I'll bet that did it. Okay, now get posting!
>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
>"The man who wrote the book on performance"
>Author: Tuning SAS Applications in the MVS Environment
>Author: Tuning SAS Applications in the OS/390 and z/OS Environments,
>Author: The Complete Guide to SAS Indexes
>Be great in act, as you have been in thought. - William Shakespeare