topic Multiple conditions statement in SAS Programming

Multiple conditions statement

VRD — Thu, 24 Apr 2014 13:08:33 GMT

I have 3 variables

s.no cond1 cond2 cond3

1 4 8 min

2 3 0

3 -1 8

4 . 1 min

5 0 -2

i want to have multiple conditions.

if cond1 and cond2 is less than 0 and cond3 is missing then newvar=yes

if cond1 and cond2 is gt 0 and cond3 is missing then newvar=no

if cond 1 or cond2 is missing then newvar=missing.

Re: Multiple conditions statement

stat_sas — Thu, 24 Apr 2014 13:32:08 GMT

Here is my try

data have;

infile datalines missover;

input s_no cond1 cond2 cond3 $;

datalines;

1 4 8 min

2 3 0

3 -1 8

4 . 1 min

5 0 -2

;

data want;

length newvar $ 5;

set have;

if cond1<0 and cond2<0 and cond3=' ' then newvar='yes';

else if cond1>0 and cond2>0 and cond3=' ' then newvar='no';

else if cond1=. and cond2=. then newvar=' ';

run;

Re: Multiple conditions statement

ballardw — Thu, 24 Apr 2014 16:26:54 GMT

Missing is always less than 0 so you probably want:

if .< cond1 < 0 and . < cond2< 0 for the first comparison

and

else if cond1 = . or cond2=. then ...

What do you want to do if one of cond1 is <0 and the other is > 0?

Or exactly = 0 since your data has 2 examples of that. You may want LE or GE instead of LT or GT in one or more of your cases.

Re: Multiple conditions statement

SKK — Fri, 25 Apr 2014 04:14:20 GMT

Hi.. Here's something with Proc SQl.. I manipulated your input data a little bit.. to get expected output..,

data have;
infile datalines missover;
input sno cond1 cond2 cond3 $;
datalines;
1              4          8
2              .          .
3              -1          8
4              .          1               min
5             -1           -2
;
run;

PROC SQL;
CREATE TABLE WANT AS
SELECT *,
CASE WHEN COND1=. AND COND2=. THEN "MISSING"
WHEN COND1 LT 0 AND COND2 LT 0 AND COND3 =" " THEN "YES"
WHEN COND1 GT 0 AND COND2 GT 0 AND COND3= " " THEN "NO"
ELSE "UNKNOWN" END AS NEWVAR LENGTH=10
FROM HAVE;
QUIT;

Re: Multiple conditions statement

Kurt_Bremser — Fri, 25 Apr 2014 05:25:59 GMT

What value do you want to have when one of (cond1,cond2) is positive and the other negative or when one of them is zero?

Re: Multiple conditions statement

VRD — Fri, 25 Apr 2014 07:23:05 GMT

i want like this.

if cond1 and cond2 is not missing and less than or equal to 0 and cond3 is missing than as yes.

if cond1 and cond2 is not missing and gt 0 than no

if cond1 or cond 2 is missing than as missing.

Re: Multiple conditions statement

SKK — Fri, 25 Apr 2014 07:57:23 GMT

Try this , it works fine for ur condition and i have also added another value "Unknown" for data which does not meet any of the conditions

PROC SQL;

CREATE TABLE WANT AS

SELECT *,

CASE WHEN COND1=. AND COND2=. THEN "MISSING"

WHEN COND1 LE 0 AND COND2 LE 0 AND COND3 =" " THEN "YES"

WHEN COND1 GT 0 AND COND2 GT 0 AND COND3= " " THEN "NO"

/*ELSE "UNKNOWN"*/ END AS NEWVAR LENGTH=10

FROM HAVE;

QUIT;

Re: Multiple conditions statement

VRD — Fri, 25 Apr 2014 08:14:35 GMT

No, This case will not work as . will be less than 0 and it will consider as yes even cond2 ios missing which should not be the case

Re: Multiple conditions statement

SKK — Fri, 25 Apr 2014 08:26:05 GMT

Try now

PROC SQL;

CREATE TABLE WANT AS

SELECT *,

CASE WHEN COND1=. OR COND2=. THEN "MISSING"

WHEN COND1 LE 0 AND COND2 LE 0 AND COND3 =" " THEN "YES"

WHEN COND1 GT 0 AND COND2 GT 0 AND COND3= " " THEN "NO"

/*ELSE "UNKNOWN"*/ END AS NEWVAR LENGTH=10

FROM HAVE;

QUIT;

Message was edited by: SK K

Re: Multiple conditions statement

Kurt_Bremser — Fri, 25 Apr 2014 09:21:33 GMT

That still does not cover line 3 where cond1 is less than 0 and cond2 is greater than 0.

Re: Multiple conditions statement

mfab — Fri, 25 Apr 2014 13:15:16 GMT

Well, I guess line 3 falls under the 'undefined' or 'unknown'. This just needs to be uncommented in the SQL-Statement above.

The original post did not specify what to do with such data. 🙂

Re: Multiple conditions statement

Kurt_Bremser — Fri, 25 Apr 2014 13:38:53 GMT

Out of experience, I DO NOT LIKE possible conditions that are not covered in the code, they tend to come back and bite one in the ass

So setting newvar explicitly to "unknown" is good practice. Just relying on empty (missing) values because they happen on their own may lead to unnecessary expensive debugging later on.