This is what I get in SAS:ĮRROR: Unrecognized SAS option name ÛNODMS.ĮRROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.ĮRROR: Unable to initialize the SAS kernel.When compiling the same project from different place on the computer, we get different binaries.ĭigging in the. log ('type C:\Users\.\OneDrive') ûnodmsĪnd there is a problem with the nodms option. \!USyd Projects\Google "Trends\Data_management\Cov\test.sas') sysin ('type C:\Users\.\OneDrive" - The University. \.\Develop Run and Debug your SAS Programs in UltraEdit_files\autoexec.sas" autoexec "c:\Users\.\OneDrive - The University. CONFIG "c:\Program Files\SASHome\SASFoundation\9.4\sasv9.cfg" "c:\Program Files\SASHome\SASFoundation\9.4\sas.exe" \.\Develop Run and Debug your SAS Programs in UltraEdit_files> It seems as if the *.sas program file is now fed through correctly to SAS, but still not the log file.Ĭ:\Users\.\OneDrive - The University. The important part of the *.bat file now looks like this: I also tried posting on the UltraEdit forums, but so far with no success. The first was spaces in the file path, which I partly resolved, but not completely. I tried getting that original tutorial to work, but keep running into problems.
I also see some attempts in the SAS forums, but none with satisfactory solutions: See, for example, this post from a SAS staffer (a decade old, unfortunately). I have "heard rumours" that it might be possible to send the program through to SAS from within UltraEdit. Are there any other UltraEdit & SAS users out there who might be able to help with (or benefit from) this? I use UltraEdit for the bulk of my coding.
0 kommentar(er)
