Difference between revisions of "SAS"

From UFRC
Jump to navigation Jump to search
m (Text replacement - "#uppercase" to "uc")
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Location==
+
__NOTOC__
SAS is installed in /apps/sas
+
__NOEDITSECTION__
 +
[[Category:Software]][[Category:Statistics]]
 +
<!-- ########  Template Configuration ######## -->
 +
{|
 +
<!--Main settings - REQUIRED-->
 +
|{{#vardefine:app|sas}}
 +
|{{#vardefine:url|http://www.sas.com/}}
 +
|{{#vardefine:exe|1}} <!--Present manual instructions for running the software -->
 +
|{{#vardefine:conf|}} <!--Enable config wiki page link - {{#vardefine:conf|1}} = ON/conf|}} = OFF-->
 +
|{{#vardefine:pbs|}} <!--Enable PBS script wiki page link-->
 +
|{{#vardefine:policy|}} <!--Enable policy section -->
 +
|{{#vardefine:testing|}} <!--Enable performance testing/profiling section -->
 +
|{{#vardefine:faq|}} <!--Enable FAQ section -->
 +
|{{#vardefine:citation|}} <!--Enable Reference/Citation section -->
 +
|}
 +
<!-- ########  Template Body ######## -->
 +
<!--Description-->
 +
{{#if: {{#var: url}}|
 +
{{App_Description|app={{#var:app}}|url={{#var:url}}|name={{#var:app}}}}|}}
  
There are currently three different versions installed:
+
SAS is a commercial integrated system for statistical analysis, data mining, and graphics as well as many enterprise oriented additional features. SAS cost and the breadth of SAS features means that both a significant monetary investment and a substantial time investment are required to master it. [http://support.sas.com/documentation/onlinedoc/stat/index.html#stat93 SAS 9.3 Documentation] is vast. For research purposes the [http://support.sas.com/documentation/cdl/en/statug/63962/HTML/default/viewer.htm#titlepage.htm SAS 9.3 User's Guide] is a thorough reference for the functions and procedures you may need to do the statistical analysis using SAS.
 
+
<!--Modules-->
SAS 9.1
+
==Required Modules==
SAS 9.2
+
[[Modules|modules documentation]]
SAS 9.3
+
===Serial===
 
+
*{{#var:app}}
==Commands==
+
==System Variables==
 +
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory
 +
<!--Additional-->
 +
{{#if: {{#var: exe}}|==Additional Information==
 +
===Commands===
 
SAS has a number of options:
 
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.
 
* -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.
+
* -filelocks fail : This causes SAS to stop and print out an error when multiple sas processes try to use the same file.
 +
* -nonews: Prevents SAS from printing a useless header to the output.
 +
* -memsize xxxxM - [http://support.sas.com/documentation/cdl/en/hostunx/63053/HTML/default/viewer.htm#n09y5anvvpzrmnn0ztkyf59qgzvr.htm specifies the total amount of memory that is available to each SAS session, and places an enforced limit on the amount of virtual memory that SAS can dynamically allocate at any one time].
 +
* -realmemsize xxxxM  - sets the [http://support.sas.com/documentation/cdl/en/hostunx/63053/HTML/default/viewer.htm#p00ta2t9eibgofn19cmdlpdfgjnw.htm recommended upper limit on working memory for procedures that can use both memory and utility disk space, such as PROC SUMMARY and PROC SORT, so that they can avoid virtual memory thrashing].
 +
* -work $TMPDIR - the directory where SAS should store its temporary files. Using $TMPDIR will allow your program to run much faster and prevent any network-related file access issues that SAS is prone to run into.
 
* -sysin file : Designate a file for SAS to load as its input.
 
* -sysin file : Designate a file for SAS to load as its input.
==Batch Submission==
+
===Batch Submission===
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.
+
To do a batch submission of a SAS script 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 cluster.
===Sample Job Script Ver 9.1===
+
===-work directory===
<pre>
+
SAS is a mature product with a long history behind it. In a modern high-performance environment it means that additional actions need to be taken to mitigate potential issues stemming from SASs focus on filesystem I/O instead of using memory.  
#!/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
+
===Interactive Use===
</pre>
+
See [[GUI_Programs]] to learn how to run the Graphical SAS interface for short debugging sessions.
Note the memsize option above. By default, if this option is not used, SAS will default to 64mb of memory usage.
+
|}}
===Sample Job Script Ver 9.2===
+
{{#if: {{#var: conf}}|==Configuration==
 +
See the [[{{PAGENAME}}_Configuration]] page for {{#var: app}} configuration details.|}}
 +
==PBS Script Examples==
 +
===Sample Job Script===
 
<pre>
 
<pre>
 
#!/bin/bash
 
#!/bin/bash
 
#
 
#
#PBS -r n
+
#SBATCH --name=sas_job
#PBS -N Market Research
+
#SBATCH --output=sas_%j.out
#PBS -o market.out
+
#SBATCH --mail-type=END,FAIL #Only email summary and failure reports
#PBS -m abe
+
#SBATCH --mail-user=your_email_address  # Where to send mail
#PBS -M <EMAIL ADDRESS>
+
#SBATCH --ntasks=1                    # Run on a single CPU
#PBS -e market.err
+
#SBATCH --mem=1gb                  # Memory limit
#PBS -l nodes=1:ppn=1
+
#SBATCH --time=01:00:00         # Run for up to one hour
#PBS -l pmem=600mb
+
date;hostname;pwd
#PBS -l walltime=00:15:00
 
 
 
EXE=/apps/sas/9.2/SASFoundation/9.2/sas
 
cd /scratch/ufhpc/
 
 
 
$EXE -memsize 1024M -nodms -work `pwd` -filelocks none -sysin sas.inp
 
</pre>
 
===Sample Job Script Ver 9.3===
 
<pre>
 
#!/bin/bash
 
#
 
#PBS -r n
 
#PBS -N Market Research
 
#PBS -o market.out
 
#PBS -m abe
 
#PBS -M <EMAIL ADDRESS>
 
#PBS -e market.err
 
#PBS -l nodes=1:ppn=1
 
#PBS -l pmem=600mb
 
#PBS -l walltime=00:15:00
 
 
 
EXE=/apps/sas/9.3/SASFoundation/9.3/sas
 
cd /scratch/ufhpc/
 
 
 
$EXE -memsize 1024M -nodms -work `pwd` -filelocks none -sysin sas.inp
 
</pre>
 
 
 
==Possible Errors==
 
* If the following error appears:
 
<pre>
 
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
 
</pre>
 
You will need to use the '''-filelocks none''' option as described above when starting SAS.
 
<pre>
 
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
 
</pre>
 
You need to designate where your work area is with the '''-work LOCATION''' directive.
 
<pre>
 
X11 connection rejected because of wrong authentication.
 
Fatal I/O error
 
The network connection has been lost.
 
 
 
Traceback
 
Traceback
 
  
 +
module load sas
  
No Traceback Available
+
sas -memsize 1024M -nodms -nonews -work $TMPDIR -filelocks none -sysin sas.inp
No Traceback Available
 
 
</pre>
 
</pre>
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: {{#var: policy}}|==Usage Policy==
* 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.
+
WRITE USAGE POLICY HERE (perhaps templates for a couple of main licensing schemes can be used)|}}
 +
{{#if: {{#var: testing}}|==Performance==
 +
WRITE PERFORMANCE TESTING RESULTS HERE|}}
 +
{{#if: {{#var: faq}}|==FAQ==
 +
*'''Q:''' **'''A:'''|}}

Latest revision as of 21:24, 6 December 2019

Description

sas website  

SAS is a commercial integrated system for statistical analysis, data mining, and graphics as well as many enterprise oriented additional features. SAS cost and the breadth of SAS features means that both a significant monetary investment and a substantial time investment are required to master it. SAS 9.3 Documentation is vast. For research purposes the SAS 9.3 User's Guide is a thorough reference for the functions and procedures you may need to do the statistical analysis using SAS.

Required Modules

modules documentation

Serial

  • sas

System Variables

  • HPC_SAS_DIR - installation directory

Additional Information

Commands

SAS has a number of options:

Batch Submission

To do a batch submission of a SAS script 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 cluster.

-work directory

SAS is a mature product with a long history behind it. In a modern high-performance environment it means that additional actions need to be taken to mitigate potential issues stemming from SASs focus on filesystem I/O instead of using memory.

Interactive Use

See GUI_Programs to learn how to run the Graphical SAS interface for short debugging sessions.

PBS Script Examples

Sample Job Script

#!/bin/bash
#
#SBATCH --name=sas_job
#SBATCH --output=sas_%j.out
#SBATCH --mail-type=END,FAIL #Only email summary and failure reports
#SBATCH --mail-user=your_email_address   # Where to send mail	
#SBATCH --ntasks=1                    # Run on a single CPU
#SBATCH --mem=1gb                  # Memory limit
#SBATCH --time=01:00:00          # Run for up to one hour
date;hostname;pwd

module load sas

sas -memsize 1024M -nodms -nonews -work $TMPDIR -filelocks none -sysin sas.inp