About Tom

Tom

You left the BY keyword out. And you don't need to include a constant variable like your new WAY in the BY group. But those are not the issue I think you are asking about. Basically SAS is saying that just changing the name is not really making a new variable. So you have two choices. Remove the CALCULATED keyword. select 'way 3' as way , id , t as s_new , count(*) as freq from have group by id, s_new ; Or add some none destructive operation, like TRIM() for character variables or SUM(var,.) for numeric variables, so that it will treat it as calculated. select 'way 3' as way , id , trim(t) as s_new , count(*) as freq format=4. from have group by id, calculated s_new ; And if all you wanted was the change the variable name you could just use the RENAME= dataset option on the source dataset. select 'way 3' as way , id , s_new , count(*) as freq format=4. from have(rename=(t=s_new)) group by id, s_new ;

SASKiwi

A temporary table is your best option as it avoids limits on lengths of SAS and macro variables and SQL statements.

Tom

If you have a BY variable then you don't need to use that trick with the conditionally executed SET statement. Just use MERGE. data want; merge cars tbl1; by type; run;

ChrisHemedinger

@Angelfish The IT client supports TRIPLEDES but only when installed with other SAS applications such as SAS for Windows or SAS Enterprise Guide. This is a software distribution practice meant to comply with some encryption technology regulations, where only known customers can get this from SAS. (IT client, as-is, is downloadable by anyone.) This makes the VS Code to SAS OnDemand harder, I know. But I don't have another answer right now. If you are part of an educational institution, I suggest looking into SAS Viya Workbench for Learners.

renee_njc

Hi Tom, I tried the CSS style and it doesn't work. The hyperlink is still there. Here is my CSS style: .body, .systemtitle, .header, .data { font-family: Courier New; } .body { color: black; background-color: white; border: solid black 0.1px; margin-bottom: 0.77in; margin-left: 1.34in; margin-right: 1.34in; margin-top: 0.77in; } .data { color: black; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; border-width: 0.1em 0 0.1pt 0; } .table { background-color: #FFFFFF; border-collapse: collapse; border-bottom-width: 0.1pt; border-collapse: separate; border-color: none; border-left-width: 0px; border-right-width: 0px; border-spacing: 0pt; border-style: solid; border-top-width: 0.1pt; color: black; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; text-align: center; margin-bottom: 0.77in; margin-left: 1.34in; margin-right: 1.34in; margin-top: 0.77in; } .header { border-collapse: collapse; border-bottom-width: 0.1pt; border-collapse: separate; border-color: none; border-left-width: 0px; border-right-width: 0px; border-spacing: 0pt; border-style: solid; border-top-width: 0.1pt; background-color: #FFFFFF; color: #000000; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; } .systemtitle { color: #000000; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; background-color: none; } .systemfooter { background-color: #FFFFFF; color: #000000; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; } .contents { background-color: #FFFFFF; color: blue; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; list-style-type: decimal; margin-left: 0px; margin-right: 0px; } .contents { list-style-type: square; pointer-events: none; } .contenttitle { color: green; font-family: 'Courier New'; font-size: 12pt; font-style: normal; font-weight: bold; margin-bottom: 4em; margin-left: 1em; margin-right: 1em; margin-top: 4em; text-align: center; width: 100%; background-color:aqua; pointer-events: none; } .contentproclabel { color: blue; font-family: 'Courier New'; font-size: 8pt; font-style: normal; font-weight: normal; list-style-type: decimal; margin-left: 0in; margin-right: 0in; } .contentitem { color: red; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; list-style-type: none; margin-left: 15%; margin-right: 15%; } .contentfolder { color: purple; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; list-style-type: none; margin-left: 15%; margin-right: 15%; } .usertext { background-color: #FFFFFF; color: yellow; font-family: 'Courier New'; font-size: 9pt; font-style: normal; font-weight: normal; pointer-events: none; } Here is my SAS code to generate the output: filename ncss "mypath./testt.css"; proc template; define style styles.mycssstyle; import ncss; end; define style styles.mycssstyleprinter; parent=styles.mycssstyle; import ncss print; class contenttitle/ pretext = "TAT"; end; run; ods pdf file="&outdir./test.pdf" style=styles.mycssstyleprinter contents = yes ; ods proclabel = "TEST1"; title "test1"; proc report data=sashelp.class(obs=10); run; ods proclabel = "TEST2"; title "test2"; proc report data=sashelp.class(obs=20); run; ods _all_ close; ods pdf file="&outdir./test.pdf" style=styles.mycssstyleprinter contents = yes ; ods proclabel = "TEST1"; title "test1"; proc report data=sashelp.class(obs=10); run; ods proclabel = "TEST2"; title "test2"; proc report data=sashelp.class(obs=20); run; ods _all_ close; I have tried the code you posted. It doesn't work either.

Tom

