run PROC OPTIONS and look for SASAUTOS in the log. It may give you a hint where to search the macro.   Shmuel   ... View more

every library will gets its own proc datasets step;   first.library means the first apearance of each library;   Shmuel ... View more

The outcome of "CALL EXECUTE" and the generated program are the same; The benefit of generated program is the ability to stop and control before real execution.   Shmuel ... View more

I got your point. In this case I shall not use macro language, though it is possible but mutch more compicated. Instead I shall show here a method that I have used a lot of times.   Let say your file contains next variables:   -  LIB stands for Library   -  DSN stand for dataset Name   -  var1 contains attribute 1  (TYPE)   -  var2 contains attribute 2  (LABEL)   -  and so on, as mutch as you need   Let's call your file ARGS (arguments); By the method, I write program A and run it to generate program B, using the fact that each program is a text file. I can look at the generated program B, make changes to program A if needed and rerun it until satisfaction.   Then I run program B to do the wanted job.   Here is a schematic prgram A:   proc sort data=ARGS; by LIB  DSN; run;     /* needed for proc datasets */ filename generated '... any path and name ...'; data _NULL_;     set ARGS end=eof;       by LIB  DSN;     file generated;       length pgm_line $80;  /* generated program line. you may change length according to need */      if first.LIB then do;        pgm_line = 'Proc Datasets lib=' || LIB || ' nolist; ';          put pgm_line;   end;      if first.DSN then do;        pgm_line = 'Modify ' || DSN || ';' ;        put pgm_line;    end;        pgm_line = 'TYPE=' || var1 || ';' ;    put pgm_line;    pgm_line = 'LABEL=' || var2 || ';' ;    put pgm_line;      *** continue as much as you need ***;        if last.LIB or eof then do;        pgm_line = 'Quit; Run;' ;        put pgm_line;   end; RUN;   /*  end od program A */   Now run this program and look at the generated output. Addapt it to your needs and rerun. When satisfied, do %INCLUDE generated; and run it.   I hope I realy got your point; Shmuel ... View more

I have the feeling that we use same word MODIFY but understand it differently.   Proc Datasets ... Modify ... enables modifying of variable attributes like: rename, variable label, format (how to display it) etc but not their value in the data set observations.   I have no idea what you mean by AREA_X, UNIT_Z - are those variable values that you want to replace in all observations of the data set ?   Please run the next code and see what RETAIN do:   data test; retain x 'Constant';  /* no equal sign is needed */ do i=1 to 5; output; end; run;   Shmuel ... View more

There is no variable named "Total" in sashelp.shoes.   I should change in your program:   var sales; output out=Regional_sales SUM(sales)=total_regional_sales;   Shmuel ... View more

I don't understand your situation. What do you mean by "...put the classification in an variable in a data set..." ? What do you mean by "... loop it into a dynamic macro variable which rund through the data set" ?   I may help you if you give an example of your inputs and what you want to be on the outputs.   Shmuel ... View more

hello, I have attached a SAS program - an example. First two steps were to create test data, the rest is a code to add label and change format of variables. Run the 1st two steps and look at the data sets: the date is not formated and the variable i  - should be labeled as "KEY". Now run the rest of the pragram (or the whole program as one unit);   Look at the log: using "options mprint" in the program enables demostrate how the macro is developed and embeded; Look again at the datasests EXPML1 and EXMPL2; change to view labels instead of columns. You will see the outcome of the MODIFY statements;   With hope it is more clear now.   Shmuel ... View more

You can use SAS macro to shorten your code:   %macro shr;    /* you may add as much common lines as need */ xattr add DS Type="Area_X"; xattr add DS Contact="Unit_U"; %mend;   proc datasets lib=XXX nolist; modify table_x;  %shr; modify table_y; %shr; quit;   I'm not sure is it possible to modify more than one file at a time. Anyway ther is no need to copy shared lines. It can be done easily by macro; Please check it; ... View more

You can repair your data-set  by overriding 1st observation values. Pay attention to variables type:  CHAR or NUM to write the correct values as correct litterals;     data new;  set old;    if _N_ = 1 then do;     Salesman_name_dept = "Michael Perry A001 Manufacturing";     Sale_date =  '10Jan09'd;     Reorder    = 50;     Event = 10;     BuySell = 45.45;     Amount = 5000.75;  end; run;     ... View more