Hi:   I'm not sure what you want. Remember that a SAS date value is stored internally as a number and a SAS date/time value is also stored internally as a number. The format that you show is only how the variable is displayed in output, such as reports. Without any format being applied, you can prove this to yourself by running this program:   That very large number that is stored internally represents the number of seconds between midnight on Jan 1 1960 and your date/time value. If you already have date/time variables stored in your data, then your assignment statement is NOT applying a format. If you want to apply a format to change the way your variable is displayed, you would use a FORMAT statement or  for the PUTLOG statement, you can specify the format after the variable to be displayed in the log. Note the difference between a format with a width of 20 and the format with a width of 18 -- that will give you the 2 digit year you seem to want. Just remember that your assignment statement is NOT storing your date/time value in a readable format --your numeric date/time value is ALWAYS stored as a number.     Perhaps if you could explain a bit more about your data and what you need to do, it would be easier to understand why you think the assignment statement is necessary. Cynthia   ... View more

Hi:   Your original code has a "timing" issue. Think about PROC REPORT as only placing one value on the report row at a time, following the order of the variables in the COLUMN statement from left to right. So on the first data row on the report (after the column headers), the first item that PROC REPORT puts on the report row is the value for ID -- at that point in PROC REPORT timing -- only the value of ID is known. When PROC REPORT puts the ID value on the report row, it hasn't placed VarA or VarB on the report row yet, so it has no visibility or knowledge about what those values are.    In the same way, next, PROC REPORT writes the value of VarA to the report row. Now, in a COMPUTE block for VarA, you can test either the value of ID OR the value of VarA. But, just like before, when PROC REPORT is putting the value for VarA on the report row, it doesn't know what the value is for VarB, so in terms of your comparison in the COMPUTE block for VarA, inside that COMPUTE block, PROC REPORT doesn't have any value on the report row yet for VarB, so the value of VarA can't be compared to VarB because VarB isn't on the report row yet.  So it's not the order of the COMPUTE blocks that will make a difference, but changing the placement of the conditional testing until AFTER all the report row has finished being built. That means in the COMPUTE block for VarB, you will have the ability to use your conditional logic because at the point in time when the COMPUTE block for VarB is executed, ALL of the items on the report row have been placed down, so now PROC REPORT knows the values for ID, VarA and VarB. Basically, you can remove the COMPUTE block for VarA, but move the IF statement into the block for VarB. You'll need to change the CALL DEFINE for the VarA IF to be sure that the correct column is highlighted, as shown in the screen shots for results and code below. Cynthia Results:   Code:       ... View more

Hi: This is not really an "ongoing" discussion, since the last post before your post was 6 years ago in 2019. The only reason it is still open is that the original poster never indicated that the thread was solved. At any rate, back in 2019, the version of SAS Studio being used was different than the version of SAS Studio that is current now. It also makes a difference what browser you're using with SAS Studio. Your best resource for this type of question would be work with Tech Support. I've never experienced the type of behavior that you're describing in SAS Studio on the SAS OnDemand server, so I don't have any good suggestions for you. You can contact Tech Support by sending mail to support@sas.com and include your Site ID and version/Operating System information and a description of the issue. Cynthia ... View more

Hi: As previously mentioned, some of the options specified in your code are LISTING only options and are ignored by ODS RTF and other ODS destinations. (HEADLINE, HEADSKIP, SKIP, etc -- all these and others are well documented) . To impact the RTF output, the best option is to use STYLE= overrides that are supported by ODS RTF, ODS PDF and ODS HTML. There have been many previous posts about using STYLE= overrides. And, as previously explained, without data, no one can test or tweak your code. Cynthia ... View more

Hi:   If this is a new behavior when you change operating systems/editors to create the SAS data, then this is probably an issue you want to raise with SAS Tech Support. They would need to look at all your code and understand the previous operating system/editor versus the current operating system/editor to explain why the difference occurs. You can always open a case with SAS Tech Support by sending mail to support@sas.com . Cynthia ... View more