@Mscarboncopy wrote: I transformed VAR1 that is being collected as character into numeric to solve my issue with leading spaces for the code you suggested I use for the merge/re-coding of the var ID. This is fake data I am entering, the data is coming from a REDCap form that is being exported as a SAS file. I use the SAS files to run through my code (The two files I mentioned before set 1 and set 2). I did not enter the values in datalines. In the code you suggested I use, you mentioned something about a possible issue coming from a number that is too long? Could that have been it? You should not see issues with dealing with integer values of that length with SAS. Not sure a about what REDCAP is doing internally or how they attempt to convert what they have internally into SAS datasets. Perhaps the field length in REDCAP is limited in some way causing some truncation? Perhaps REDCAP's idea of how to convert what they have into SAS datasets is flawed? Look at the values for the two observations that you think should match before your attempt to convert them on the SAS side into numbers. To really see what character variables have use the $HEX format. That will display each byte as two hexadecimal digits. A space will be show as hex code 20. The digits will be hexcodes 30 to 39. Any other hexcodes will cause trouble. You can get some "rounding" if you where to write out that number using SAS's BEST format without enough characters to represent all of the value. To get only one digit you would have to use BEST3. format, which would result in displaying 7E8 which when converted back into a number would become 7 with 8 zeros. 22 data test; 23 string='657,899,654'; 24 number1=input(string,comma32.); 25 string2=put(number1,best3.); 26 number2=input(string2,32.); 27 put (_all_) (=/); 28 run; string=657,899,654 number1=657899654 string2=7E8 number2=700000000

Richardvan_tHoff

Both Solutions work. Thank you both.

quickbluefish

For this, you'd probably just want use a macro in SAS (basically, an .ado file in Stata - not what Stata calls a macro). To do what you're after, try: %macro loop (varlist=); %let varlist=%cmpres(&varlist); %do i=1 %to %sysfunc(countW(&varlist, ' ')); %let x=%scan(&varlist,&i,' '); ** your code here -- just reference x by preceding with ampersand ; ** for example... ; proc means data=some_dataset; var measure_&x._value; output out=avg mean=mean_&x; run; %end; %mend; *loop(); %let cath=var1 var2 var3 var4 var5; %loop(varlist=&cath);

Tom

@J111 wrote: Hello, We get the same error if the csv is local or if it is located on the web and not at the Linux server. Thanks your reply is helpful. Do you get the error the FIRST time you run that code? Or the only on the second, third, etc ? You did not CLOSE the file you OPENED. data a(drop=fid); infile fileref truncover obs=1; fid=fopen('fileref'); moddate=finfo(fid,'Last Modified'); fid=fclose(fid); run;

hmlong25

Ok thank you that makes sense

Tom

Let's step through each line in the data step an see what it is you asked SAS to do. data want1; So this says the data step is going to create the work dataset named WANT1. format date date9. value 8.; This line is attaching display formats to two variables. Since neither variable has yet been defined the data step compiler will GUESS that you wanted them defined as numeric variables since you are attaching numeric formats to them. stop; This is only executable statement in the data step. It tells the data step to stop running, which prevents it from executing the automatic OUTPUT statement that will run in any data step that does not contain an explicit output statement. So the only difference between the two is that in one you told SAS to use 8 characters to display the variable named VALUE and the other you told it that it should display it with 10 characters instead. So both datasets will have the same variable names, same variable types and the only difference is the display format that is attached. Note that there is no need to attach formats to normal numeric variables, SAS will automatically use the BEST12. format in most places when the variable does not have any format attached. The same with character variables, there is no need to attach the $ format to character variable because the default behavior is to display the full value of the character variable. If you want to avoid forcing SAS to GUESS how to define the variables then define them before using them in statements (like FORMAT, INFORMAT, assignment statements, ARRAY, etc.) that will require that SAS knows the variables type. For example using LENGTH statement. Then you only need to use the FORMAT statement to attach formats to the variables that need them. data want1; stop; length date value 8 ; format date date9. ; run;

Kurt_Bremser

Maxim 6: Google Is Your Friend. Do a search for "crontab", which will lead you to this documentation (Maxim 1!) page: https://man7.org/linux/man-pages/man1/crontab.1.html

Ksharp

Maybe OP has an old version sas. When I do the same thing with very old sas, I am really running into the same problem.

FreelanceReinh

Hello @RichardAD, I think you can retrieve the names of SAS-supplied functions (and CALL routines) from DICTIONARY.FUNCTIONS and then add the names of user-defined functions (and, optionally, subroutines, see 'SUBROUTI' below) from the CMPLIB: proc sql; create table fncnames as select fncname from dictionary.functions where fncname ne ' ' union select scan(_key_,-1,'.') from %sysfunc(getoption(cmplib)) where name in ('FUNCTION' 'SUBROUTI') ; quit; While it should be possible to load this dataset into a PROC FCMP array or hash object, you could also create a numeric informat data infmt; retain fmtname 'isfncname' type 'I' label 1 hlo 'U'; set fncnames(rename=(fncname=start)) end=last; output; if last then do; hlo='O'; label=0; output; end; run; proc format cntlin=infmt; run; and then use the INPUT function to obtain the 1/0 flag for existing/non-existing function names: data test; input name :$20.; fnflag=input(name,isfncname.); cards; cos propcase baseconvfp other ; In my SAS session there is a user-defined function BASECONVFP, but there is no function named "OTHER", so the result is this: Obs name fnflag 1 cos 1 2 propcase 1 3 baseconvfp 1 4 other 0

Tom

Why did you define the SCORE variables as CHARACTER? That is why you got a message like this in the log. NOTE: Character values have been converted to numeric values at the places given by: (Line):(Column). 162:9 163:11 164:11 165:11 If you have to keep them as character then add an INPUT() function call to avoid those messages: Example: if input(score(i),32.) <= 50 then grade(i) = 'C'; Why did you define the GRADE variables as NUMERIC? Define them as CHARACTER so they can hold values like 'C'.

Online Status	Online
Date Last Visited	9 hours ago