Best would be to show the LOG. Copy the code and all of the other messages from the log. Suggest starting a new session and only running the code to assign the library/data set and the steps you show. If you get the same results then show that log. The new session means there will be less stuff to wade through that might be involved.   That sort of error is a bit odd and may relate to something else you had done earlier, possibly related to which ODS destination(s) are open.   Your question about the Title statement I would say is not likely to be the issue. The use of Title as the same as Title1 goes back about 40 years so I doubt very strongly that it has any effect.  ... View more

Why sgplot?   I would tend to use SGPANEL such as proc sgpanel data=_temp; panelby grp1 grp2/layout=lattice; series x=ind y=y/ lineattrs=( color=red thickness=2 pattern=solid); run;quit; Which, barring many values of grp1 and grp2 automatically creates the correct number of rows and columns. Note that Layout=lattice is for exactly 2 Panelby variables. ... View more

Why do you think that is a storage full error? It states a permissions issue which likely means a configuration issue or your admin doesn't want you accessing the location. ... View more

How good is the documentation of the  file you want to read? As in do you know the variable type, length and possibly the needed Informat such as for dates, times or currency and matching display Format? ... View more

I have a silly (?) question: why do you only have one comma in 345,123456  and several other of your example values? Normally when I see a single comma in a value with that many digits I have to assume comma is from one of the languages that uses a comma for separating the decimal and a . for the thousands separator.   Another approach would be use a custom format with differing digit selectors based on range of values but that would normally have multiple commas in those values. ... View more

Don't forget the DIF function: new_days = review_date - lag(review_date); is the same as new_days = dif(review_date); Same concern as LAG for conditional operation.     ... View more

You show some values with one decimal point displayed. What is the FORMAT currently assigned to the values? By default the displayed values are actually rounded by the format and so an actual value of 254.41 and 254.400338 would both display as 254.4.   See if this yields more of what you expect. The round function will round the values to the tenths decimal before the comparisons. data check1; set example; where round(hours1, 0.1)^= round(hours3,0.1) or round(hours2,0.1) ^= round(hours3,0.1); keep id hours1 hours2 hours3 ; run; ... View more

Looking at the data how do we know which is the "latest" entry? Proc SQL in general doesn't normally do anything in the order of the data set so values of variables need to be defined to determine what "latest" might be.   If you need to process data in the order it appears in a data set then the DATA step does that.   Hint: code that does not do what you need is not sufficient description of the process. You need to include a bit more narrative as to what is required referencing variables and values. ... View more

For graphics related questions it is a very good idea to include some example data in the form of working data step code so we can test your plot.  When macro values are included, if they are at all critical, then you should provide a definition of the macro variables so they will resolve to expected values when testing.   What does your LOG look like? Copy your log text and on the forum open a text box using the </> icon that appears above the message window and paste the text. I suspect there may be error messages related to the LEGENDITEM statement.   ... View more

Example data in the form of a working data step and the code used to create the plot you have is a good way to ask a question. Without your code we don't know the options that may be available in the procedure to add stuff.   Where would the purple flag go?  ... View more

A minor detail: do any of the "time" variables cross midnight? If you have a starttime of 23:59 and playtime values like 00:10 you have to deal with possible negative time interval values for comparisons of start of win streak.    I'm not quite sure how your problem would work if the same player had multiple starttime values, play sessions in effect.    For consideration, when you have a two value variable, such as your Result, you may want to consider using a numeric 1/0 value as there a many things that can be done with such much easier than with character values. For example if you code 1 as win and 0 as lose then the SUM of the result over any group of observations is the number of wins, the Mean would be the percent of wins in decimal form, i.e. .60 = 60% wins. ... View more

Make sure every data set has a variable, same name in all, with the source data year. Make sure that all of the same named variables existing in the data sets have the same properties: type, length, label and range of values. I always found  changes in value ranges much more of a problem than intermittent missing values such as you describe from versions of the data set.   Append the data sets with a data step then all of the variables will be in the resulting data set with missing values for the years the variable isn't in the source data. The data step appending the data can also be used to create new variables to hold the analysis values such as when the ranges of values change.    I would be very tempted to assign special missing values to variables that were not in a given year so the data set documents the reason they are missing instead of having to go to an external dictionary.   I suspect any dummy variable approach, assuming you mean to add an indicator variable for each of the actual data points, is likely to add complexity to any analysis, increase the data set size significantly and likely not be very helpful in the long run.       Depending on the analysis you may want to use options that treat missing values as an analysis level.  ... View more

What you describe is generally considered poor practice in the world of relational databases. It is also possible that your current data design is poor if this sort of thing, adding variables to the same-named table, is needed.   A more typical approach would be to have a view or query that reads the existing data table that had the results needed and use the view for reporting or whatever that table with the additions is used for. Properly designed views would use "new" table after import or update or what ever is causing new data. Then nothing to delete, just remember to use the view instead of the raw data table. ... View more

Related functions WHICHN and WHICHC may be useful if you need to extend this logic to selecting more  choices.   Be very sure of the CASE of the compared character values using IFC and WHICHC.   %let ref_mm_ind_stind=%sysfunc(ifn(&mmnote=max, 400, &ref_mm_ind_stind)); would not get the desired behavior if &mmnote has a value of MAX (or many others with one or more capital letters). If the resolved values of the macro variable MMNOTE might have case issues then use one of the %LOWCASE or %UPCASE in macro code such as %let ref_mm_ind_stind=%sysfunc(ifn(%lowcase(&mmnote)=max, 400, &ref_mm_ind_stind)); This can be very important if you have to deal with user entered values such as a response to a prompt. ... View more

@Hopes wrote: Hi everyone, I forgot to mention that when I run the code, it generates the report without any problem. However, I coded the report in SAS to be shared with internal people via email, along with a link that allows them to access the report saved in an internal folder. When I click on the link, I see the issue with the title. I think it could be an Outlook issue rather than SAS, which is another potential cause. Here is an example of the SAS code for the email:  Since the code following the above has no Title statement you might need to tell us what part of the code shown contains your "title".   If you haven't worked with SAS very long you may not have learned that TITLE and FOOTNOTE statements persist in a given session until changed. So if a previous unrelated program has a TITLE "Some title text"; then that title will appear in all output following. You would use a simple TITLE; to clear all of the title text following.    Best practice when posting code is to paste the text into a text or code box opened on the forum using the </> or "running man" icon that appears above the message window. Code pasted into the main message window will be formatted by the forum software and may result in artifacts that change the behavior of the code when copy/pasted into a SAS session for testing. The box also helps visually separate the text discussion of the problem from the code. Log text should go into a text box as well.   I will be a bit pedantic and say that your first code does not actually show the code you ran, only the definition of a macro. Statements prior to the macro execution  may be the cause.  It might also help to specifically state which "title" text you do not want to appear. The commented out code in the macro including ODS PDF might indicate as well that you are generating a PDF or some other ODS destination output as well. At which point options like GTITLE/NOGTITLE and GFOOTNOTE/NOGFOOTNOTE might come into play. ... View more