With a valid SAS Profile, to sign up, visit welcome.oda.sas.com and sign in to begin the registration process.
Setting up an account for SAS OnDemand for Academics is a two-step process. This offering is only available to users who have a SAS Profile. Hence, the first step is to create a SAS Profile unless you already have one. Creating a SAS Profile is free. For convenience, a link is provided to the SAS Profile site from our Sign In page.
Once your SAS Profile is ready to use, sign in to SAS OnDemand for Academics through welcome.oda.sas.com to step through your registration. Please select your desired home region. See the in-page help information to guide that decision if you are unsure which region to select. This process normally takes 5-10 minutes, but may take longer in some cases. You will be notified by e-mail when the process completes and you are ready to begin using the offering.
To identify the LIBNAME or FILENAME statement for your course, do the following:
See Step-by-Step Guides for more information.
Additionally, instructors can register courses and select other software applications during the registration process. Users can be invited to register for these courses. Once either of these activities occur, links for the software associated with these courses will be available on a user's dashboard.
See Step-by-Step Guides for more information.
If you forget your SAS Profile password or are concerned about whether it meets expected password strength criteria, see What should I do if I forget my password?
SAS recommends saving your work and exiting the SAS software application that you are using after completing your work. If you have an active session that is approaching six hours and you need to continue, save your work and exit the software. You can then start a new SAS session.
SAS is not responsible for any data or content that is lost due to session expiration.
This policy may be particularly notable to researchers and instructors for advanced courses who wish to use resource-intensive SAS code. While such users are welcome to use the site, such intensive workloads are not appropriate for a widely shared learning environment. Other options, such as obtaining a SAS license for a private environment, should be pursued instead. However, these users may still use the site for their less intensive workloads.
We also recommend avoiding large long-running jobs where possible. Such jobs tend to eventually report high resource usage, and hence are more likely to be terminated. In addition, these are more likely to be terminated due to the duration of the session. Sessions are subject to termination after 6 hours, and after 3 hours of inactivity.
In the event your session is terminated due to this policy, a notice including the time of the action should get logged to the special path ~/my_system_notices/termination within your home directory. This path will not exist otherwise. If it does, you can open the "termination" file as a text file within SAS Studio to view the details.
After the software is installed on the lab machines, only registered users can sign in with their SAS® OnDemand for Academics credentials.
If you must have students register together during your course, then we suggest you stagger the registrations (a few students every five minutes) to reduce the risk of complications.
Also be aware that we naturally experience higher numbers of requests during certain times of the school year, such as the beginning of semesters. Allow for more time to get started during these periods.
The process of logging in is similarly sensitive to the number of requests. Consequently, we recommend staggering logins in situations where all students will be using the site simultaneously.
See Forgot Password using the SAS Profile for password management.
UTF-8 is the only SAS session encoding that is supported by SAS OnDemand for Academics. Do not attempt to override the default UTF-8 encoding. If your data encoding is non-UTF-8, the SAS software will attempt to convert the data to UTF-8. Be aware this conversion can impact your performance while using SAS OnDemand for Academics. It is strongly advised that you convert your data to the appropriate UTF-8 encoding while using SAS OnDemand for Academics.
Generally speaking, this should not be an issue. We do not actively block domains. There are several domains that we are aware of that will reject these emails (including registration emails) if you have an email address associated with them. Often this requires that you work with your provider to add an exception for email originating from @sas.com. All email sent from SAS OnDemand for Academics will originate from @sas.com. Your provider should have instructions on their web site for this process or you can request help from their technical support team. SAS Technical Support cannot help in this case. We are currently aware that the following domains are affected.
There may be others but we have noticed a significant number of bounces from these particular domains.
If you experience issues, you should use a different email address not associated with the affected domain. If you cannot provide another email address, you will need to let your instructor know so they can work with your school's IT department to allow access for @sas.com emails.
Per the license agreement, you are solely responsible for the data or Content uploaded or accessed and for ensuring such data or Content is stored appropriately on your computer. SAS is not responsible for the accuracy of the data or Content, your use of the data or Content, or for any loss of data or Content. For the same reason, it is always a best practice to maintain downloaded backup copies of any important files that you intend to store on the ODA servers. The copies on the ODA servers should only be treated as temporary working copies.
The my_content and my_courses subdirectories are from the original site scheme. These have been phased out as of Summer 2020 and will no longer be created. However, the links that already exist will not be removed to avoid impact to existing references within user code. When present, the my_content path links your home directory to your course data directory. Similarly, your my_courses links your home directory to the course data directories associated with your enrolled courses. In this case, there are multiple links potentially and so each instructor's course data directory will have a separate link under my_courses named for that instructor.
The my_shared_file_links subdirectory is the current scheme for providing the same links in a more uniform manner. Under this scheme, you will receive a link to any associated course data directory (including your own) as needed. The individual links still use the User IDs for the associated users (including your own), as with the older my_courses scheme. This ensures uniform access using the same file paths for both students and instructors. For example, one would access the shared content for the instructor jsmith0 through the path ~/my_shared_file_links/jsmith0. You cannot modify the direct contents within the my_shared_file_links subdirectory since these links are maintained for you automatically. Additionally, these links will still only permit read access to any course data directories other than your own.
See also
Alternatively, if you want a precise value instead of a percentage, then you can install and run a tool:
/courses/support
and then click Save.
See also
User <username> has insufficient permissions to create /home/<username>/.. Contact your system administrator to resolve.
or
ERROR: An I/O error has occurred on file.
You will also see a message indicating you are over your quota when you access your dashboard in SAS OnDemand for Academics.
To correct this issue, you must delete personal SAS files or data files that you no longer need:
Sign in through welcome.oda.sas.com to view the meter(s) of your personal quota usage. You might need to delete more files in order to create enough space to run SAS programs, create new projects or files, or upload additional data.
If you exceed your data storage quota,
this self-service option will appear in your dashboard under the Quotas section.
In some cases, being over quota can prevent SAS Studio from launching,
thus limiting the ability to remove content from your home directory.
This utility will assist by removing the largest file in your home directory regardless of file type.
Since this is a forced removal and the largest file will not be recoverable,
it is recommended to first attempt to remove files manually using SAS Studio.
After running the utility a message will show you the location, file name, and size of the file that was removed.
See also
All users have up to 5 GB of storage for personal data files that they upload as well as for SAS programs created with SAS Studio. If you are a part of a course that uses SAS Enterprise Miner or SAS Forecast Server, then your project files are automatically stored on the SAS Server and count against your personal 5 GB storage quota.
The Upload feature within SAS Studio is used to perform file uploads. For more information about uploading course data or SAS program files, refer to the Step-by-Step Guides.
If you would like more information, please see the above link for system requirements.
If you need help determining your home region, see "How do I know which region I am using?" in the Regions Questions section.
https://welcome.oda.sas.com/sas-environment.xml
After the client is installed, the user will select their "Home Region" during sign in. See "How do I know which region I am using?" in the Regions Questions section.
Note: Some versions of Apple Safari will not allow you to choose files to load data. You must drag and drop the data to upload in SAS Studio. Please see the following SAS Note for more information and steps.
This setting may not function when using certain versions of Microsoft Internet Explorer or Apple Safari. Spaces are often used instead of tab characters in these Web browsers. If this is the case, then select the Substitute spaces for tabs check box within the Editor preferences.
Apple Safari prompts you only when you sign out. If you exit the browser, close the browser tab, refresh the browser page, or navigate to a different browser page, Safari will not prompt you, and your unsaved changes will be lost.
Additionally, you can avoid refreshing your Web browser. This will result in a loss of any work that has not been saved. Most Web browsers provide a warning to let you know that your work will be lost if you choose to proceed with a page refresh/reload.
To resolve the file format compatibility issues between Windows, Macintosh, and Unix, you will need to include a FILENAME statement that uses the TERMSTR option.
If you are using a file created with the Microsoft Windows operating system, use the TERMSTR=CRLF option, such as in the following example:
FILENAME cars "~/Projects/data/cars.txt"
TERMSTR=CRLF;
If you are using a file created with the Macintosh operating system, use the TERMSTR=CR option, such as in the following example:
FILENAME cars "~/Projects/data/cars.txt"
TERMSTR=CR;
The file names and paths listed above are for example purposes only; your values might vary. For more information about SAS syntax, refer to SAS Studio Documentation.
Alternatively, if the file is large, your Web browser could be timing out or your wireless connection might not be ideal. Consider trying a smaller file size or verify that your wireless network is working properly.
For more information, see Working with SASPy, including Jupyter Notebook, or click on the link available in the ODA interface.
Java version 1.8.0_162 or higher, Python 3.3 or higher, and SASPy 3.3.4 or higher (using the latest version is recommended).
For more information on SASPy, please see SASPy on sassoftware.github and the installation and configuration instructions.
While SAS OnDemand for Academics is presented as a single web site, the site actually consists of multiple instances of SAS distributed around the world. This is necessary to ensure that every user will receive reasonable performance regardless of his or her geographic location. The location of each instance is referred to as an ODA region.
While some parts of ODA are shared across regions, other parts are limited to a single region due to technical restrictions. Most notably, file content (both home and course files) usually only exists in the region associated with each user. Similarly, metadata made by applications, such as project or library definitions, is created only in the region being used at the time.
Your home region is the region that your account has been configured to use. When you first register an ODA account, the region that performs that registration automatically becomes your home region and is the region that you are expected to use consistently. Due to this, it is important that the region used during account registration reflect the best choice for your typical location. Users should not choose a home region based on temporary locations like a training room or lab unless the account will be exclusively used from that location.
Currently, the home region for an account cannot be changed after the initial registration. Several situations that may motivate this question are discussed in later entries below. If your own situation is not covered by the information provided here, then technical support can be contacted for further assistance if needed.
No. This would still be changing your home region (just temporarily), and hence the answer to the previous question still applies. When traveling, you should continue to use your normal home region.
After signing in through welcome.oda.sas.com, the home region is displayed within the regional pages. All regional web pages report the region name in the upper right section of the page header, beside your user information.
In most cases, a course instructor and all enrolled students will be from the same region naturally due to residing in the same geographic location. In that case, regions require no special consideration during course planning. However, courses involving multiple regions can arise from other situations including:
As the hosted applications are generally configured for individual rather than collaborative use, file access is usually the main issue for students from other regions. In particular, these students will not be able to access any shared course files provided by the instructor since that shared directory naturally only exists within the instructor's region.
For cases where the instructor's course data directory is not used to share content with students, the concern can be ignored. Outside of practical considerations like the availability of the region and timing of its maintenance periods, all students should have a similar experience. Such situations typically involve enrolled users receiving course materials directly from the instructor by other means (email, file sharing site, etc.) and then individually uploading the files into their home directories as needed for the course work. Some instructors prefer to embed course data into their example SAS code by providing data steps that load the data through a datalines statement. Regardless, the course definition in this case mainly exists to manage the enrollments and access to needed applications, neither of which are impacted by using multiple regions.
For cases where the instructor's course data directory is used to share content with students, that instructor can request through technical support that those shared files be copied to the other regions being used by those non-local students. Copying files in this way is a manual process that only copies the state of the files at the time of the request. In addition, the time needed to perform the request will vary. Additional requests will also be needed if the primary copies of the files in the instructor's region are later changed. Hence, a best practice in this situation is to finalize the course data content and request this copy well before the related coursework is scheduled to begin. Delaying the request risks delays that may impact the course due to the material being unavailable in the remote regions. If you are an instructor and need to make such a request, please provide the following information to technical support:
When handling situations where a course might involve multiple regions, communication and planning are the key factors. To avoid late discovery of issues, the following practices are recommended:
Support for course-based shared environments ended on May 15, 2018. Shared environments existed only in the course instructors' home regions, and provided no means of accommodating students from other regions. Course instructors also could not fully manage these environments as they needed to. As there was no way to correct the various problems identified over time, a different approach was needed.
With the newer personal environment option, each user authorized to use Forecast Studio is granted the ability to create/destroy a single forecasting environment for personal use. The environment files reside under the special my_forecast_environment directory in that user's home directory and the environment is labeled Personal Environment: account-name. This environment is not visible or accessible to any other user making it a private workspace.
The Manage your personal environment link can be found within the Forecast Studio entry under Applications on the Dashboard page. Clicking on this link will take you to the management page, which will report whether your personal environment currently exists. That page will then also present either the Create or Delete action as appropriate.
Note that deleting the environment will permanently remove all content and configuration associated with it, including files. The environment can then be created again, but no prior content or other customizations will be restored. Instead, the new environment is created with the default configuration and no projects. Hence, deleting and re-creating an environment is a quick way to reset the environment back to its original starting state.
This message means that your personal environment has not been created yet. See the earlier entry on managing this environment for details on how to create it.
Please see the SAS Enterprise Miner Questions for the proper URL to provide during lab installation.