SAS Fraud Management jobs fail with a message similar to the following in the job shell logfile:
Did not execute submit3_4268512.sh.
This job failure can occur if the WORK directory on the SAS Fraud Management batch server is mounted with no Execute permission.
See the !SASROOT/sasv9.cfg file to determine whether the file system uses the WORK library. (Generally, the /tmp file system is configured as the WORK library.)
Then, submit the following df UNIX command to determine the mount of the /tmp file system.
$ df /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 16373760 48856 16324904 1% /tmp
$
You can also use the following UNIX command to check if the /tmp mount on the SAS Fraud Management batch server contains the Execute permission. Note: If you use a different file system or mount as the WORK library, then complete the same checks for that file system or mount used as the WORK library.
mount | grep /tmp
An output similar to the following occurs when you submit the above command:
/dev/sda3 on /tmp type xfs (rw,noexec,relatime,attr2,inode64,noquota)
If noexec is displayed for /tmp, then the directory does not have the Execute permission.
Note that the noexec parameter is defined as "Do not permit direct execution of any binaries on the mounted filesystem."
You can also check by creating a simple .sh file with the SAS Fraud Management sasomr user in the /tmp file system on the SAS Fraud Management batch server. Give the test shell script the Execute permission (chmod +x) and run it to see whether the /tmp file system contains the Execute permission.
Note: You can put any UNIX command in this test script. For example, echo test, pwd, date, and so on.
You will need to work with your UNIX administrator to grant Execute permission to the /tmp file system on the SAS Fraud Management batch server.
If you want to use a different file system or mount as the WORK library, then, see SAS Note 43988, "How to change the WORK library path for your SAS® Business Intelligence Servers."