Unfotunately, it isn't possible to use multiple WHERE filters in the same step as you're hoping to accomplish, regardless of what PROC you've selected. The nature of the WHERE statement is that it filters the data prior to processing your request, which means the data will need to be read an additional time to include a different subset of rows. That additional reading is triggered by running a new step.   That being said, it doesn't mean it's impossible to get the type of output you're looking for. It will probably just be a bit less sleek or require different techniques than you hoped. Here's a quick, basic version I wrote up that I think will give you roughly what you wanted for this sample data, but it's just what came to mind first (aka not optimized) and I'm sure many folks would happily take my version and improve upon it. Happy to see the results if they do and it helps you find a version you like better for your needs! 🙂   /* These first three proc tabulates are the same as your initial code with */ /* one minor tweak; these output the data to separate datasets so they can */ /* be manipulated and modified more easily. */ proc tabulate data=sashelp.class out=work.first; class sex age; table sex, age; where sex="M"; run; proc tabulate data=sashelp.class out=work.second; class sex age; var height; table sex, age; where sex = "M" and height>60; run; proc tabulate data=sashelp.class out=work.third; class sex age; var height; table sex, age; where sex = "M" and height>60 and name like "J%"; run; /* The following data step combines all previous results, and adds a */ /* "tab" column to identify which original proc tabulate the row is */ /* from. */ data work.combo; set work.first(in=a) work.second(in=b) work.third(in=c); if a then tab="a"; else if b then tab="b"; else if c then tab="c"; run; /* When proc tabulate outputs data, it flips it around to save more */ /* "vertically" instead of the way it prints "horizontally." The */ /* following proc transpose will flip things back around so that */ /* the style will more closely match the original proc transpose. */ proc transpose data=work.combo out=work.trans(drop=tab _name_); var N; by tab; id age; run; /* Modifications are done, so we'll print to show it off! */ proc print data=work.trans; run;   ... View more

Which operating system are you using at home? VirtualBox offers built in support for this functionality on Linux, Mac OS, and Solaris only.   If you're using Windows, I would recommend you look into a third-party guide for setting up something like VBoxVmService to perform such a function. ... View more

When working with macro variables and scoping, I like to visualize it like each variable within the macro program is a piece of paper that you're adding to a stack. We start off and put the mv (shoes) piece of paper onto the stack, which is just the one paper right now. We can see that paper and take it away or update it whenever we want. But when we move into the %product macro, we have to add a new piece of paper. This is the positional parameter mv. This is NOT the same mv from before; this is a local macro variable. It needs a new piece of paper. So now we have a piece of paper called mv (tents). After adding that paper, we see it's time to update mv to clothes. But it's hard to get to the original macro variable because that paper is UNDER the new piece of paper! Since we can't get to that variable without moving our papers around, we instead update our top sheet (the local mv) When we see %mend, that means all the local variables need to be removed. We take off and throw away the mv (clothes) paper. Now the only variable left is the original macro variable mv (shoes). That's what prints when we run the program.   Why is this different than the dog and cat example?   We start off easy again: a single piece of paper called a (cat). We go inside the macro %animal and we IMMEDIATELY see a reassignment to that macro variable a. Since it's already on the top of the stack, we're able to make changes to that paper without moving anything else around or creating a new, local version of a. We scratch out a (cat) and write a (dog). The macro is able to complete with only a single piece of paper running around, so the values change as you would expect, given their names.   Hope this helps if you're struggling with the visuals! ... View more

Are you using SAS University Edition, perhaps? I don't believe that PROC QLIM is one of the supported SAS/ETS procedures of that software.   Alternatively, if you're using a normal version of SAS Studio not requiring the virtual console; are you certain your license has SAS/ETS available? If you aren't sure, you can run the following code and check the log output to see what products are listed:   PROC SETINIT; RUN; ... View more

I don't believe what you're asking for is possible, using libname concatenation   What you might be able to do instead is create multiple libraries, one concatenating all your relevant inputs together and the rest referring to each component of the concatenation. From there, I found this pre-written macro program that you might be able to customize to calculate free space for each particular folder. ... View more

I get the feeling you may be confusing SAS ODS with SAP ODS. In SAP, this stands for Operational Data Store. But in SAS, this is the Output Delivery System. As far as I know (though I don't use ODS very often), output is it's primary intended use, maybe even the only use. Not input.   What pops into my head for input is that SAS can treat Excel Workbooks as a library. If you use a LIBNAME statement such as:   LIBNAME myExcel XLSX path="D:\text.xlsx";   From here, it's particularly easy to read all the data and turn it into whatever you'd like because every sheet from the original data is now accessed just like a data set in a library. To extend your example, if you have paper and maybe an electronic worksheet and you just wanted all the data concatenated, you could use:   DATA work.combined; SET myExcel.paper myExcel.electronic; RUN;   If there are header rows or you need to do some manipulation with the numbers it will take a bit of extra finagling, but once you've got the data you like, then you can start using ODS to send it back to Excel, etc. ... View more

It sounds like you're trying to do a transpose. Check out PROC TRANSPOSE here and see if that might be able to do what you want. ... View more

I'm not sure why the Excel destination does not allow you to do this properly, but it is definitely a problem with the Excel destination itself. I played around with various code for a while and couldn't figure out a way around it. Are you open to using other file types that may be readable via Excel even if they aren't native? If you change your output file extension to .xls and use the tagsets.excelxp destination, you can create the newlines as you wish. ... View more