Usage Note 18836: Scheduled flow in LSF will not start if a file dependency exists
If a job is scheduled from SAS Management Console with a file
dependency, the job may not start if the userid which the job is
scheduled to 'RunAs' does not have read permissions on the file or
access to the parent directories in the file's pathname.
For example, if file /u/scheduler/dependent/filedir/depFile_f is used to
trigger job RunFirst as user AR001, then user AR001 (or the group that
AR001 is a member of) must have read permissions on depFile_f and must
have read and execute permissions on all directories in the
/u/scheduler/dependent/filedir path.
If the user cannot 'see' into the directories, then the existence of the
file cannot be determined, and a job is not triggered.
Operating System and Release Information
| SAS System | Platform JobScheduler for SAS (UNIX) | 64-bit Enabled Solaris | 5.31 | | 9.1 TS1M3 SP4 | |
| Solaris for x64 | 5.31 | | 9.1 TS1M3 SP4 | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.31 | | 9.1 TS1M3 SP4 | |
| 64-bit Enabled AIX | 5.31 | | 9.1 TS1M3 SP4 | |
| HP-UX IPF | 5.31 | | 9.1 TS1M3 SP4 | |
| Linux on Itanium | 5.31 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2007-05-02 18:00:35 |
| Date Created: | 2006-10-24 15:31:21 |
