You tell the truth. At this stage (whatever GPT-3.5 or GPT-4), it is definitely not feasible to generate SAS code using chatgpt. I have actually tested using chatgpt to help me with SAS programming, and the results have been disappointing. But I still agree that AI is the future. So I try to test different AI tools to help me write code, in order to be ready to embrace AI one day in the future. Although many tools are based on GPT model (or use ChatGPT API), i still think they have differences (because it will be fine-tuned for different areas). And GPT series will be updated to higher performance (GPT-5, GPT-6, etc.). But, unfortunately, when I try to use GitHub Copilot to generate SAS code on VScode, I fail to install the SAS extension at the first step.....LOL ... View more

Hi, Koen. I agree with you. To be honest,I don't believe that GitHub Copilot can help SAS coding too much. The GitHub Copilot is for IDEs (e.g. VScode), and the most popular languages should be python, java ,etc. Since SAS is not a mainstream language for development task, even we can use GitHub Copilot to generate SAS code, the performance would be bad. But AI may be the 'future', right? And, the GitHub Copilot X will be released later, which based on GPT-4. Not like ChatGPT (can do anything but not domain specific), GitHub Copilot focuses on programming. So, these days, I just want to try if I can use GitHub Copilot to generate SAS code on VScode. I know SAS has extension in VScode, but I fail to install and use it to test how GitHub Copilot could help us do SAS coding. ... View more

But I find that a new problem has arisen: if %INCLUDE is used to call a ".sas" file, the source code of the MACROs can be easily discovered by others. Using a compiled catalog eliminates this risk of leakage. How can this problem be solved?   Additionally, if the author is able to recompile the MACROs on SAS WinServer as a new encrypted catalog  (rather than his own PC), will there still be a problem with calling it on SASEG? ... View more

Oh, I just forgot to say: Thanks for your comment ：） ... View more

Make sense! It should work! I will try %include ".sas" to call macros later. ... View more

Hey Kurt, i've sent a detailed info to Tom, maybe you see that. I'm not sure if "%SYSGET" is included in macro's source code, because the author isn't me. But this issue seems related to "environment variable". ... View more

Hey Tom, thanks for your comment, and I need to say I am not quite familiar with SAS. I guess now I could explain it to you better now:   So, this is the SAS MACRO FILE I have metioned before. I find it is the "catalog" type (in the "property"). I guess this should be the thing you said "stored compiled macro", and it do have many macros inside:   And I'm sure that this "stored compiled macro" was coded and created by author in SAS 9.4 with his own laptop. And, if others want to use this macro, they just download this sas7bcat file into their own laptop. By using SAS 9.4 in their own laptop, they can easily call macros like this:   At before, our group members can only use SAS 9.4 in their own laptop. These days, we bought a Windows Server (work station?) and built a SAS server system in it, and group members use SASEG 8.3 im their own PC (remotely connected to the server) So, as before, we still want to use this "stored compiled macro".  And I just put this "stored compiled macro" (sasmacr.sas7bcat) into the Windows Server, and the directory is "D:\SASMacro". I guess when a group member use SASEG 8.3, he can also easily call macros in this "stored compiled macro" (remotely though). But this time, it cannot work, and the code I run in the SASEG 8.3 like this:     (the warning is as below, warning 2/3 don't matter too much) Commonly, after running this %sumtest, there should be an output dataset with some numbers. But this time, with this warning, there is no number in the dataset. Weird! So I'm not sure if this is as what you said "use a stored compiled macro on a version of SAS running on Windows Server you probably need to have created the stored compiled macro on that machine and not be trying to access a verison compiled on a different version of SAS."   Besides, does this means if I still want to use this "stored compiled macro" (sasmacr.sas7bcat) in our remote SAS system, I need to let macro author re-compile his macros in the SAS 9.4 (Windows Server Version)?      ... View more

Yeah, my EG has already connected with SAS WinServer, and I can use it normally. But, Actually, I am not the author of this MACRO FILE, so i cannot get the source code. The only thing I know is that, when this MACRO FILE is stored in everyone's own PC (rather than Server), macros in this FILE can be normally used in personal SAS 9.4 without problem. By the way, I have tested like this: created a very "simple" MACRO stored in WinServer, and then called it successfully in my SASEG. The code below is my test macro: ---------------------------------------- libname test "D:\test_macro"; options mstored sasmstore=test; %macro text_output()/store source; %put "Welcome to use SAS MACRO!"; %mend; ------------------------------------------------- So, i am not sure if this MACRO FILE can only be used in SAS9.4, rather than stored in Server and then used in SASEG. ... View more