Hi:   If you run PROC CONTENTS, you should see that the variable Y has been defined as character with a length of 1 byte. SAS represents missing values for a character variable as a space. This is essentially what your assignment statement is telling SAS to assign to the value for Y.   Just because your assignment statement has y='' (with the 2 quotes next to each other), in your program it is the same as if you had used y=' '; (quote space quote). Either way the stored value for Y is a missing value -- or space for the character variable.    That should create Y as a character value with a length of 1. So when the data is exported to Excel, the space character is what fills the cell. You call it a "false space" but in fact, it is a real space and your code assigned the space to Y. Cynthia ... View more

Hi Another suggestion is to be sure that your folder path is 100% correct in the right case and spacing. For. example, SAS OnDemand would consider Data Dictionary (with space) DataDictionary (no space) data dictionary (lower case with space) datadictionary (lower case, no space) to be 4 separate folder names. Or, myfolders, My Folders, and my folders are all different folder names. Without seeing your error messages, it is hard to just guess what the error might have been. However, one of the most common issues that people encounter with using the SAS OnDemand server is making sure that their folder paths are correct. You can always right click on a folder in the Server Files and. Folders panel and choose Properties to see the full and correct path to use for that folder. Cynthia ... View more

Hi: Reread the instructions for the practice again and then run a PROC CONTENTS on the pg2.np_yearlyTraffic data table. In the instructions, there is a sentence that says "Notice that the Count column records the number of cars that have passed through a particular location." So, you need to use the COUNT column from the starting data to create totTraffic in this instance. In a different scenario, you might create your own variable, but it is not necessary in this case. Cynthia ... View more

Hi: The INFORMAT you use in your INPUT. statement MUST match what is contained in the character value you want to convert to numeric. You are making the new numeric variable CRDATE by using the INPUT function to turn the string '2024-11-15', etc, into a numeric value representing a SAS date value. You told the INPUT function that CREATIONDATE should be transformed using the INFORMAT mmddyy10. I'm not entirely sure you need TRIM, depending on whether the original variable has trailing spaces. However, your CREATIONDATE character string looks like it is YYYY-MM-DD on all the rows you gave as an example. So I think you need this: crdate = input(trim(creationdate), yymmdd10.); Cynthia ... View more

Hi:   You might want to go back and revisit the lectures on the RETAIN statement and the SUM statement. In this code (I changed the output data table names with 1 and 2), You can see that the only difference is the RETAIN statement. The fact that Example 2 works the same as Example 1 tells you something about how the SUM statement works.   Notice that the lecture on the SUM statement explains that the SUM statement does an automatic RETAIN.   Thus, the RETAIN statement in the first example is not necessary for purposes of having the program work. On the other hand, using a RETAIN statement, even with a SUM statement makes it clearer that totTraffic is the variable being accumulated and retained.    Understanding when you need to use RETAIN and when it's not absolutely required is one of the objectives for this practice. However, you can break the SUM statement like this:   Learning when to use the RETAIN statement and how the SUM statement works is one of the goals of this Lesson. Cynthia   ... View more

Hi,   Thanks for explaining what you're using to study. The data for some of our free classes, like Programming 1 and Statistics 1 is available from inside the free e-learning version of the class. However, the Machine Learning class is not one of the free classes.   The Machine Learning class data is provided only on our Virtual Lab images. When a student purchases a Learning Subscription with the Machine Learning class or when they take the class as an academic user then the data is pre-loaded on the lab they use for class.   So that is why you're not finding the COMMSDATA table when searching for publicly available data for the class. You can look for some alternative data in the SAS documentation. Sample data for SAS Viya platform: https://support.sas.com/documentation/onlinedoc/viya/examples.htm Sample data for SAS Visual Analytics: https://go.documentation.sas.com/doc/en/vacdc/v_031/vareports/n1dj9jn3klf501n1ovpkkahcegot.htm My understanding is that you should find the HMEQ data as publicly available data to use to practice. Here's a video that shows using HMEQ data in Model Studio: Demo using HMEQ Sample data: https://www.youtube.com/watch?v=Ep3p7WzptCw Cynthia ... View more

