topic Re: the impact of putting rename function in different location within data step in SAS Programming

the impact of putting rename function in different location within data step

ForrestYao — Tue, 12 Dec 2023 02:23:46 GMT

Hi all,

The following questions confused me a lot, I would like to understand the following codes, specifically, how they impact the results when I put the rename function on the different locations within the data step.

first piece:

Data new_student1;

set student;

rename gender = sex;

if name = 'jack' then gender = 'm';

run;

second piece:

Data new_student2;

set student (rename = (gender = sex));

if name = 'jack' then sex = 'm';

run;

third piece:

Data new_student3 (rename = (gender = sex));

set student;

if name = 'jack' then gender = 'm';

run;

Can anyone explain in detail how the code runs in sequence and what the results for each step are?

Much appreciated!

Sam

Re: the impact of putting rename function in different location within data step

Tom — Tue, 12 Dec 2023 04:13:30 GMT

Why are you confused?

Can you tell us which statement is specifying the INPUT to the data step?

Can you tell us which statement is specify where the OUTPUT of the data step will be saved?

Once you can see that then for each step explain

1) What variables names will come into the data step.

2) What variable names will exist while the data step is running.

3) What variable names will be written to the output dataset.

Re: the impact of putting rename function in different location within data step

s_lassen — Tue, 12 Dec 2023 13:41:28 GMT

The first data step and the second do the same thing, but in different ways. When RENAME is used as a statement as in the first data step, the variable is renamed on the output dataset, but not in the statements in the data step. So, in data step 1, the gender variable is modified, and then renamed to "sex" on the output dataset. In the second data step, the gender variable is renamed when the data is read, so it is called "sex" in the data step, and in the output data.

RENAME used as a statement is non-executable, meaning that it does not matter where you put it in the code (unless you put it before the SET statement, in which case the RENAME statement will be the definition of the GENDER variable, meaning it will be numeric, and the code will generate an error).

In the third data step, the gender variable is renamed when the data is read, and then a new variable named "gender" is created. The new variable is only assigned a value when name='jack', and the sex variable (which was the original "gender" variable) is not modified.

Hope that answers your questions.

Re: the impact of putting rename function in different location within data step

ForrestYao — Wed, 13 Dec 2023 01:34:33 GMT

thanks, may i ask one more question, i guess the real confusing part for me is when the if statement becomes effective? For example, the first query, rename happens after new_student1 is created, and it will not change table student_score, but when the if statement will happen? will it happen before or afte r the rename statement? because in new_student1, the gender attribute has already been renamed to sex, then why the if statement still says gender = M? much appreciated your reply!

Re: the impact of putting rename function in different location within data step

ForrestYao — Wed, 13 Dec 2023 01:35:38 GMT

i meant student instead of student_score, just FYI

Re: the impact of putting rename function in different location within data step

Tom — Wed, 13 Dec 2023 03:28:46 GMT

The IF statement is a EXECUTABLE statement. Just like an assignment statement.

It executes for every iteration of the data step when the program flow gets to that part of the program. So in your simple data steps the IF statement will execute once for every observation read in by the SET statement.

The RENAME statement is NOT an EXECUTABLE statement. It just helps the compiler set up the data step. So it let's SAS know that when it is ready to setup the output dataset(s) that the name in the new dataset should be the new name, not the name that the variable was referenced by while the data step was executing.