Hiding continuation characters, like the commas in your macro call, at the END of the line makes much more difficult for a human to scan the code and confirm it meets the required pattern.   %T(YEAR=2018 ,FILE=D2018 ,base=USA ,scale_name= CIL ,TABLE= TABLE1 ); Turn on the MPRINT option before the macro call to see what SAS code the macro call ends up generating. ... View more

I do not understand what you want.   It sounds like you want to count and take the mean of the counts. But you don't need to do that as the mean of the counts is just the total number of observations divided by the number of distinct values.   For example if you had GENDER coded as M and F there are two gender categories.  So the mean of the count of people per category is N/2.   What do intend to DO with this mean?  What value would a SD add?   ... View more

The code you posted is using the TOUCH command. So what is it that you want translated?   State clearly what you want.  You mentioned modified time IN a file.  The code you posted is not putting anything INTO a file.  It is changing the last modified date OF a file.  ... View more

@jason4sas wrote: Agree. But still, how come the returned value is truncated? If I simply replace the macro variable with its true value, the truncation is not happening:   %put WARNING: %sysfunc(ifc(%length(abv,bdev),%str(,abv,bdev),)); WARNING: ,abv,bdev   Therefore, it seems %str(,&final_class) coming with something unexpected inside of the %sysfunc.  Because now there is something for %STR()  to quote.   Before %STR() was ignoring the value of the macro variable.  That is not its job to worry about.    If you look at the values that are stored in the SASHELP.VMACRO you can see how there is difference between the result of use %str() on A,B when it is text or when it is the result of expanding a macro variable reference. 10 %let x=A,B; 11 %let y=%str(A,B); 12 %let z=%str(&x); 13 14 data _null_; 15 set sashelp.vmacro; 16 where name in ('X','Y','Z'); 17 put name= value= +1 value $hex12.; 18 run; name=X value=A,B 412C42202020 name=Y value=
AB 01411E420220 name=Z value=
A,B 01412C420220 And if you use %QUOTE(&x) instead you get: name=Z value=AB 03411E420820 ... View more

