@Ms_Harvey wrote: SAS seems to have corrected itself!!  This error message is no longer appearing!! Thanks  So you either restarted SAS, or you submitted some more code that added the missing quote.   This is a common problem and sometimes it can be fixed by submitting something like this "magic" string. ;*';*";*/;run;quit; In a normal SAS session that would be interpreted as an empty statement followed by three very short comment statements and finally run and quit statements.   When you have unbalanced single quotes the single quote closes the open string.  If instead you had unbalanced double quotes the double quote closes the open sting. If instead you had an unbalanced block quote the star slash closes it. The run and quit statement should then close whatever proc or data step SAS was currently in the middle of. ... View more

The code you posted if TN_RES_Flag="Y" ; looks fine.  So you need to look EARLIER in the program to see where the quotes became unbalanced.  Or in previously submitted lines of code if you are running SAS interactively.   The issue is probably at least 260 bytes earlier in the program based on the warning message you got.  So it might even be in a previous step.   If you cannot balance the quotes then you will need to restart the SAS session.  If you are using SAS/Studio or Enterprise Guide to submit your SAS code there should be an option to restart the SAS session without logging out of SAS/Studio or Enterprise Guide.  If you are using SAS Display Manager then close SAS and restart it. ... View more

From that linked article it looks like you can get the name of the FILESET that is executing the batch job by using the environment variable named BATCHJOBDIR. %let batchjobdir = %sysget(BATCHJOBDIR); %let fileSet = %scan(&batchjobdir, -1, /); But I doubt that has anything to do with the name of the PROGRAM that is being run by the batch job.   Note: If you want to avoid getting a error if the environment variable does not exist then use logic like in this macro:  https://github.com/sasutils/macros/blob/master/qsysget.sas   ... View more

Can you explain WHY that works? ... View more

You cannot ADD strings.  You can concatenate them.   But why is the variable character if it is something that you want to do arithmetic on?  Did something go wrong with your creation of the original dataset?  Your starting point looks like a summary of some other dataset? Can you share the original dataset? Can you share the code that made that summary dataset?   It should be simple to change the those strings into numbers using the INPUT() function.  Since you seem to have two different numbers in the strings you can use SCAN() to separate them. num1 = input(scan(value,1,'()'),32.); num2 = input(scan(value,2,'()'),percent32.);   ... View more

Didn't the DESCENDING keyword on the CLASS statement work? It seems to work for me. data have; do id=1 to 2; do group=1 to 3; do time=1 to 2; row+1; contvar=rand('integer',1000); output; end; end; end; run; proc tabulate data=have format=6.1 nosep ; class group ; class time / descending; var contvar; table contvar*(n mean std nmiss),group*time; run; ... View more

PROC IMPORT reads from files, not from libraries.  If you don't want to include the actual filename in the PROC IMPORT code then use a FILENAME statement to create a FILEREF. filename pract "/home/u63717210/EPG1V2/practices/p102p01.sas/eu_sport_trade.xlsx"; proc import datafile=pract dbms=xlsx out=eu_sport_trade replace ; run; proc contents data=eu_sport_trade; run; If you want to have SAS make the workbook look like a library by using a LIBNAME statement with the XLSX engine then there is no need to use PROC IMPORT.  Instead if you know the name of the worksheet then you can just reference it directly. So if the sheet is named eu_sport_trade then just use that with the LIBREF that you created to reference the data. libname pract xlsx "/home/u63717210/EPG1V2/practices/p102p01.sas/eu_sport_trade.xlsx"; proc contents data=pract.eu_sport_trade; run; If you don't know what the sheets are named then you might try just copying all of the sheets into datasets in the WORK library. libname pract xlsx "/home/u63717210/EPG1V2/practices/p102p01.sas/eu_sport_trade.xlsx"; proc copy inlib=pract outlib=work; run;  After you see the names in the SAS log you will know what dataset name to use in your PROC CONTENTS code. ... View more

