It's clear from that screenshot that your are using SAS On Demand for Academics.
Please note that this is a learning tool, not a production environment. I looked at the FAQ: https://support.sas.com/ondemand/caq_new.html
While I don't see an answer there about scheduled jobs, I would agree with others, it is unlikely that this is supported. See for example other similar limitations that are mentioned in the FAQ:
Do SAS sessions expire?
SAS sessions are established when you connect to our hosted SAS servers from the SAS software application that you are using. If a SAS session has been inactive for three hours, it will expire. All SAS sessions will expire after six hours. These limitations are in place in order to conserve computing resources. Typical educational usage of the system often requires sessions that are much shorter than the expiration periods noted.
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.
Are there limits on what I can do in my SAS sessions?
Yes. Since SAS ® OnDemand for Academics supports a large population of SAS learners, we focus considerable attention on ensuring the site is available and reliable to all users. To help meet this goal, we rely on our users to also be mindful of resources consumed by their jobs, and the resulting impact on their fellow users as well as the site. As a safeguard, resource consumption by user sessions is continuously monitored. This includes, for instance, the number of user processes, duration of the session, processing time consumed, process memory consumed, and the number of bytes transferred between files or network resources. Sessions found to be consuming excessive resources are subject to termination without notice. This practice is necessary to maintain the fair and equal access to the site for all users. SAS is not responsible for any data or content that is lost due to such actions. Chronic offenders may also be subject to further action.
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.
... View more
