Hi:   The SURVEYREG example 120.4 is the one I used https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_surveyreg_examples04.htm and I got a bubble plot as shown in the documentation. Cynthia ... View more

Hi: The PROC SURVEYREG documentation describes how you use can use ODS GRAPHICS with this procedure: https://go.documentation.sas.com/doc/en/statcdc/14.2/statug/statug_surveyreg_details54.htm As shown in the documentation, using various statements will cause PROC SURVEYREG to automatically produce graphics. I don't see the PLOTS= option in your code so I wonder whether you might need a PLOTS= option. When I run the example from the doc using the FARMS data (which has both a STRATA and a WEIGHT statement, the default plot that I get is a bubble plot without using the PLOTS= option. This might be a question that is better worked with Tech Support so they can look at your data and your code and help you figure out the correct SURVEYREG syntax for what you want to do.. Cynthia ... View more

Hi, Kurt, This student was correct, the PG1 library, expects the full path like this: libname pg1 '/home/<userID>/EPG1V2/data'; So if they end the path with just EPG1V2, they will receive errors as shown in the OP's screen shot. Cynthia ... View more

Hi: To help you understand about macro variables and macro programs, here's an "oldie but goodie" paper on Macro Basics that may help you. https://support.sas.com/resources/papers/proceedings13/120-2013.pdf Cynthia ... View more

Hi:   Consider this code. SASHELP.CLASS has 19 rows with ages spanning from 11 to 16. In this code, I am outputting only the rows that meet the condition. However, my output is INSIDE the IF/THEN DO/END block because I want to do 2 things when the condition is met: 1) create the variable THISFIELD when the condition is true and 2) output the entire observation to the output data set when the condition is true.     Compare that code to this code where the output is being used for every row:   In this example, you can see that all 19 observations were written to the output dataset in this case. However, only the rows that met the IF condition have a value for the THISFIELD variable. The rest of the rows have a blank for the THISFIELD variable.   The difference is that the first program is executing 2 statements when the condition is met. The second program is only executing the assignment statement that created THISFIELD when the condition is met. For the second program, the OUTPUT statement is operating on EVERY row.   Both types of output are under your control based on how you code your conditional logic. A WHERE statement would also work for my example:   A WHERE works for my example because the variables used in the WHERE already exist in the input data set. So in this case, the only observations that are passed to the program are the observations that meet the WHERE condition. So I know that these rows are the ones that should be output and should have THISFIELD created. Cynthia ... View more

Hi:   CALL SYMPUTX is used to insert Macro variables into a macro variable symbol table because the values stored in the macro variables can be  based on information from reading the SAS dataset -- as in this case where we want to know the starting and stopping obs number for the last 10 observations in the input data. In the first example, I create the CURRENTOBS variable by capturing the _N_ value and then for PROC PRINT, I hard-coded the firstobs= and obs= values in the program. (keep in mind that if the data are sorted differently, not in alpha order, then the CURRENTOBS value for each row would be for a different name.)     In the second program, I also create CURRENTOBS in the DATA step program. Then, using the END= option allows me to use conditional logic when SAS is handling the last observation in the input data set. In this case, on the last row, I now know the number of obs in the data file and I just need to subtract to get the value for FIRSTOBS. My helper variables are created using CALL SYMPUTX and since I stored the helper macro variables in the Global Symbol Table, they are available throughout this SAS session, until I delete them from the Global Symbol Table or the session ends. That way, they are available to use in the PROC  PRINT step.     Knowing about and using helper macro variables like this is a useful technique for taking the information from one program and saving it into a macro variable for use in a subsequent step. Of course, SAS Macro processing and the Macro facility can be very, very much more complicated than what I show here, but the amount of code that is used is minimal and if you use the var statement to control the order of the variables for PROC PRINT, you don't have to fiddle with the LENGTH statement to make sure that CURRENTOBS appears first. The VAR statement, to me is a better way to control variable order for report purposes. Fiddling with the order of the variables in internal storage is not really necessary, if the end result is a report. (in my opinion I would rather control the order of variables with a VAR or COLUMN statement instead of relying on the data to be in a certain order when internally stored.)   Cynthia ... View more

Hi:   In addition, your program seems more complicated than it needs to be. Assuming that SASHELP.CLASS is sorted by name and that all you want are the last 10 observations, you can create the CURRENTOBS variable with a simpler program and then use options FIRSTOBS and OBS to control only getting the last 10 in PROC PRINT, as shown below:   Or, an alternative approach would be to use Macro variables as helper variables to capture the numbers you need to print only the last 10:   Cynthia ... View more

Hi: The phrase "clinical sas programming" is a very broad topic. If you mean you are doing Clinical Trials Study submissions to a reporting agency, then look up Lisa Fine's book on how PROC REPORT is used for Clinical Trials Reports. Here's the link to that book: https://redshelf.com/app/ecom/book/1878389/proc-report-by-example-1878389-9781612909134-lisa-fine Or, Jack Shostak's book on SAS Programming in the Pharmaceutical Industry: https://redshelf.com/app/ecom/book/1878385/sas-programming-in-the-pharmaceutical-industry-second-edition-1878385-9781612908052-jack-shostak Cynthia ... View more

Hi: The class videos are hosted on BrightCove servers. Failure to view the videos even with Google Chrome or Firefox points to some restriction in your network or browser settings. Please read this article to see which ports and domains need to be enabled for the videos to work: https://studio.support.brightcove.com/general/architecture/domains-and-ports-must-be-accessible-video-cloud.html . If you are using SAS OnDemand for Academics, there are explicit instructions in the Course Overview and Data Setup section of the course for how to set up the data. You need to run a folder and data creation program on SAS OnDemand for Academics in order to make everything needed for the class. Please go back to the Course Overview and Data Setup section -- it is the first one listed in the table of contents on the main class page. Cynthia ... View more

Hi: Review this Tech Support note: https://support.sas.com/kb/31/278.html and you'll see the code to remove this extra Table 1 node. This node is generated by PROC REPORT, so you need to use PROC REPORT to remove it. Cynthia ... View more