Did you try something like this? data for_plot; set sample; day=weekday(datepart(InjuryDateTime)); hour=hour(InjuryDateTime); run; proc sgplot; heatmap x=day y=hour / freq=Injury1; run; proc sgplot; heatmap x=day y=hour / freq=Injury2; run; ... View more

Try telling SAS what BUFSIZE to use instead of accepting the default. data _null_; call execute('data b000 '); do k=1,2,4,8,16,32,64,128,256,512; call execute(cats('b',put(k,z3.),'(bufsize=',k,'k)')||' '); end; call execute(';x=1;run;'); run; proc contents data=work._all_ out=contents memtype=data; run; NOTE: CALL EXECUTE generated line. 1 + data b000 2 + b001(bufsize=1k) 3 + b002(bufsize=2k) 4 + b004(bufsize=4k) 5 + b008(bufsize=8k) 6 + b016(bufsize=16k) 7 + b032(bufsize=32k) 8 + b064(bufsize=64k) 9 + b128(bufsize=128k) 10 + b256(bufsize=256k) 11 + b512(bufsize=512k) 12 + ;x=1;run; NOTE: The data set WORK.B000 has 1 observations and 1 variables. NOTE: The data set WORK.B001 has 1 observations and 1 variables. NOTE: The data set WORK.B002 has 1 observations and 1 variables. NOTE: The data set WORK.B004 has 1 observations and 1 variables. NOTE: The data set WORK.B008 has 1 observations and 1 variables. NOTE: The data set WORK.B016 has 1 observations and 1 variables. NOTE: The data set WORK.B032 has 1 observations and 1 variables. NOTE: The data set WORK.B064 has 1 observations and 1 variables. NOTE: The data set WORK.B128 has 1 observations and 1 variables. NOTE: The data set WORK.B256 has 1 observations and 1 variables. NOTE: The data set WORK.B512 has 1 observations and 1 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds   ... View more

Since SAS7BAT files are BINARY files that are written in blocks the minimum size depends on the blocksize being used.  I am not sure exactly how SAS decides what blocksize to use but I suspect is is heavily influenced by the blocksized used by the device that you are writing the SAS file to. Check the settings of the device that you wrote the file on. ... View more

The default FONT used by SAS/Studio setup for SAS ODA makes the Greek characters the same as the Latin ones when I run your program. Looks like that might be using TIMES as the FONT. ... View more

Sounds like you need to find a FONT that has both the normal letters and also Greek mu and gamma. ... View more

Why all that rigmarole to change the variable names and order?   Why not just read the CSV file yourself so you can control the names and order instead of forcing SAS to GUESS what is in the CSV file and so use names and order you don't want?   Something like: data filter1_data; infile "\\columbia\dfsr1\Actuarial\Alice\Ohio PPA Agents\Filtered.csv" dsd truncover firstobs=2 ; * Define the variable type and storage lengths in the order you want; length ...... ; * Now read in the variables in the order they appear in the CSV file ; input ..... ; run;   ... View more

Do you want an actual XLSX file?  Or do you instead just want to make a series of CSV files like you started with?   If the latter it is much easier since you can just use the FILEVAR= option on the FILE statement. %let varnames= Agent_Name Family_Number Unit_Number Zip_Code Effective_Date Single_Term_Current_Premium Single_Term_Proposed_Premium Single_Term_Impact Annualized_Current_Premium Annualized_Proposed_Premium Annualized_Impact Impact_Percent ; %let path=where ever you want to write the new csv files; data _null_; set filter_2; by agent_name; * Calculate filename to use ; filename=cats("&path/",agent_name,".csv"); file csv dsd filevar=filename; * Write header line when starting a new AGENT ; if first.agent_name then put "%sysfunc(translate(&varnames,%str(,),%str( )))"; * Write data line ; put &varnames; run; ... View more

and a PDF file named 'PDF_output_file.pdf' will be created in the same directory in which the ODS_PDF() module was executed. Not really.  It will create the file in whatever directory the macro variable SAS_EXECFILEPATH (if it exists) is pointing at.       ... View more

