Date: Thu, 24 Dec 1998 10:34:42 -0500
Reply-To: Jules Bosch <jxb@BELLATLANTIC.NET>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Jules Bosch <jxb@BELLATLANTIC.NET>
Organization: Bosch Systems Inc.
Subject: Re: OBS=, What happened here?
Content-Type: text/plain; charset=us-ascii
One of the issues to beware of when using the OBS=N option is that it
remains in effect during the current SAS session until it is reset via
OPTIONS OBS=MAX or OPTIONS OBS=<some other #>.
A while ago I was testing code and had limited the obs to be processed
via OPTIONS OBS=30. Later, in the same same SAS session, I opened up a
permanent data set to edit it. The code that facilitates editing the
data set uses a PROC FSEDIT statement and concludes with a PROC SORT
statement. At the start the data set contained 500+ obs; when I
finished it had only 30 obs! I was momentarily puzzled until it dawned
on me that OBS=30 was still in effect. While I had a back up copy of
the data set, I still lost all the work I had just completed.
Now, I include the OBS=MAX option at the start of all my code streams
just to be safe.