@sathya66 I've tried to use use this %try_lock macro in the past but even after tweaking it got never to a fool-proof solution that only relies on SAS code. In a Unix/Linux environment you could use flock for such purposes.    With SAS what always worked for me both under Windows and Unix/Linux is libname option filelockwait. If you don't need to wait for more than 10 minutes then that's what I'd be going for.    FILELOCKWAIT=n specifies the number of seconds SAS waits for a locked file to become available to another process. If the locked file is released before the number of seconds specified by n, then SAS locks the file for the current process and continues. If the file is still locked when the number of seconds has been reached, then SAS writes a locked-file error to the log and the DATA step fails. The valid values range from 0 to 600. The default value is 0. ... View more

Can you share a cut-down version of your Excel that shows this behaviour? Ideally an Excel with only one sheet and one row of data and the SAS code to read it that then returns the undesired result. ... View more

@Ronein wrote: I just want to use the output data set and I dont need the print on screen Just repeating what @Tom already shared:   Prevent the printing of what exactly? If you just want to prevent the frequencies from printing just use the normal PROC FREQ options for that, no need to delve into how ODS works. tables _all_ / noprint; ... View more

@odahviing I simply copy/pasted your question as-is into Copilot. I've only "browsed" through the answer but it looks right to me and provides certainly much more detail than I could - and certainly explains things in much more detail than I could.   You're on the right track! The behaviour you're observing is indeed related to how the Program Data Vector (PDV) is managed in SAS when using the SET statement. Here's a step-by-step explanation: Creating c1 , c2 , and c3 : c1 is created by copying all observations from sashelp.class . c2 is created by copying the first 3 observations from c1 and keeping only the name variable. c3 is created by copying the first 3 observations from c1 and keeping only the age variable. Creating c_out : The PUT statement outputs the current values of all variables in the PDV. The first SET statement reads from c2 and c3 . When it reads from c2 , it initializes the name variable and sets age to missing. When it reads from c3 , it initializes the age variable and sets name to missing. The second SET statement reads from c3 and c2 . When it reads from c3 , it initializes the age variable and sets name to missing. When it reads from c2 , it initializes the name variable and sets age to missing. The key point is that each SET statement reinitializes the PDV, setting variables not in the current dataset to missing. This is why you see missing values for name in the first observation and age in the fourth observation. Here's a simplified breakdown of the c_out dataset creation: First Observation: SET c2 c3 : Reads from c2 , initializes name , sets age to missing. SET c3 c2 : Reads from c3 , initializes age , sets name to missing. Second Observation: SET c2 c3 : Reads from c2 , initializes name , sets age to missing. SET c3 c2 : Reads from c2 , initializes name , sets age to missing. Third Observation: SET c2 c3 : Reads from c3 , initializes age , sets name to missing. SET c3 c2 : Reads from c3 , initializes age , sets name to missing. Fourth Observation: SET c2 c3 : Reads from c3 , initializes age , sets name to missing. SET c3 c2 : Reads from c2 , initializes name , sets age to missing. I hope this clarifies the behavior you're seeing! If you have any more questions or need further explanation, feel free to ask. ... View more

@sathya66 wrote: Thanks for this . how can we use the same password in AUTH domains? can we use encrypted passwords in Authdomains (pwencode) I believe using proc pwencode to encode your password and then use this encoded pw for the user in SAS metadata that connects to the DB via the authdomain definition should work.  Not sure if you can use anything above method SAS002. PROC PWENCODE Why don't you just give it a try? ... View more

@xyan20  There is also a SAS VS Code extension that can surface SAS Tables. SAS Extension for Visual Studio Code Given what's already available for free published by SAS, I'm not so sure why I would even try a paid for alternative. And even if interested I'd never download and install software from a site where I'm not 100% that I can trust. For me such software would need to be published for download on a well known reputable site.  ... View more

The approach Tom proposes is not that hard to implement. Please provide usable sample data if you're after code (=instead of screenshots two data steps that create the sample data).    ... View more

@Kurt_Bremser  That makes sense and is certainly a valid use case. However.... afaik there is no equivalent for metadata-bound libraries under SAS Viya and for this reason alone I wouldn't use it anymore for any new implementation. ... View more

I believe for VA reports row and column level security is implemented but in the moment where a user can access the actual physical data via SAS the only way I know of to implement column level security is via metadata secured libraries - and I'm not a big fan of these.    Ideally store your data in a database. Most DB's provide much better options for such security implementations via views where the user can execute the view without the need of direct access to the underlying table.    Potentially (haven't tried, just an idea) such column level security could also get implemented via a data step view where the secured columns are stored in a separate table with this table secured on OS level. ... View more

Without really knowing my first assumption is insufficient memory. Not sure if there is a way that can get you more memory for your session. Something to ask your SAS admin.  And as a test: Run a python script that does nothing else than reading the data into python. If this works then you could investigate where your current script consumes additional memory and if there are options to reduce its hunger. ... View more

@terryeastman  I've used Proc Export to create a .xlsx (not .xls).  I can replicate what you describe and for me it happens both in a Linux and Windows environment using SAS EG. I don't believe that it has anything to do with "PC SAS" or SAS Studio but with the version of SAS and potentially Microsoft Excel components (if SAS uses them at all for creation of the xlsx) where you execute your code.    If I look into the cell value itself then it's NULL (not a single blank) but function isnull(<cell>) returns FALSE. Once I click into the cell and then into the pane where I would type formulas and then into another cell the value changes to TRUE.   In my test case if I compare the xml of the sheet before and after these actions then I can see that it changed - the highlighted bit got removed. No clue what this means. Using Shift + F9 to recalculate all formulas in the active sheet had no impact. The result of isnull(<cell>) remains FALSE even though there is not even a blank in the cell. What did return the expected result what using formula LEN(<cell>)=0   I suggest you take this up with SAS Tech Support. Don't expect a speedy resolution though as it's likely something in the bowels of SAS or Microsoft.   In the meantime the workaround using LEN(<cell>)=0 instead of isnull(<cell>) should get you going.   From what I understand the "fake space" is not an actual blank but the observed issue is due to the generated xml that makes the isnull() function return the wrong result.      ... View more

If you're using a SAS Server version then one person could also run multiple sessions.  If you've got SAS/Connect licensed then you can spawn multiple sessions from a master SAS session - like each session with different parameter values for your macro. Or if xcmd is set then you could also generate and execute batch commands for running multiple sessions in parallel and in batch.   ... View more