topic Re: how to use the options label with a sas macro function in SAS Enterprise Guide

how to use the options label with a sas macro function

alepage — Tue, 25 Mar 2025 20:10:37 GMT

Hello,

I have tried this SAS code but I forgot to mentioned that it is inside of a macro function and the options label seems not working properly. How to solve that issue.

options label;
Data BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE1.&CO._AUTO_PRM&MOISC.&YEAR. ;
run;

/****** Bande2 for Property *****/
options label;
Data BANDE5.&CO._PROP_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE2.&CO._PROP_PRM&MOISC.&YEAR. ;
run;

/****** Bande3 for Enterprise *****/
options label;
data BANDE6.&CO._CNA_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE3.&CO._CNA_PRM&MOISC.&YEAR. ;
run;
proc compare base=bande1.&CO._AUTO_PRM&MOISC.&YEAR. compare=BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. 
listvar;
/*attrib _all_ label=' '; */
run;
proc compare base=bande2.&CO._prop_PRM&MOISC.&YEAR. compare=BANDE5.&CO._prop_PRM&MOISC.&YEAR. 
listvar; 
/*attrib _all_ label=' ';*/
run;
proc compare base=bande3.&CO._CNA_PRM&MOISC.&YEAR.  compare=BANDE6.&CO._CNA_PRM&MOISC.&YEAR.  
listvar; 
/*attrib _all_ label=' ';*/
run;
proc compare base=bande1.&CO._AUTO_PRM&MOISC.&YEAR. compare=BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. 
listvar;
/*attrib _all_ label=' '; */
run;
proc compare base=bande2.&CO._prop_PRM&MOISC.&YEAR. compare=BANDE5.&CO._prop_PRM&MOISC.&YEAR. 
listvar; 
/*attrib _all_ label=' ';*/
run;
proc compare base=bande3.&CO._CNA_PRM&MOISC.&YEAR.  compare=BANDE6.&CO._CNA_PRM&MOISC.&YEAR.  
listvar; 
/*attrib _all_ label=' ';*/
run;

Re: how to use the options label with a sas macro function

PaigeMiller — Tue, 25 Mar 2025 20:48:40 GMT

You haven't explained what is wrong with the code.

Re: how to use the options label with a sas macro function

SASKiwi — Tue, 25 Mar 2025 22:28:07 GMT

An OPTIONS LABEL statement works the same in a macro as outside. Try this test;

%macro test (option=);

options &option;

data cars;
  count = _n_;
  set sashelp.cars;
run;

proc contents data = cars  details;
run;

%mend test;

%test(option = nolabel);
%test(option = label);

If your macro behaves differently then you will need to post a complete example that demonstrates the problem.

Re: how to use the options label with a sas macro function

alepage — Wed, 26 Mar 2025 14:15:03 GMT

Hello,

When the macro function %premiumc is executed, it read a .dat file to create three sas datasets, one for auto, one for property and another one for enterprise. (refer to bande1, bande2, bande3).

Here's the various libname and macro variables:

libname  BANDE1 spde '/.../Temp/Alain/test/Classic/gc/auto';
libname  BANDE2 spde '/.../Temp/Alain/test/Classic/gc/habi';
libname  BANDE3 spde '/.../Temp/Alain/test/Classic/gc/entr';

libname  BANDE4 spde '/.../Temp/Alain/test/Classic/gc2/auto';
libname  BANDE5 spde '/.../Temp/Alain/test/Classic/gc2/habi';
libname  BANDE6 spde '/.../Temp/Alain/test/Classic/gc2/entr';

filename TX1   '/.../pa.pxp4xax.sep4tuac.mo1.dat' lrecl=2000 recfm=v;
%LET MOISC =fev;
%LET YEAR =2025;
%let co=gc;

Then we have the macro function

%macro premiumc;

...

%mend premiumc;

%premiumc;

Into that existing macro function, some SAS code at the end (but inside the macro function) the following SAS code:


/****** Bande1 for Auto *****/
options label;
Data BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE1.&CO._AUTO_PRM&MOISC.&YEAR. ;
run;
/****** Bande2 for Property *****/
options label;
Data BANDE5.&CO._PROP_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE2.&CO._PROP_PRM&MOISC.&YEAR. ;
run;
options label;
data BANDE6.&CO._CNA_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE3.&CO._CNA_PRM&MOISC.&YEAR. ;
run;
proc compare base=bande1.&CO._AUTO_PRM&MOISC.&YEAR. compare=BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. 
listvar;
/*attrib _all_ label=' '; */
run;
proc compare base=bande2.&CO._prop_PRM&MOISC.&YEAR. compare=BANDE5.&CO._prop_PRM&MOISC.&YEAR. 
listvar; 
/*attrib _all_ label=' ';*/
run;
proc compare base=bande3.&CO._CNA_PRM&MOISC.&YEAR.  compare=BANDE6.&CO._CNA_PRM&MOISC.&YEAR.  
listvar; 
/*attrib _all_ label=' ';*/
run;

So after reading the .dat file, three sas datasets are created respectively into bande1, bande2, and bande3.

Thereafter, I read those datasets and I had the variable ORGNL_SAS_DS_ROW_NBR into the three datasets but the updated datsets are saved in band4, bande5 and bande6 respectively.

After that, a proc compare is done comparing the dataset in bande1, bande2 and bande3 with those in bande4, bande5 and bande6.

The issue we have is with the label values. When we compare the values of bande1 and bande4 sas said that they are diffent which is not the case and the label value for bande5 and bande6 are black even if we use the options label (see the sas code options label;

data...

ORGNL_SAS_DS_ROW_NBR=_N_;

set...

run;

When we select just the following line of code and execute it , it works fine.
How to solve that issue?

/****** Bande1 for Auto *****/
options label;
Data BANDE4.&CO._AUTO_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE1.&CO._AUTO_PRM&MOISC.&YEAR. ;
run;

/****** Bande2 for Property *****/
options label;
Data BANDE5.&CO._PROP_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE2.&CO._PROP_PRM&MOISC.&YEAR. ;
run;

/****** Bande3 for Enterprise *****/
options label;
data BANDE6.&CO._CNA_PRM&MOISC.&YEAR. ;
ORGNL_SAS_DS_ROW_NBR=_N_;
set BANDE3.&CO._CNA_PRM&MOISC.&YEAR. ;
run;

proc compare base=bande1.&CO._AUTO_PRM&MOISC.&YEAR. compare=BANDE4.&CO._AUTO_PRM&MOISC.&YEAR.
listvar;
/*attrib _all_ label=' '; */
run;
proc compare base=bande2.&CO._prop_PRM&MOISC.&YEAR. compare=BANDE5.&CO._prop_PRM&MOISC.&YEAR.
listvar;
/*attrib _all_ label=' ';*/
run;
proc compare base=bande3.&CO._CNA_PRM&MOISC.&YEAR. compare=BANDE6.&CO._CNA_PRM&MOISC.&YEAR.
listvar;
/*attrib _all_ label=' ';*/
run;

Re: how to use the options label with a sas macro function

Tom — Wed, 26 Mar 2025 14:21:59 GMT

When you change a system option using the OPTION statement it stays that way until you run another OPTION statement to change it. It does not matter whether the option statement is part of your open code program or is generated by a macro you have run.