Hi, There are several different ways that we provide a SAS Viya environment to practice the Machine Learning course: 1) SAS  Viya for Learners which is the platform available to academic users to practice; 2) Virtual Lab inside the Machine Learning class that is available with a paid subscription; 3) Virtual Lab interface accessible from inside Coursera/SAS classes.   However, the class name you say you are taking or reading sounds more like one of the classes on our platform, not on the Coursera platform.   Depending on which of these methods you are using, you should find the COMMSDATA file when you are in Visual Analytics or in Model Studio. However, if you are using SAS  Viya at your company installation of SAS Viya or in one of our Viya free trial packages, our class data would not be loaded at your company and our class data is not loaded in the Viya free trials.   When you say that you've looked in SAS Studio for the data, depending on which SAS Studio you're using, you would not find the data in SAS Studio on your work installation of SAS or  on the SAS OnDemand for Academics server. If you are a university student and are using SAS Viya for Learners, then you should be able to find the data when you use Model Studio or Visual Analytics or SAS Studio under the Develop Code and Flows menu.    Can you clarify how you're using SAS Studio and how you're taking the course? For example, did you sign up for the course on the SAS web site? Or on the Coursera web site? Or is your University professor teaching Machine Learning using SAS Viya as a  text in your class--in this case, I would expect your professor to also be having students do practices on the SAS Viya for Learners platform.   Once we know better which SAS Studio you're trying to use to  open the COMMSDATA file, it will be easier to help you. As I remember most of the practices in the Machine Learning class use SAS Viya and Model Studio. The first demo in the most current version of the Machine Learning class has students open Model Studio and navigate to the COMMSDATA file, which is already loaded on the SAS Viya for Learners server. That first demo does not have students open COMMSDATA with SAS Studio.   What version of the class are you taking?  If you are using SAS Course Notes, then most of our courses with course notes assume that students are using the classroom image that is loaded in the Virtual Lab. University students using SAS Viya for Learners have slightly modified instructions. Knowing how you are using SAS  Studio, which platform and which version of the class would be very useful information. Cynthia ... View more

Hi:   That is not what I observed. Did you run my test program using my fake test data? With the test data and nearly the same program (columns=2 instead of columns=3) that specific character string worked in the WHERE statement in my test program. If the test program works on my test data, but the WHERE does not work on your real data, then I would suspect some issue with the way the values are stored in the data set....either unprintable spaces, two underscores or two hyphens instead of 1, leading spaces....something is off with the data.   If you run my test program with MY fake test data, and the WHERE in the SGPANEL does not create the graph that I pasted, then, that is an issue you need to address with Tech Support.   My test data and test program proves that the string '464918_99' can be used in a WHERE statement and the condition works correctly, when '464918_99' is in the data.    You have not provided any sample or representative data or shown a SAS log which should have something like THIS after the SGPANEL step that shows EXACTLY how many observations were selected based on the WHERE:  You keep saying that the character string is not being 'read' by the WHERE statement, which is clearly NOT the case in my test program. Just saying over and over that the value is not being read doesn't help anyone make constructive suggestions because you haven't said whether Variety is a character or numeric variable in your data; you haven't said whether Variety has a user-defined format in use; you haven't shown any results or log messages that illustrate your assertion that the value is not being read or used by the WHERE statement. On the other hand, several community members have made suggestions and provided code and asked questions that all point to other things you need to check before you can really say that the WHERE statement is not 'reading' the value '464918_99'.   So, did you run my ENTIRE test program and what EXACTLY did the log show and what EXACTLY were the results? Cynthia     ... View more