About Wesley

Wesley · ‎07-17-2014

Here is a fairly simple example of how to re-assign a value to the global variable defined outside the macro. As you can see VAR3 has been changed to the new value. So VAR3 can be viewed as the "return" value. WRT documenting macro variables, my experience has been that they are not documented very well or simply not at all. I am guilty of that as well. That's why I usually run code with: OPTIONS SYMBOLGEN MACROGEN; The example you provide later is probably some code that was written for one purpose and then modified later on and as such suffers from code bloat. Extraneous code is left in because it doesn't hurt anything. It all comes down to style too. Some people like to indent their code with a few spaces and other use a tab. As you can see my style is "flatearther". %let var1 = 13; %let var2 = 6; %let var3 = 0; %MACRO callmacro(x1, x2, x3); %let &x1 = %eval(&&&x1 - &&&x2); %MEND; %put &var3; %callmacro(var1, var2, var3); %put &var3;

Wesley · ‎04-04-2013

Okay, I just re-read your original question. The following will give you a data set in work that has only as many records as there are distinct values of sex. proc sort data=sashelp.class(keep=sex) out=class nodupkey; by sex; run; The following will create a macro variable for each unique value of sex. If the only values are Male and Female then: ID1 = Female ID2 = Male n = 2 Since this was sorted by sex (default is ascending) and F comes before M. data _null_; set class end=last ; call symputx(cats('id',_n_),sex); if last then call symputx('n',_n_); run;

Wesley · ‎04-04-2013

Well, there is a lot of information in this. ID1 has the value for the first observation (assuming you don't re-order the data set). ID127 has the value for the 127th observation. "n" tells us how many macro variables were created. If you want to access all the variables created then you'll need this number. Yes, this will reveal the values of all the macro variables you just created. Typically, I'll group things together so I can process things differently. I wouldn't use the method you're asking about. I assume this is just an example of how to create many different macro variables at once. I can't really see how to use that. I can always do the following: In the end you'll have as many different data sets as you have different sexes. All the sets will combine to recreate the original data set. /* the loop won't run in open code */ PROC SQL; DROP TABLE sex_count; CREATE TABLE sex_count as select distinct sex from class ; quit; %let number_of_sexes = &sqlobs; %do i = 1 %to &number_of_sexes; DATA _NULL_; x=&i; SET sex_count point=x; CALL SYMPUT('CDE_SEX', sex); stop; run; %put &CDE_SEX; PROC SQL; DROP TABLE _.&CDE_SEX; CREATE TABLE _.&CDE_SEX as select * from class where SEX = "&CDE_SEX" ; quit; %end; Another method to use is: PROC SQL noprint; SELECT sex into :id1 - :id&n from class ; quit; But you'll need to define "n" ahead of time. Maybe I put too much in here.

Wesley · ‎04-04-2013

Knowing how many macro variables are created will allow you to use a loop such as: /*inside a macro of course*/ %do i = 1 %to &n; %put id&i = &&id&i; %end; Then you'll be able to see all the values that got assigned to the list of macro variables you created. There are many other nice things you can do too.

Wesley · ‎04-04-2013

Don't forget the last macro variable that's being created. That would be "n". The number of observations is being stored there. Wes

Wesley · ‎12-09-2012

Hi, The next line in the About SAS 9 window is "SAS 9.3 TS 1M0" next line "X64_7PRO platform". As I mentioned in my reply to Paul, (he was right) SAS/ACCESS Interface to Oracle was licensed but not installed. It is now installed and I'm getting a new error. Which I won't repost here but it is pasted in my reply to Paul. New job, I was on travel Wed, Thurs, Fri. So, are you from New Zealand? I see the Kiwi in your handle. Thanks, Wes

Wesley · ‎12-09-2012

Thanks for the responses. After some some more discussion here at work. I was informed that: Yes, SAS/ACCESS was licensed but not installed on my computer (?) Okay, so now it's installed as per our SAS administrator. So, you've seen this before? I am in the local admin group for my PC. I'm getting a different error now (progress). ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. ERROR: Image SASORA found but not loadable.. Please make sure Oracle environment is set correctly. Look in the install/Config doc for additional info for your platform. Other possible reasons - incomplete Oracle client install, 32/64-bit mismatch between Oracle client & SAS, incorrect Oracle client version(Oracle client must match the version picked during post-install process), incompatible sasora for your OS or its attribs don't permit SAS to load it. ERROR: Error in the LIBNAME statement. I was on travel Wed, Thurs, Fri. I came in today (Sunday) to see what I will have to deal with on Monday. I search for Oracle client 64 bit and get some choices. As for my version of SAS, when I bring up the "Help->About SAS 9" it says "SAS 9.3 TS Level 1M0" next line "X64_7PRO platform" then it goes on about the OS and Hardware info. Thanks, Wes

Wesley · ‎12-04-2012

Hi, I've got a HP Compaq with a core I5 running Windows 7 Professional Service Pack 1. SAS 9.3 TS Level 1M0 has just been installed on it. I've run PROC SETINIT and it shows that SAS/ACCESS Interface to Oracle is licensed with an expiration date of 31DEC2012. Problem, when I execute the libname statement it tells me that the Oracle engine cannot be found. Is this referring to the Oracle client? Because that is installed in: C:\oracle\product\10.2.0\client_1 I'm not sure just what exactly is not being found or how to proceed to get around this. Thanks, Wesley Okay, I thought I would provide an update. SAS/ACCESS Interface for Oracle was not installed. Once that was installed I got the 32 bit/64 bit mismatch error. I looked for the Oracle Client. All I kept finding was the Instant Client. That's not what I needed. I finally found that it is referred to as OCI (Oracle Client Interface). It's located under the database server download (currently Oracle DataBase 11g release 2). You have to select the "see all" option for the version of the client you are looking for (Microsoft Windows (x64) in my case). So the 64 bit client version 11.2.0 is working fine for me. Read the install directions. You should only need to install the "client" and "runtime" I'm not the SAS administrator. I am the user. The administrator installed SAS and the modules I needed but refused to help beyond that, very frustrating. So it was up to me to trouble shoot the problem and fix it with no assistance from the SAS administrator. Did I ask for help? Yes. /end rant I would like to thank SASKiwi and Paul Homes for their help. Their responses helped direct my search and I didn't know that SAS would show the product was licensed but would not tell you if it was installed. Thanks, I hope my update will help some one in the future. Wes

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: sharing variables between macros

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: The ORACLE engine cannot be found.

Re: The ORACLE engine cannot be found.

The ORACLE engine cannot be found.

Re: The ORACLE engine cannot be found.

Re: sharing variables between macros

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: Understanding Call Symput!

Re: The ORACLE engine cannot be found.

Re: The ORACLE engine cannot be found.

The ORACLE engine cannot be found.