SAS is installed in /apps/sas/sas9.1
SAS has a number of options:
- -work /location : This is the location of your work area. It is needed if it is not defined in your SAS initialization files.
- -nodms : This stops SAS from using its GUI capability and goes into a text only mode.
- -filelocks none : This causes SAS to not use filelocking.
- -sysin file : Designate a file for SAS to load as its input.
To do a batch submission to SAS, you would use the -sysin command line option and write all of your SAS commands in a file. In this way you can submit jobs to the batch queue system to run your jobs on the rest of the cluster.
Sample Job Script
#!/bin/bash # #PBS -r n #PBS -N Ceci-Inside #PBS -o Ceci-Inside.out #PBS -m abe #PBS -M <EMAIL ADDRESS HERE> #PBS -e Ceci-Inside.err #PBS -l nodes=1:ppn=1 #PBS -l pmem=600mb #PBS -l walltime=00:15:00 EXE=/apps/sas/sas9.1/sas cd /scratch/ufhpc/camadorp $EXE -memsize 1024M -nodms -work `pwd` -filelocks none -sysin CECI-OUTSIDE.sas
Note the memsize option above. By default, if this option is not used, SAS will default to 64mb of memory usage.
- If the following error appears:
ERROR: A lock is not available for #C00002.CORE.CATALOG, lock held by another process. FATAL: Unable to initialize the options subsystem. ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. UNABLE TO INITIALIZE THE SAS KERNEL
You will need to use the -filelocks none option as described above when starting SAS.
ERROR: Library WORK does not exist. FATAL: Unable to initialize the options subsystem. ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. UNABLE TO INITIALIZE THE SAS KERNEL
You need to designate where your work area is with the -work LOCATION directive.
X11 connection rejected because of wrong authentication. Fatal I/O error The network connection has been lost. Traceback Traceback No Traceback Available No Traceback Available
You apparently do not have X11 access to the node, and you will have to use it through a console mode using the -nodms directive.
- If this is the case and you want X11 access to the node, connecting to the node with ssh -X should fix the problem for you. Remember that this has to pass through every node that you are connected through in the chain, so if you connect to the submission node first, that node must be connected with the -X option, then the node that you connect to do the actual interactive work must also be connected to in this fashion.