Because you told PROC IMPORT to GUESS how to read the data. And to GUESS for each file independent of the other files.  And to GUESS using only the first 20 lines of the file.   Just write your own data step to read the files. Here is a simple template.     data EAP; length filename $200 fname $20 ipedsyear 8 ; infile "[directory path]eap*.csv" dsd truncover filename=filename ; input @; if filename ne lag(filename) then delete; fname = scan(filename,-1,'/\'); ipedsyear = input(substr(fname,4),4.); length var1 $25 var2 8 var3 $10 var4 8 var5 8 varlast $10; informat var5 mmddyy.; format var5 yymmdd10.; input var1 -- varlast; run; Just update the LENGTH statement to use the names and types of the variables in your CSV files.  Update the INFORMAT and FORMAT for any variables that need them (normally only DATE, TIME and DATETIME values need special informats or formats).  And update the INPUT statement to use the variable list based on the first and last variable in your files.   For my example I assumed your CSV files have 6 variables named VAR1 to VAR5 and VARLAST.  Some of them are character and some are numeric (length=8).  One is a date string that has values stored in MDY order in the CSV file but that you want to print using YMD order so that you don't confuse half of your audience.   ... View more

Assign a RANK to each observation.  Sort by the RANK.  And set the flag true only on the first observation.   data have; infile cards dsd dlm='|' truncover; input Facilityid Lender :$20. LenderRole :$20. LeadArrangerCredit :$3. AgentCredit :$3.; cards; 1|Deutsche Bank|Arranger|Yes|No 1|Goldman|Admin Agent|No|No 1|JP Morgan|Participant|No|No 1|Citi|Administrative Agent|No|No 2|Morgan Stanley|Manadated Lead arranger|No|No 2|Wells Fargo|Bookrunner|No|No 2|UBS|Bookrunner|No|No 2|Credit Suisse|Bookrunner|Yes|No 3|Deutsche Bank|Administrative Agent|No|Yes 4|JP Morgan|Bookrunner|No|No 4|Goldman|Bookrunner|No|No 4|Citi|Bookrunner|No|No 4|UBS|Bookrunner|No|Yes ; data rank; set have; if lenderrole='Administrative Agent' then rank=1; else if LeadArrangerCredit='Yes' then rank=2; else if AgentCredit='Yes' then rank=3; else rank=4; run; proc sort; by facilityid rank; run; data want; set rank; by facilityid rank; FLAG = first.facilityid and (rank<4) ; run; Results:     ... View more

Because %STR() is not quoting the value of the macro variable referenced. Use %QUOTE() instead.   In general %STR() is for quoting the text that is in your program.  If you want to quote text that is GENERATED by your program use something else. ... View more

@JKHess wrote: Thanks so much...I'm running this now. What I'm still confused about is why SAS apparently mixed formats when reading in the file. If it decided that the format was dd/mm/yyyy instead of mm/dd/yyyy, then why did it correctly read in dates that had a 'day' value>12?  SAS did NOT switch format (I think you meant INFORMAT).   The problem is that the file you get with the Export CSV option uses an AMBIGUOUS style for the text of the DATETIME fields.  It has text in the style AA BB CCCC DD:EE FF.   That is why I said to use the file produced by the API url instead.  That file has the datetime strings in the unambiguous ISO format of YYYYMMDDThhmmss.    PROC IMPORT did not know of a SAS informat that could read that so it used ANYDTDTM informat which can handle many different styles, picking the one it thinks best matches the current string's value.    When the value of either AA or BB is larger than 12 then it is obvious which one is the DAY and which one is the MONTH.  But for a value like '01 04 ...' either one could be the month.     In that case the ANYDT... informats use the setting of the DATESTYLE system option.    That is normally set to use the order most often used by the country indicated by the LOCALE setting.  So in the US it would assume 01 04 is January fourth.  But in Europe it might assume you wanted first of April.   If you have one order you want it to use the set the DATESTYLE option before the call to PROC IMPORT.     Since this data is from NYC you should set DATESTYLE to MDY.   ... View more

Here is another one. This works: data _null_; call execute('proc print data=sashelp.class;var'); call execute('name'); call execute('sex'); call execute(';run;'); run; But if you send the exact same set of characters as one string it does not work since there is nothing between the variable names. data _null_; call execute('proc print data=sashelp.class;varnamesex;run;'); run; Breaking the statements into multiple pieces has an impact on how it is parsed by SAS.   ... View more

No idea.  Why would you attempt to send block comments to CALL EXECUTE()?  And if you did why in multiple function calls?   Write the code to a file if the goal is to produce a human readable code file.  Then the block comments will work as expected when the file is sourced using %INCLUDE. ... View more

You don't show any numbers in your expected output so it is impossible to tell what "percentage sum" you want to calculate.   Also it looks like you have unique combinations for A, B and C so the counts of any frequency tables are going to be 1 in every combination so I am not sure what you intended to calculate. ... View more

You can see the problem in your screen shot. Notice the horizontal position of the letter C in the variable 'Case Number'n . Then notice that the first visible letter in the other variable names is slightly shifted to the right for the other variables.   Run PROC CONTENTS and create a DATASET with the variable names.  Then use the NLITERAL() function to generate strings you can use to reference those strange variable names. proc contents data=bodyfat out=contents; run; data _null_; set contents; nliteral=nliteral(name); put nliteral name=$quote. label=$quote.; run; Then copy and paste the name literal strings from the SAS log into your VAR statement. ... View more

Yes.  Change the code so it does not cause that note/warning.   If there is a syntax error you should see in the LOG the code with underlines below it showing what part of the code is generating that note.  If not then you probably will see notes about trying to convert strings to numbers.   So what code is on line 520 of your program?  What statement/function call starts at column 35?   Example: 1233 data test; 1234 set sashelp.class; 1235 x = sex*name; 1236 run; NOTE: Character values have been converted to numeric values at the places given by: (Line):(Column). 1235:6 1235:10 NOTE: Invalid numeric data, Sex='M' , at line 1235 column 6. NOTE: Invalid numeric data, Name='Alfred' , at line 1235 column 10. Name=Alfred Sex=M Age=14 Height=69 Weight=112.5 x=. _ERROR_=1 _N_=1 So on line 1235 this program is trying to treat SEX and NAME as if they had NUMERIC values.  So SAS happily tried to convert M and Alfred to numbers, but it couldn't. So the fix is not to treat character variables as numbers.  If the character variable has a value that could be a number then convert it yourself using the appropriate informat.   ... View more

Double check the name it generates for the first column.  The ZIP engine has a nasty habit of including the BOM (Byte Order Mark) as part of the data. ... View more

Example: proc format ; invalue $yntf 'Y','true'='Y' 'N','false'='N'; run; data nycems; infile "c:\downloads\nycems.csv" dlm=',' dsd truncover firstobs=2 ; length cad_incident_id 8 incident_datetime 8 initial_call_type $6 initial_severity_level_code 8 final_call_type $6 final_severity_level_code 8 first_assignment_datetime 8 valid_dispatch_rspns_time_indc $1 dispatch_response_seconds_qy 8 first_activation_datetime 8 first_on_scene_datetime 8 valid_incident_rspns_time_indc $1 incident_response_seconds_qy 8 incident_travel_tm_seconds_qy 8 first_to_hosp_datetime 8 first_hosp_arrival_datetime 8 incident_close_datetime 8 held_indicator $1 incident_disposition_code 8 borough $24 incident_dispatch_area $2 zipcode 8 policeprecinct 8 citycouncildistrict 8 communitydistrict 8 communityschooldistrict 8 congressionaldistrict 8 reopen_indicator $1 special_event_indicator $1 standby_indicator $1 transfer_indicator $1 ; informat incident_datetime first_assignment_datetime first_activation_datetime first_on_scene_datetime first_to_hosp_datetime first_hosp_arrival_datetime incident_close_datetime anydtdtm. zipcode comma. valid_dispatch_rspns_time_indc valid_incident_rspns_time_indc held_indicator reopen_indicator special_event_indicator standby_indicator transfer_indicator $yntf. ; format incident_datetime first_assignment_datetime first_activation_datetime first_on_scene_datetime first_to_hosp_datetime first_hosp_arrival_datetime incident_close_datetime datetime19. ; input cad_incident_id -- transfer_indicator ; run; ... View more