@Tecla1 wrote: Tnks for your kindly replay. If a certain condition is met (finding "ADDEBITI" or "POLIZZE" in a list of table name – `%if %sysfunc(find(&nome, ADDEBITI, i)) > 0 %then %do;`), I need to export the table to the same Excel file but to the "ADDEBITI" or "POLIZZE" sheet.   That does not help much since it is not clear where the list of table names is.   But it seems to me if you want to set the name of the SHEET in the XLSX workbook then you should either put it into a macro variable. ods excel options(sheet_name="&sheetname"); You could generate different sheet names based on some test you want to do.  So perhaps something like: %let sheetname=default_name; %if %sysfunc(findw(&out,addebiti,%str( ),i)) %then %do; %let sheetname=ADDEBITI; %end; ods excel options(sheet_name="&sheetname"); Make sure to open and close the workbook only once.  ods excel file="myfile.xslx"; %mymacro(sheetname=ADDEBITI); %mymacro(sheetname=SomethingElse); ods excel close;   ... View more

Can you clarify what you want to happen exactly? Do you want different PROC steps to generate different sheets? filename xlsx "myfile.xlsx"; ods excel file=xlsx; ods excel options(sheet_name="PROC FREQ"); proc freq data=sashelp.class; tables sex; run; ods excel options(sheet_name="proc print"); proc print data=sashelp.class; run; ods excel close; Note it will be faster to get a working example of the code you want to generate before trying to use a code generation tool, such as a SAS macro, to generate that code. ... View more

Note that CONNECTION=GLOBAL is really only useful if you need to make multiple connections to the same foreign database.  For example to make librefs that point to two different schemas in the same database.   But that is less needed now that you can use the CONNECT USING syntax of PROC SQL and the SCHEMA= dataset option in SAS code.   ... View more

@SwissC wrote: Not sure if you see the same but in my view of the page, the code box is not displaying correctly, I did honestly but each line of code on separate lines. That happens when you edit the text inside the code block in the normal editor window instead of the code box pop-up window.  Put the cursor inside the code box and push the icon to get the pop-up to appear and then close the pop-up and the line breaks should be fixed. ... View more

The code you shared does not (and should not) get any errors about something being longer than 8 characters.    Instead it shows that the file you tried to IMPORT from does not exist because you told SAS to look for it in the wrong place. ERROR: Physical file does not exist, /pbr/biconfig/940/Lev1/SASApp/pps/p102p01.sas/eu_sport_trade. Perhaps you tried to make a LIBREF using a name that was longer than 8 characters?  The libref you use in a LIBNAME statement has to be a valid SAS name between one an eight characters.  Its value does not have to match the name of the directory that it points to.  So if you want to make a libref pointing to that practices folder you could call it PRACTICE or FRED or SAM or any other valid SAS name (that is not already being used from some other libref. libname fred "/home/u63717210/EPG1V2/practices/"; proc import out=fred.myds ...   ... View more

No.  There is no magic formula to break summarized data into sub categories. You will need to go back to the original data and perform the actual counting that you want.  ... View more

Look very carefully at the PATTERN of the two path names you used: "/home/u63717210/EPG1V2/practices" "pps/p102p01.sas/eu_sport_trade.xlsx" What differences do you see: The first one starts with /, the root node of the Unix file system, and the second one does not.  That means that the operating system will treat the first one as an ABSOLUTE (or complete) path and the second one as a RELATIVE path.  When you use a RELATIVE pathname the operating system starts at the current working directory and begins evaluating the path.  So what file it is looking for depends on the setting of the current working directory.   ... View more

@NewUsrStat wrote: Sorry another question: since the rate is originally calculated N/D where N is not subtracted from D, is it correct to calculate CI where N is subtracted from D from a statistical point of view? The rate is number of events divided by the total number of trials.  Which you can write as :   RATE = (#Events) / (#Events + #Non-Events)   For SAS to calculate statistics you need the number of events and the number of non events.  It will figure out the total by just adding them up.   So if you only have the number of events and the total you can calculate the number of non events using simple subtraction.       ... View more