I am using SAS OnDemand for Academics and my code is generating these errors as attached in the photos. The code is working perfectly with SAS university edition. Any suggestions! Thanks
The dataset you inspect in your WORK is named IMPORT, not HALE.
The right side of the screen shows a task definition for importing a file to a dataset, not the dataset itself. You need to execute that task to create the dataset in your current session.
Pretty clear, the data sets are not present in the work library that On demand uses. Did you upload the data sets to the server or read a file to create them? On Demand is cloud based and all the data must reside on the server.
How could I reside the data on the server? This is screenshot shows that data in the work library
The dataset you inspect in your WORK is named IMPORT, not HALE.
The right side of the screen shows a task definition for importing a file to a dataset, not the dataset itself. You need to execute that task to create the dataset in your current session.
Thank you very much @KurtBremser. I was able to create hale in the work library. but then I got different errors as shown in the screenshot attached
Please post logs by copy/pasting the text into a window opened with the </> button. It is much easier for you to do and easier for us to read.
Your dataset was imported with
options validvarname=any;
so the blanks in the variable names were kept.
Either use name literals like
'Clearsky GHI'n
or reimport the data with
options validvarname=v7;
so that blanks in variable names are replaced with underlines during the import.
Very Very appreciated! It works great now. thank you very much for the help
You have two datasets absent from the work library on the SODA server, as @ballardw noted.
But the second dataset (work.spearman) is missing because the first (work.hale) is missing, therefore preventing proc corr from creating work.spearman from work.hale. You appear to have two symptoms from one problem.
yes agreed. How to solve the first issue
The WORK library is initialized with the start of each SAS session and removed when the session terminates; since the name of the directory is tied to the process number of the SAS process, you cannot re-use it (not with simple means).
You may have run the code that creates WORK.HALE earlier and were then logged out of ODA because of inactivity. You need to rerun that code.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Follow along as SAS technical trainer Dominique Weatherspoon expertly answers all your questions about SAS Libraries.
Find more tutorials on the SAS Users YouTube channel.