When you schedule a SAS job using an Operating System Services scheduler under the Schedule Manager plug-in in the SAS Management Console for a UNIX server, you might receive error messages such as the following:

   Scheduling of '[your-job-name]' failed
   ('Submission of generated code to server failed.  ERROR:
   One or more flows were not successfully scheduled.
   ERROR: at: you are not authorized to use at.  Sorry.
   ERROR: /usr/bin/at -f

   '[path-to-job-script.sh]' now').

This problem occurs if you do not have authority to use the UNIX at command. Your UNIX system administrator needs to add your user name to the at.allow file and ensure that your user name is not in the at.deny file. Both of these files are under the /var/adm/cron directory.

This issue can also occur if the at daemon is not running. You can verify that this daemon is running by submitting the following command on the UNIX server:

If the only line that returns is the grep command itself, the at daemon is not running, and your UNIX administrator has to start it.

There also are circumstances where, even with all of the above issues correct and working, you might still receive an error message that says you are not authorized to use the at command, or something similar to this. This might be due to the /usr/bin/at command file not being setuid to root so that the file permissions are something like this: -rwxr-xr-x.

You can correct this by logging on to the UNIX system as root and running this command: