By current design, using STOP in the Task Manager within SAS Enterprise Guide is supposed to stop execution on the SAS server after a step boundary has been reached and should also allow you to continue working from the point in which the code was stopped. STOP will stop execution after a step boundary if the SAS server is your Local machine. However, in some cases rerunning the code will not start from the point the code was stopped. Additionally, STOP does not stop execution after a step boundary if the code being run is within a macro and the SAS server is a remote machine.

In most cases, based on the current design, it is best to use End SAS in the Task Manager instead of STOP. Using End SAS will kill your sas.exe session running on the SAS server, which means temporary data that was generated during your SAS connection that is needed by your project will need to be recreated by rerunning the code in your project. Additionally, if your task or code accessed a non-SAS database such as ORACLE, then processing will very likely continue to run on the database although the sas.exe session has ended.

The goal with a future version of SAS Enterprise Guide and SAS^® software is to improve the functionality of STOP so that End SAS will not be required in most cases.

Operating System and Release Information