topic Re: IF THEN command in ODS and Base Reporting

IF THEN command

Edwinl — Sun, 04 Aug 2013 00:53:47 GMT

Not sure what but anytime I types the following command it highlight in red

if weight=999 then weight=.;

run;

if weight=999 then weight=.; and hit run

I tired %if weight=999 %then weight=.

Any help please

Re: IF THEN command

Patrick — Sun, 04 Aug 2013 01:06:00 GMT

Nothing wrong with the statement as such.

Does below code work for you?

data _null_;

set sashelp.class;

if weight=999 then weight=.;

run;

There might be something wrong in your code before this statement. That's why you would need to post the full data step - or the procedure code if this is Proc Report.

And: Which client is this? EG? And which version?

Re: IF THEN command

Cynthia_sas — Sun, 04 Aug 2013 17:59:25 GMT

And, some procedures have a WEIGHT option or WEIGHT statement. So sometimes, the syntax checker will flag those as red, but the code will execute correctly. Without seeing ALL of your code, it is hard to speculate.

You should not confuse macro syntax %IF with data step "regular" IF.

cynthia

Re: IF THEN command

Edwinl — Sat, 10 Aug 2013 02:49:20 GMT

proc data=DMC_data.cholesterol;

var weight;

run;

The MEANS Procedure

N means Std dev minimum maximum

200

172.3750000

64.5029264

109.0000000

999.0000000

then I did

if weight =999 then weight=.;

and run the above proc procedure and still 999 was not replaces and if was highlighted in red.

I then tried the suggested syntax

data _null_;

set sashelp.class;

if weight=999 then weight=.;

followed by the above proc syntax and still 999 wasn't replaced.

run;

proc data=DMC_data.cholesterol;

var weight;

if weight=999 then weight=.;

run;

Re: IF THEN command

Patrick — Sat, 10 Aug 2013 03:31:05 GMT

You need to invest some time in skilling up and understand the SAS concept of a Data Step and a Procedure.

Also consider using the EG wizards as this will support you in creating valid SAS code.

To give you a start below a simple example how your code could look like:

data test;
set DMC_data.cholesterol;
if weight=999 then weight=.;
run;

proc means data=test;
var weight;
run;

Re: IF THEN command

Tom — Sat, 10 Aug 2013 15:43:35 GMT

2) A) Cannot work as you cannot use an IF statement without some context to tell what to operate on.

B) Worked fine, but because you told it to throw away the output of the data step (data _null_;) it will have no effect other than to test the syntax of your IF statement

3) You cannot use an IF statement in a PROC. You could use a WHERE statement to eliminate the WEIGHT=999 records from the data. (where weight ne 999;)

You probably need to add a step some where to recode your special missing values from valid numbers like 999 into SAS missing or special missing values. I would recommend doing this in the first step that reads in your data from the source (if you cannot modify it in the source). Perhaps you are used to using SPSS which has support for indicating that normal values are to be treated as missing. SPSS also has an implied data step for every analysis procedure that support using things like IF statements and other code that can transform the data before it is passed to the analysis algorithm.

Re: IF THEN command

jakarman — Sun, 11 Aug 2013 06:36:48 GMT

Tom
You are right to aim at some basics. It are the concepts to be reviewed: SAS 9.3 Programmer's Bookshelf

Some nasty things:

1/ Missings
For statisticians it it quite common and makes sense to have many of them with different meanings.

- The SQL concept is failing in this part, just having one value "missing".

- SAS SPSS Stata (and others) are solving that it in different ways but supporting that.

SAS has the option to work with many types: SAS(R) 9.3 Statements: Reference (missing).

- The 9 habit as used in surveys is something going back to the hollerith approach, just having the numbers 0-9 as options.

That time has passed but habits are pertinacious. At the data-cleansing step this should solved, adjusted

an old proceedng http://www.nesug.org/proceedings/nesug01/ps/ps8009.pdf

And (stata) Stata FAQ: How can I recode missing values into different categories?

2/ Formats

Nothing is what is what is seems to be. The numeric (floating) technical handling is rather basic as some quirks can pop-up.

The rounding and difference with integers is a pitfall. Dates Times and datetimes are challenging. Unicode for the next frontier.

The concept of formats is rather unique with SAS. It is the only one environment/language I have seen where this is a segregated part of the data and can be seperately maintained. This offers quite smart and simple approaches not well known. Base SAS(R) 9.3 Procedures Guide, Second Edition (proc format). You could use MLF (Multi Labe Format) own proceduers (FCMP)

The switch in thinking: No need to adjust data generate additonal datasets, just apply different formats at analyzing.

Note:

Base SAS(R) 9.3 Procedures Guide, Second Edition (Proc report) This procedure has a compute block (it is exceptional)