You are using FILEEXISTS() to test if the physical file exists and then using the FDELETE() function to delete whatever physical file the filref PDF_REF is pointing at.  There are two problems with that: that fileref might not have been defined yet that fileref might be pointing at a completely different file. It might make more sense to run the FILENAME() function first.  You can then use the FILEREF() function to check if (A) the filename function worked and (B) the file it points to exists or not.  Then you can decide if the existing file needs to be deleted.   Example of using FILEREF(). 1 * Macro to check a fileref and report results; 2 %macro file_chk(fileref); 3 %put NOTE: &=fileref %sysfunc(choosec(2+ %sysfunc(sign(%sysfunc(fileref(&fileref)))) 4 ,is Defined but does NOT Exist 5 ,is Defined and Exists 6 ,is NOT Defined)).; 7 %mend file_chk; 8 9 * Make sure PDF_REF fileref is not defined ; 10 %let fileref=pdf_ref; 11 %put rc=%sysfunc(filename(fileref)); rc=0 12 13 %let path=%sysfunc(pathname(work)); 14 %let fileref=pdf_ref; 15 * Check FILEREF ; 16 %file_chk(&fileref) NOTE: FILEREF=pdf_ref is NOT Defined. 17 * Use FILENAME() to create FILEREF ; 18 %let rc=%sysfunc(filename(fileref,"&path/test.pdf")); 19 %file_chk(&fileref) NOTE: FILEREF=pdf_ref is Defined but does NOT Exist. 20 21 * Write something to the file ; 22 data _null_; 23 file &fileref; 24 put 'hello'; 25 run; NOTE: The file PDF_REF is: (system-specific pathname), (system-specific file attributes) NOTE: 1 record was written to the file (system-specific pathname). The minimum record length was 5. The maximum record length was 5. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 26 %file_chk(&fileref) NOTE: FILEREF=pdf_ref is Defined and Exists. 27 28 * Remove the file ; 29 %let rc=%sysfunc(fdelete(&fileref)); 30 %file_chk(&fileref) NOTE: FILEREF=pdf_ref is Defined but does NOT Exist. 31   ... View more

@alepage wrote: ERROR: Nesting of %IF statements in open code is not supported. %IF ignored. ERROR: Skipping to next %END statement. You can either remove the %ELSE and make each %IF independent. %if &cie=b1 %then %do; company="A"; %end; %if &cie=b2 %then %do; company="B"; %end; Or perhaps you don't need the second %IF at all and can instead just use the %ELSE. %if &cie=b1 %then %do; company="A"; %end; %else %do; company="B"; %end;   ... View more

@alepage wrote: The script below is not giving the expected result. Please correct the script   /*%let cie=b2;*/ %let cie=b2; data class; format company $1.; set sashelp.class; if &cie eq b1 then company="A"; else if &cie eq b2 then company ="B"; run; Just be your own macro processor and see what SAS code you asked the macro processor to create.  Your example would generate this data step. data class; format company $1.; set sashelp.class; if b2 eq b1 then company="A"; else if b2 eq b2 then company ="B"; run; Since SASHELP.CLASS does not have variables named B1 or B2 the IF condition will be true since both variables will always have missing value.  So the new variable COMPANY will always be set to "A".   PS  Why did you feel the need to attach the $1. format to COMPANY?  It really won't have any impact on how SAS displays it since it will only be one byte long. Perhaps you meant to use this statement instead to define COMPANY as a character variable with a storage length of one byte. length company $1; ... View more

Probably only the SOURCE entries. Also if it is really from 28 years ago you might need to have access to an old version of SAS to read it.  Catalog files are not cross version compatible like V7 SAS datasets are. ... View more

Can you see why that did not work? Do you see the pattern that will emerge in the output? Hint: Check how many OUTPUT statements the data step executes on each input observation. Think about what values the variables will have when the OUTPUT statements execute. ... View more

In addition it is always preferable to use normal SAS code to read a delimited text file (aka CSV file) instead of using PROC IMPORT.  This ie because a delimited text file has no place to store information about how to define the variable which forces PROC IMPORT to make educated GUESSES about how the variables should be defined. ... View more

What did you try?  How did it go?  Did you get any errors in the log?   You just need to add two statements and modify one other. data want2; set db; length TypeTransfusion $20; array list TypeTransfusion1-TypeTransfusion3 ; array list2 Result1-Result3; do index=1 to dim(list); TypeTransfusion=list[index]; Result=list2[index]; output; end; drop TypeTransfusion1-TypeTransfusion3 Result1-Result3; run;   ... View more