CALL SLEEP puts the
DATA step in which it is invoked into a nonactive wait state, using
no CPU time and performing no input or output. If you are running
multiple SAS tasks, each task can execute CALL SLEEP independently
without affecting the other tasks.
Note:
-
In batch mode, extended sleep periods
can trigger automatic host session termination based on time-out values
set at your site. Contact your host system administrator as necessary
to determine the time-out values used at your site.
-
If you are running the asynchronous
RSUBMIT statement in a
SAS/CONNECT session, specifying CALL SLEEP
for a DATA step affects only that DATA step. It does not affect any
other SAS tasks that you are running on the remote system.