@Kurt_Bremser's first reply is spot-on - the best way to schedule a SAS job to run is to use the scheduling capabilities of the machine where SAS actually runs (either locally for SAS Studio Single User or on the server where SAS is installed for SAS Studio Basic or Mid-Tier). Remember that SAS Studio is simply a new interface to the SAS system, and code submitted in SAS Studio still runs in a SAS process on the operating system in the same way that code submitted through the SAS windowing environment / Enhanced Editor runs.
Be aware that the "batch mode" in SAS Studio 3.5 referenced in the link you posted has been renamed to background submit in 3.6 and later versions because the job doesn't really running in batch mode. The job actually runs in the background - meaning you can continue to work in SAS Studio while the job runs rather than having to wait for the job to complete.
See this SAS Global Forum paper for more information about the feature:
Submitting Code in the Background Using SAS® Studio
... View more