OUT= names the data set created with the name following the =. OUTPCT as an option would look like:   PROC FREQ DATA=subset; TABLES make*origin / OUT= mydatasetname OUTPCT; RUN;       @_maldini_ wrote: I'm trying to output summary statistics from PROC FREQ so that I can use PROC SGPLOT to plot column percentage on an X-axis.   I'm trying to following the SAS documentation: "If you specify the OUTPCT option for a two-way or multiway table, the output data set also includes row, column, and table percentages."   PROC FREQ DATA=subset; TABLES make*origin / OUT=OUTPCT; RUN; The above syntax only produces a data set w/ Count and Total Percent.    What is the proper format for the OUT= option? How do I incorporate OUTEXPECT or OUTPCT or PCT_COL into the syntax?   Thanks!     ... View more

@ballardw Good catch 🙂 ... View more

> So you just change the style and re-run the syntax? Yes   > Is there a way to change some of the attributes of a style once you select it? Not by using the interface. You would have to use PROC TEMPLATE and submit code.   ... View more

The PUT() function use FORMATs, not INFORMATs. Formats convert values to text.  Informats convert text to values.   The width used to read a character string into a number does not make a difference since there is only one way to store any given number. (Note if the width used on the informat is shorter than the string being read there could be an impact when converting text into numbers, since then the trailing characters in the string are ignored when deciding what number they represent.  If you read the string '1234' with the informat 3. you get the number 123 instead of the number 1,234 since the '4' is not read.)   The width used to write a number makes a big difference in the value being stored because there are many ways to write the same number as a character string. The value 10 written with 5 characters is a different string than the same number written using 6 characters, there will be an another space character written.  Or you could write the number with leading zeros instead of leading spaces. Or trailing spaces instead of leading spaces.   If the values can only be integers (or at least you want the value printed into the character variable to be rounded to an integer) then using a format like 32. might be appropriate.   But if you know the values are integers that are always between 100 and 999 then using the format specification of 3. makes sense.  If the the values can be less then 100 do you want leading zeros instead of leading spaces? Use the format specification Z3. instead to get leading zeros.  Of use the format modifier -L to remove the leading spaces.   CharID = PUT(StudentID, Z3.); CharID = PUT(StudentID, 3.-L);  If the values contain fractional parts then you might want to use a fixed number of decimal places by using a format specification like 10.3.  Or if the range of values is extreme you might want to use the BEST format so that SAS will try to use the best format for the value that can fit into the number of characters specified by the width used in the format specification. ... View more

Usually easier to just copy/paste the text into your post, like you did above. I (and other users) hate downloading files. If I downloaded a file for each question I tried to answer my downloads would get too bogged down..... Remember to limit it to just a few observations though. You should be able to run that code successfully on your computer anyways. ... View more

@timeless wrote: That was exactly what I was doing Check your program and SAS log more carefully.  The only way to get that message is to not include a format specification. If you include an invalid format specification you get a different error message. 718 data _null_; 719 input string $20.; 720 num1=input(string,20.); 721 num2=input(string,??20.); 722 num3=input(string,??); - 22 76 723 num4=input(string,); - 22 76 724 num5=input(string,1234); ---- 85 76 ERROR 22-322: Expecting a format name. ERROR 76-322: Syntax error, statement will be ignored. ERROR 85-322: Expecting a format name. 725 cards; NOTE: The SAS System stopped processing this step because of errors. NOTE: DATA statement used (Total process time): real time 0.02 seconds cpu time 0.03 seconds ... View more

Solved. Thank you! ... View more

This is the current graph. I'd like to limit the decimal places to 2.  ... View more

Thanks! ... View more

Label options CURVELABEL <=“text-string”> adds a label for the curve. CURVELABELATTRS=style-element<(options)> | (options) specifies the appearance of the labels in the plot when you use the CURVELABEL= option. CURVELABELLOC=OUTSIDE | INSIDE specifies whether the curve label is placed inside the plot axes (INSIDE) or outside of the plot axes (OUTSIDE). CURVELABELPOS=AUTO | END | MAX | MIN | START specifies the location of the curve label. DATALABEL <=variable> displays a label for each data point.   https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/grstatproc/n1jkqnmk6y6ms9n1b2vvubyzqd4a.htm ... View more

@_maldini_ wrote: Yes, there are formats, but I still can't figure it out. I don't understand the format for "redcap_event_name_". Thanks again for your help!   data kb_data; set redcap; WHERE redcap_event_name = "baseline_arm_1"; WHERE SAME AND informed_consent_hip_v_1 = "0"; WHERE SAME AND informed_consent_hip_v_0 is missing; FORMAT redcap_event_name $redcap_event_name_.; /* value $redcap_event_name_ baseline_arm_1='baseline' fu_1_arm_1='fu_1' fu_2_arm_1='fu_2'; */ informed_consent_hip_v_1 informed_consent_hip_v_1_.; /* value informed_consent_hip_v_1_ 0='Incomplete' 1='Unverified' 2='Complete'; */ /* informed_consent_hip_v_0 does not have a format */ run; Your error messages are because the variable you are using is numeric and you compare it to a character value. When you place digits inside quotes you are intending a CHARACTER comparison. Try = 0; The second error is because the semicolon after redcap_event_name $redcap_event_name_.; ends the Format statement. Remove the ; there and the error should go away.   In future when posting LOG information it is better to copy the log text for the entire procedure or data step, open a text box using the </> and paste the text. It is very hard to deal with pictures of text. Can't copy/paste, make corrections or such. ... View more