Tuesday, September 24, 2013

SAS 9.4 Foundation requirements and clients

SAS 9.4 Foundation

  1. Windows OS -  32 bit or 64 bit
  2. Web browser - IE 32 or 64

SAS®Enterprise Guide®6.1
Supported Operating Systems
SAS Enterprise Guide is supported on the following platforms:
• Microsoft Windows Server 2008 (x64) with Service Pack 2
• Microsoft Windows Server 2008 R2 with Service Pack 1
• Microsoft Windows Server 2012 (x64)
• Microsoft Windows 7 (x64) with Service Pack 1 - Professional, Enterprise & Ultimate 
Editions
• Microsoft Windows 8 Pro (x64)
SAS Enterprise Guide 6.1 is now only available as a 64-bit application. Therefore, it is only supported 
on the 64-bit editions of the Microsoft Windows operating systems listed above.
System Requirements Wizard
The System Requirements Wizard is used to ensure that a computer onto which you would like to 
install SAS Enterprise Guide software meets the minimum system software requirements. Space 
requirements will vary depending upon the third-party components and the individual files on your 
computer that need to be updated. The System Requirements Wizard will inform you of the components that do not meet the minimum system requirements before updating them. The System Requirements Wizard will install these components if you do not already have them installed on your system:
• Microsoft .NET Framework 4.0
• Microsoft Windows Installer 3.1
• Microsoft Runtime Components 8.0 Service Pack 1
• Microsoft Runtime Components 9.0 Service Pack 1
• Microsoft Runtime Components 10

SAS® Add-In 6.1 for Microsoft Office
Supported Operating Systems
SAS Add-In for Microsoft Office is supported on the following platforms:
• Microsoft Windows Server 2008 with Service Pack 2 (both 32-bit and 64-bit versions)
• Microsoft Windows Server 2008 R2 with Service Pack 1
• Microsoft Windows Server 2012
• Microsoft Windows 7 with Service Pack 1 - Professional, Enterprise and Ultimate Editions 
(both 32-bit and 64-bit versions)
• Microsoft Windows 8 Pro (both 32-bit and 64-bit versions
Additional Software Requirements
One of the following versions of Microsoft Office is required:
• Microsoft Office 2007 
• Microsoft Office 2010 (32-bit or 64-bit)
• Microsoft Office 2013 (32-bit or 64-bit)
The SAS Add-In for Microsoft Office is now available as either a 32-bit or a 64-bit application. If you are using 32-bit Microsoft Office, you must use the 32-bit version of the SAS Add-In for Microsoft Office. If you are using 64-bit Microsoft Office, you must use the 64-bit version of SAS Add-In for Microsoft Office.The SAS Add-In for Microsoft Office supports Microsoft Office 2013 desktop clients that are deployed from Microsoft Office 365 or on-premise deployment systems. Microsoft Office web applications that are browser-based are not supported.

SAS 9.3 Foundation requirements and clients

SAS 9.3 Foundation

SAS®Add-In 5.1 for Microsoft Office
Supported Operating Systems
SAS Add-In for Microsoft Office is supported on the following platforms:
• Microsoft Windows XP Professional with Service Pack 3
• Microsoft Vista with Service Pack 1
• Microsoft Windows Server 2003 with Service Pack 2
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2
• Microsoft Windows 7
For the best user experience, we recommend one of the following platforms:
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2

• Microsoft Windows 7
Additional Software Requirements
One of the following versions of Microsoft Office is required:
• Microsoft Office 2007
• Microsoft Office 2010 (32-bit or 64-bit)
The SAS Add-In for Microsoft Office is now available as either a 32-bit or a 64-bit application. If you are using 32-bit Microsoft Office, you must use the 32-bit version of the SAS Add-In for Microsoft Office. If you are using 64-bit Microsoft Office, you must use the 64-bit version of SAS Add-In for Microsoft Office.

SAS® Enterprise Guide® 5.1
Supported Operating Systems
SAS Enterprise Guide is supported on the following platforms:
 Microsoft Windows XP Professional with Service Pack 3
 Microsoft Windows XP Professional x64 Edition with Service Pack 2
 Microsoft Vista with Service Pack 1
 Microsoft Windows Server 2003 with Service Pack 2
 Microsoft Windows Server 2008
 Microsoft Windows Server 2008 R2
 Microsoft Windows 7
For the best user experience, we recommend one of the following platforms:
 Microsoft Vista with Service Pack 1
 Microsoft Windows Server 2008
 Microsoft Windows Server 2008 R2
 Microsoft Windows 7
SAS Enterprise Guide 5.1 is now available as either a 32-bit or a 64-bit application. If you are using a 32-bit Microsoft Windows operating system, then you must use the 32-bit version of SAS Enterprise Guide. If you are using a 64-bit Windows operating system, then you can run either the 32-bit or the 64-bit version of SAS Enterprise Guide. Note: In the 64-bit version of SAS Enterprise Guide, you cannot open Microsoft Exchange or Microsoft Access data. If you need these features, install the 32-bit version of SAS Enterprise Guide.
System Requirements Wizard
The System Requirements Wizard is used to ensure that a computer onto which you would like to
install SAS Enterprise Guide software meets the minimum system software requirements. Space
requirements will vary depending upon the third-party components and the individual files on your
computer that need to be updated.
The System Requirements Wizard will inform you of the components that do not meet the minimum
system requirements before updating them. The System Requirements Wizard will install these
components if you do not already have them installed on your system:
 Microsoft .NET Framework 4.0
 Microsoft Windows Installer 3.1
 Microsoft Runtime Components 7.0
 Microsoft Runtime Components 8.0 Service Pack 1
 Microsoft Runtime Components 9.0 Service Pack 1

 Microsoft Runtime Components 10



SAS Microsoft Add-in 6.1 Requirements using 9.4 EBI SAS Server


Link

System Requirements
1
SAS®
Add-In 6.1 for Microsoft Office
Basic Installation Requirements
Platform Installation Space Required Minimum 
Recommended RAM
Microsoft Windows 400 MB 2 GB
Microsoft Windows for x64 400 MB 2 GB
Supported Operating Systems
SAS Add-In for Microsoft Office is supported on the following platforms:
• Microsoft Windows Server 2008 with Service Pack 2 (both 32-bit and 64-bit versions)
• Microsoft Windows Server 2008 R2 with Service Pack 1
• Microsoft Windows Server 2012
• Microsoft Windows 7 with Service Pack 1 - Professional, Enterprise and Ultimate Editions 
(both 32-bit and 64-bit versions)
• Microsoft Windows 8 Pro (both 32-bit and 64-bit versions)
Additional Software Requirements
One of the following versions of Microsoft Office is required:
• Microsoft Office 2007 
• Microsoft Office 2010 (32-bit or 64-bit)
• Microsoft Office 2013 (32-bit or 64-bit)
The SAS Add-In for Microsoft Office is now available as either a 32-bit or a 64-bit application. If you 
are using 32-bit Microsoft Office, you must use the 32-bit version of the SAS Add-In for Microsoft 
Office. If you are using 64-bit Microsoft Office, you must use the 64-bit version of SAS Add-In for 
Microsoft Office.
The SAS Add-In for Microsoft Office supports Microsoft Office 2013 desktop clients that are deployed 
from Microsoft Office 365 or on-premise deployment systems. Microsoft Office web applications that 
are browser-based are not supported.SAS and all other SAS Institute product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and 
other countries. Other brand and product names are registered trademarks or trademarks of their respective companies.
 indicates USA registration.
Copyright  2013 SAS Institute Inc., Cary, NC, USA. All rights reserved.
2
26 July 2013
System Requirements Wizard
The System Requirements Wizard is used to ensure that a computer onto which you would like to 
install SAS Add-In for Microsoft Office software meets the minimum system software requirements. 
Space requirements will vary depending upon the third-party components and the individual files on 
your computer that need to be updated. 
The System Requirements Wizard will inform you of the components that do not meet the minimum 
system requirements before updating them. The System Requirements Wizard will install these 
components if you do not already have them installed on your system:
• Microsoft .NET Framework 4.0
• Microsoft Windows Installer 3.1
• Microsoft Runtime Components 8.0 Service Pack 1
• Microsoft Runtime Components 9.0 Service Pack 1
• Microsoft Runtime Components 10
• Microsoft Visual Studio Tools for Office 10.0
Additional Requirement Information
To run SAS Add-In for Microsoft Office after it is installed, you must have one of the following 
configurations:
• SAS Foundation installed on the client machine (local configuration)
• A metadata connection to a SAS Metadata Server and SAS Workspace Server with 
SAS/Integration Technologies (remote configuration)

SAS 9.4 Foundation requirements

Link


19 September 2013

Table of Contents
Using the System Requirements............................................................................ 1
SAS Technical Support.................................................................................... 1
Preparing for Installation ............................................................................... 2
File System Requirements ........................................................................................... 2
Administrator Privilege ................................................................................................ 2
Anti-virus and/or Firewall Software ............................................................................... 2
Windows for x64 Environments...................................................................... 2
Server Operating Systems........................................................................................... 2
Microsoft Windows Server 2008 Family......................................................................................................2
SAS Support for Windows 7 and Windows 8 ........................................................... 3
Supported Operating Environments for Windows........................................... 3
Java Requirements......................................................................................... 3
Web Browser.................................................................................................. 3
Hardware Requirements.......................................................................................... 5
Machines Supported ....................................................................................... 5
Distribution Media .......................................................................................... 5
System Configuration ..................................................................................... 5
Desktop Systems ....................................................................................................... 5
Server Systems ......................................................................................................... 5
Monitors Supported........................................................................................ 5
Additional Features ................................................................................................. 6
The User Installation Experience in SAS 9.4................................................... 6
Internet Access.......................................................................................................... 6
HTMLHelp Viewer ....................................................................................................... 6
SAS Universal Viewer.................................................................................................. 6
Dynamic Data Exchange.............................................................................................. 6
Electronic Mail ........................................................................................................... 6
SAS Service Configuration Utility .................................................................................. 7
SAS Deployment Wizard and Subset Orders ................................................................... 7
Space Requirements ............................................................................................... 8
Disk Space Consumed by Installed Products .................................................. 8
DBCS Support................................................................................................. 9
National Language Support (NLS) .................................................................. 9
Asian Language Support............................................................................................ 10
Specific Product Requirements............................................................................ 11
Base SAS Software ....................................................................................... 11
SAS Analytics Accelerator for Teradata ........................................................ 11
SAS High-Performance Forecasting 12.1 ...................................................... 11
SAS Scoring Accelerator for Aster ................................................................ 11
SAS Scoring Accelerator for DB2 .................................................................. 11
SAS Scoring Accelerator for Greenplum........................................................ 12
SAS Scoring Accelerator for Netezza ............................................................ 12ii
SAS Scoring Accelerator for Oracle............................................................... 12
SAS Scoring Accelerator for Teradata........................................................... 13
SAS/ACCESS Interface to Aster.................................................................... 14
SAS/ACCESS Interface to DB2...................................................................... 14
SAS/ACCESS Interface to Greenplum ........................................................... 14
SAS/ACCESS Interface to Hadoop ................................................................ 14
SAS/ACCESS Interface to MySQL.................................................................. 15
SAS/ACCESS Interface to Netezza................................................................ 15
SAS/ACCESS Interface to ODBC ................................................................... 15
SAS/ACCESS Interface to OLE DB................................................................. 15
SAS/ACCESS Interface to Oracle .................................................................. 16
SAS/ACCESS Interface to PC Files ................................................................ 16
SAS/ACCESS Interface to PostgreSQL .......................................................... 17
SAS/ACCESS Interface to SAP HANA ............................................................ 17
SAS/ACCESS Interface to Sybase ................................................................. 17
SAS/ACCESS Interface to Sybase IQ ............................................................ 17
SAS/ACCESS Interface to Teradata .............................................................. 18
SAS/ACCESS Interface to Vertica ................................................................. 18
SAS/AF......................................................................................................... 18
SAS/CONNECT.............................................................................................. 19
SAS/EIS ....................................................................................................... 19
SAS/Genetics 12.1 ....................................................................................... 19
SAS/GIS ....................................................................................................... 19
SAS/GRAPH.................................................................................................. 20
SAS/IntrNet ................................................................................................. 20
CGI Tools and Applications .................................................................................... 20
Application Dispatcher: ............................................................................................20
htmSQL:....................................................................................................20
MDDB Report Viewer Application:.......................................................................................20
Xplore Sample Web Application:...............................................................................................20
Design-Time Controls: ................................................................................................................20
Java Tools and Applications ....................................................................................... 21
SAS/CONNECT Driver for Java:...............................................................................................................21
Tunnel Feature:...................................................................................................................21
SAS/OR 12.1 ................................................................................................ 21
SAS/TOOLKIT............................................................................................... 21
SAS/Warehouse Administrator..................................................................... 21

System Requirements for SAS 9.4 Foundation for Microsoft Windows for x64
Page 1
Using the System Requirements
This document provides requirements for installing and running SAS 9.4 Foundation on Microsoft
Windows for x64. You must update your system to meet the minimum requirements before running
SAS 9.4 Foundation.
These are the major requirements listed in the document:
Software Requirements
Hardware Requirements
Additional Features
Space Requirements
Specific Product Requirements
For additional information and to view the latest system requirements for your system, please visit
the SAS Install Center web site, http://support.sas.com/documentation/installcenter.
SAS Technical Support
For information about SAS Technical Support, please visit http://support.sas.com/techsup/.System Requirements for SAS 9.4 Foundation for Microsoft Windows for x64
2
Software Requirements
Preparing for Installation
File System Requirements
The 8.3 filename convention must remain enabled. The use of file systems supporting long filenames
is recommended.
Administrator Privilege
An installer must have administrator privilege to install various updates. This requirement ensures
that SAS 9.4 Foundation can be completely and safely installed.
Anti-virus and/or Firewall Software
Before you start, it is recommended that you close your anti-virus and firewall software. Some antivirus and/or firewall configurations can prevent an application from installing successfully. If you are
unable to close the anti-virus or firewall software, make sure that your configuration allows you to
install software and to update the registry. If your SAS installation fails and you have mandatory
anti-virus or firewall software running, please check with your system administrator.
Windows for x64 Environments
SAS 9.4 Foundation is supported in the following environments:
Server Operating Systems
Microsoft Windows Server 2008 Family
SAS 9.4 Foundation is supported on the following x64 editions of the Windows Server 2008 family
with SAS 9.4 TS1M0 and higher:
Microsoft Windows Server 2008 SP2 Standard Edition
Microsoft Windows Server 2008 SP2 Enterprise Edition
Microsoft Windows Server 2008 SP2 Datacenter Edition
SAS 9.4 Foundation is supported on the following x64 editions of the Windows Server 2008 R2 family
with SAS 9.4 TS1M0 and higher:
Microsoft Windows Server 2008 R2 SP1 Standard Edition
Microsoft Windows Server 2008 R2 SP1 Enterprise Edition
Microsoft Windows Server 2008 R2 SP1 Datacenter Edition
SAS 9.4 Foundation is supported on the following x64 editions of the Windows Server 2012 family
with SAS 9.4 TS1M0 and higher:
Microsoft Windows Server 2012 DataCenter Edition
Microsoft Windows Server 2012 Standard Edition
Microsoft Windows Server 2012 Essentials Edition
Microsoft Windows Server 2012 Foundation Edition

Monday, July 8, 2013

Logging - Workspace Server


Link



Create a Log File for Workspace Server Troubleshooting

Standard (non-pooled) workspace servers are not initially configured to produce log files. However, you might need to capture workspace server messages in a log file for troubleshooting purposes. In these situations, you can use the alternative logging configuration file (logconfig.trace.xml) that is provided in each workspace server's configuration directory.
The alternative configuration provides high-level logging messages (for example, DEBUG and TRACE messages) which can be used by SAS Technical Support to help resolve server issues. The messages are written to a rolling log file. The file is written to a Logs directory within the server's configuration directory.
CAUTION:
Do not use or modify the logconfig.trace.xml logging configuration files unless you are requested to do so by SAS Technical Support.
Performance issues can result from the use of these files.  [cautionend]
If SAS Technical Support requests that you enable detailed logging for workspace server troubleshooting, follow these steps:
  1. If you are enabling workspace server logging to a log file for the first time, you must grant all users of the workspace server Read, Write, and Execute access to the server's Logs directory.
  2. Rename the server's logconfig.xml file to logconfig_orig.xml.
  3. Rename the server's logconfig.trace.xml file to logconfig.xml.
  4. When troubleshooting is completed, do the following:
    1. Rename logconfig.xml to logconfig.trace.xml.
    2. Rename logconfig_orig.xml to logconfig.xml.
Note:   You can also adjust logging dynamically by using the Server Management features of SAS Management Console. See Using SAS Management Console to Monitor SAS Servers.  [cautionend]

_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546

Thursday, May 2, 2013

EG access to metadata files

I found out a interesting thing about data access today for Enterprise Guide. If you load a file onto the process flow panel from the SAS folds structure you are actually using the metadata to do that. If you load your file onto the process flow panel from the SAS Servers (libraries) list you are actually loading the real file and not thru metadata.

_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546

Friday, April 19, 2013

SAS Addin Software requirements

SAS Addin 5.1

Link

Platform
Microsoft Windows 400 MB\2 GB
Microsoft Windows for x64  400 MB\2 GB
Supported Operating Systems
SAS Add-In for Microsoft Office is supported on the following platforms:
• Microsoft Windows XP Professional with Service Pack 3
• Microsoft Vista with Service Pack 1
• Microsoft Windows Server 2003 with Service Pack 2
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2
• Microsoft Windows 7
For the best user experience, we recommend one of the following platforms:
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2
• Microsoft Windows 7
Additional Software Requirements
One of the following versions of Microsoft Office is required:
• Microsoft Office 2007
• Microsoft Office 2010 (32-bit or 64-bit)
The SAS Add-In for Microsoft Office is now available as either a 32-bit or a 64-bit application. If you are using 32-bit Microsoft Office, you must use the 32-bit version of the SAS Add-In for Microsoft Office. If you are using 64-bit Microsoft Office, you must use the 64-bit version of SAS Add-In for Microsoft Office.


SAS Addin 4.3

Software Requirements
platforms:
• Microsoft Windows XP Professional updated with Service Pack 3 or later (both 32‐bit and
x64‐bit versions)
• Microsoft Windows Vista ‐ Business, Enterprise, and Ultimate Editions (both 32‐bit and
x64‐bit versions)
• Microsoft Windows 7 ‐ all versions
• Microsoft Windows Server 2003 (both 32‐bit and x64‐bit versions)
• Microsoft Windows Server 2008 (both 32‐bit and x64‐bit versions)
Additional Software Requirements
One of the following Microsoft Office installs:
• Microsoft Office 2010 (32‐bit version only)
• Microsoft Office 2007
• Microsoft Office 2003
System Requirements Wizard
The System Requirements Wizard is used to ensure that a computer onto which you would like to
install SAS Add‐In for Microsoft Office software meets the minimum system software requirements.
Space requirements will vary depending upon the third‐party components and the individual files on
your computer that need to be updated.
The System Requirements Wizard will inform you of the components that do not meet the minimum
system requirements before updating them. The System Requirements Wizard will install these
components if you do not already have them installed on your system:
• Microsoft Runtime Components 8.0 SP1
• Microsoft Runtime Components 9.0 SP1
• Microsoft .NET Framework 3.5 SP1
• Microsoft Web Services Enhancements 3.0
• Microsoft Visual Studio Tools for Office 2.0
• Microsoft Visual Studio Tools for Office 3.0
• Microsoft Visual Studio Tools for Office 3.0 SP1
SAS

_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546

Thursday, April 11, 2013

How to determine if a process has a lock on a file


Link

Received this SAS error:
ERROR: A lock is not available for ******.********.DATA.

Introduction

Sometimes, you try to delete a file and receive access violation or file in use - errors. To successfully delete a file, you will need to identify the process which has locked the file. You need to exit the process first and then delete the particular file. To know which process has locked a file, you may use one of the methods discussed in this article.

Using Process Explorer

Process Explorer shows you information about which handles and DLLs processes have opened or loaded.
  • Download Process Explorer from Microsoft site and run the program.
  • Click the Find menu, and choose Find Handle or DLL...
  • Type the file name (name of the file which is locked by some process.)
  • After typing the search phrase, click the Search button
You should see the list of applications which are accessing the file. Here is a screenshot:
Note: There is also a command-line tool named Handle from Windows Sysinternalsthat can display open handles for any process in the system.

Wednesday, March 20, 2013

ORA-01555 & ORA-02063 error


ERROR: Error fetching from cursor. ORACLE error is ORA-01555: snapshot too old: rollback segment
       number  with name "" too smallORA-02063: preceding line from "DataBase Path"



Proc sql ;
  connect to oracle as ora (blah blah blah) ;
  create table gnu as
  select * from connection to ora
  (select day accnt_id record_type record_subtype
                    paid_mou bonus_mou cust_type COS
   from DW_CDR_ACCOUNT_DAY
   where day <= to_date(&orastartdate) and cust_type='Consumer' and record_type in ('VOICE','SMS','XTRAS') and COS in (10,20,30,40,60)
   ) ;
   disconnect from ora ;
Quit ;

Data usage2 ; set gnu ; Yadda yadda yadda. ;
-Roy
********************************************************************************
Thanks for all, for your valuable suggestions, I have sent my code and the error to my DBA.
I am sending the code to all of you, so that all who have spend time on this error can have a look at the code and let me know your comments in tuning the code.
options obs=max errorabend compress=yes BUFNO=256 BUFSIZE=64;
data _null_; enddate=today(); startdate=enddate-90; *startdate=intnx('month',date(),-4,'b'); *enddate=intnx('month',date(),-2,'e'); call symput ('startdate',startdate); call symput ('enddate',enddate); run;
%let oraStartDate=%eval(&startdate*60*60*24); %let oraEndDate=%eval((&enddate*60*60*24)+(86399));
data usage2 (keep=accnt_id monthof duration total_mou); set ora_dev.DW_CDR_ACCOUNT_DAY (keep=day accnt_id record_type record_subtype paid_mou bonus_mou cust_type COS); where day <= &orastartdate. and cust_type='Consumer' and record_type in ('VOICE','SMS','XTRAS') and COS in (10,20,30,40,60); day_date=datepart(day); monthof = intnx('month',day_date,0); array fixnulls(3) $ accnt_id record_type record_subtype; do i=1 to 3; if fixnulls(i)='NULL' then fixnulls(i)=' '; end; format day_date date7.; duration=sum(paid_mou,bonus_mou); if duration=. then duration=0; total_mou=duration; format monthof mmddyy8.; run;
I am facing error due to this ora_dev.DW_CDR_ACCOUNT_DAY data set.
ERROR: Error fetching from cursor. ORACLE error is ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$" too small.
The Oracle docs note this on the ora-02063 error:

ORA-02063: preceding stringstring from stringstring
 
Cause: an Oracle error was received from a remote database link.
 Action: refer to the preceding error message(s)
Oracle MOSC documents give an account of ORA-02063 as occurring when "You want to query or update a remote table and receive the following error":
ORA-02063: preceding line from <name of a database link> This also happens when a select is issued over a database link, and not a  distributed transaction Solution Description -------------------- The ORA-2063 indicates that this must be done at the remote database. Explanation ----------- When the error is generated at the remote database it is accompanied with an ORA-2063. In this case the parameter distributed_transactionsmust be increased at the remote database. If there is no ORA-2063 the parameter distributed_transactions must be increased at the local database. In a distributed environment, if a select is issued in a session without the  SET TRANSACTION READ ONLY command, the select query is considered a distributed transaction. If the parameter distributed_transactions is set too low, this too will result in an ORA-2042 and ORA-2063  
It is important to note that ORA-02063 typically appears with ORA-02042

SAS FullsTimer Option

Link


FULLSTIMER SAS Option

The SAS System provides the FULLSTIMER option to collect performance statistics on each SAS step, and for the job as a whole and place them in the SAS log. It is important to note that the FULLSTIMER measures only give you a snapshot view of performance at the step and job level. Each SAS port yields different FULLSTIMER statistics based on the host operating system. See the SAS host specific documentation for the exact statistics offered. FULLSTIMER is invoked as a SAS option and takes effect after the option invocation. If you would like to have the performance statistics written to a SAS data set, download this ZIP file which contains the experimental %LOGPARSE macro.
Why start with the FULLSTIMER option for monitoring? The best reason is that it tells you what is happening with the SAS system specifically. The statistics it provides are at the job step and can help pinpoint performance problems down to the step. This is extremely helpful in narrowing troublesome activity, and relating it to what your code is telling the system to do. (Note: If the test execution is long, expensive, high impact to the environment, and is not easily set up, the SAS session monitoring can be done simultaneously with server and system performance monitoring.) FULLSTIMER measures can be used to help determine if more in-depth performance monitoring with host monitoring or third party tools is indicated.
A sample result of a FULLSTIMER option UNIX output for a SAS Data Step is listed below:


NOTE: DATA statement used:
real time 0.06 seconds
user cpu time 0.02 seconds
system cpu time 0.00 seconds
Memory 88k
Page Faults 10
Page Reclaims 0
Page Swaps 0
Voluntary Context Switches 22
Involuntary Context Switches 0
Block Input Operations 10
Block Output Operations 12
It is important to know how these numbers are defined and what can be derived from them.
FULLSTIMER Statistics Definition and Interpretation
Real Time - the Real Time represents the elapsed time or "wall clock" time. This is the time spent to execute a job or step. This is the time the user experiences in wait for the job/step to complete. Note: As host system resources are heavily utilized the Real Time can go up significantly - representing a wait for various system resources to become available for the SAS job/step's usage.
User CPU Time - the time spent by the processor to execute user-written code. This is user-written from the perspective of the operating system and not the customer's language statements. That is all SAS system code that is not operating system code.
System CPU Time - the time spent by the processor to execute operating system tasks that support user-written code (all CPU tasks that were not executing user-written code). The user CPU time and system CPU time are mutually exclusive.
Memory - Memory represents the amount of memory allocated to that job/step. This does not represent the entire amount of memory that the SAS session is consuming, as it does not reflect any SAS overhead activities (SAS manager, etc.).
Page Faults - Represents the number of virtual memory page faults that occurred during the job/step. Page Faults are pages that required an I/O to retrieve (a read was done to the I/O subsystem).
Page Reclaims - Represents the number of pages retrieved from the page list awaiting re-allocation (all done in memory). These pages did not require I/O activity to obtain.
Page Swaps - The number of times a process was swapped out of main memory.
Voluntary Context Switches - Represents the number of times a process releases its CPU time-slice voluntarily before it's time-slice allocation is expired. This usually occurs when the process needs an external resource, like making an I/O call for more da ta.
Involuntary Context Switches - The number of times a process releases its CPU time-slice involuntarily. This usually happens when its CPU time-slice has expired before the task was finished, or a higher priority task takes its time-slice away.
Block Input Operations - The number of "bufsize" reads that occur. These are I/O operations to read the data into memory for usage. Not all reads have to utilize an I/O operation since the page being requested may still be cached in memory from previous r eads.
Block Output Operations - This represents the number of "bufsize" writes that occur. These are the same as block input operations except that they pertain to the writes to files. As in the case of block input operations, not all block outputs will cause an I/O operation. Some files may still be cached in memory.
Performance problems usually involve one or more of the following physical areas:
  • CPU activity
  • Memory activity
  • I/O subsystem activity (disk and file systems) Network activity (this will be discussed outside the context of the SAS system later).
By examining FULLSTIMER statistics, and interpreting what is happening with and between the factors producing the measures, we can get a quick idea of where the system is having problems. We can then resort to host-level and third-party measuring tools to obtain a very detailed picture of problem issue. If the host-level and third-party tools give such detail why not use them first? Very simply, there are many tools to use, and each is fairly good at one or more specific areas of investigation, such as CP, Memory, and I/O. Also some require Server Root-Level access to deploy. FULLSTIMER is quick and easy (incorporated in the SAS system), requires no special privileges, you can do it yourself, and it can help quickly narrow the field of things to test next.
The following is a general list of interpretations you can make using FULLSTIMER:
  • Real Time/CPU Time. The most valuable way to use FULLSTIMER is to compare timing information. By comparing the Real Time (elapsed time), with the total CPU time (system CPU time plus user CPU time) you can quickly determine if the problem is CPU related.
    • If the Real time and total CPU time are within 15 percent of each other, this usually indicates that the system is moving data well (at least during the run time of that job/step processing). This means that the ratio of CPU process time is close to that of the total job. This indicates that the system memory, disk system, and file system are getting data to the CPU quickly enough to not be a problem. If you are experiencing bad task performance, and the real and CPU time are within 15 percent of each other, it most likely means that your task is CPU bound. The only way to improve the performance will be to get a faster CPU, split the process over more CPUs (multi-threading or parallel processing), or reengineer the code to be more efficient.
    • If the Real time and total CPU time are routinely very disparate, (for example if there is a 50 percent margin between them), then you very likely have a problem in your system getting information to the CPU fast enough. Make a closer examination of the Memory and I/O subsystems using the host or third-party tools mentioned in the next section.
Other valuable information from FULLSTIMER can be gained by looking at the other statistics:
  • Memory. If a sizeable quantity of memory is used and your elapsed time differs greatly from your total CPU time, you may also want to take a close look at your memory using host or third-party tools that are mentioned in the next section.
  • Involuntary Context Switches. If Involuntary Context Switches are consistently high across many steps and jobs over long time-periods, then your CPU system is under a heavy load, and you will want to examine that more closely with the tools mentioned in the next section.
  • Page Swaps. If Page Swaps are consistently high then your memory system is being stressed, and needs more examination.
Other statistics like Block Input and Output operations, Page Faults and Reclaims, and Voluntary Context switches can hint at issues, but require more corroboration from the measures previously discussed to make a case for narrowing down investigation. These measures could be high in-and-of themselves without being a symptom of performance problems.
Once FULLSTIMER statistics have been examined, they should help indicate which area(s) should be examined in more detail. It is often the case on overloaded systems that multiple areas present themselves for examination. The FULLSTIMER activity should help point to tools that could be used to get a more detailed level picture of any hardware/file system issues. This comprises our next step, detecting performance issues at the host server system level.
page divider
We at SAS have created the Scalability Community to make you aware of the connectivity and scalability features and enhancements that you can leverage for your SAS installation. The success of this community depends on you. Send electronic mail to scalability@sas.com with your comments, requirements, and suggestions.
_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546


Tuesday, March 19, 2013

Best Practices for Configuring your IO Subsystem for SAS®9 Applications


This is a great paper concerning IO for your SAS EBI

io subsystem configuration


_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546


SAS Dataflux state\province list

I got this one from some DataFlux doc.

US STATES
=========
AL Alabama
AK Alaska
AZ Arizona
AR Arkansas
CA California
CO Colorado
CT Connecticut
DE Delaware
DC District of Columbia
FL Florida
GA Georgia
HI Hawaii
ID Idaho
IL Illinois
IN Indiana
IA Iowa
KS Kansas
KY Kentucky
LA Louisiana
ME Maine
MD Maryland
MA Massachusetts
MI Michigan
MN Minnesota
MS Mississippi
MO Missouri
MT Montana
NE Nebraska
NV Nevada
NH New Hampshire
NJ New Jersey
NM New Mexico
NY New York
NC North Carolina
ND North Dakota
OH Ohio
OK Oklahoma
OR Oregon
PA Pennsylvania
RI Rhode Island
SC South Carolina
SD South Dakota
TN Tennessee
TX Texas
UT Utah
VT Vermont
VA Virginia
WA Washington
WV West Virginia
WI Wisconsin
WY Wyoming

AS American Samoa
FM Fed. States of Micronesia
GU Guam
MH Marshall Islands
MP Northern Mariana Is.
PW Palau
PR Puerto Rico
VI Virgin Islands


CANADIAN PROVINCES
==================
AB Alberta
BC British Columbia
MB Manitoba
NB New Brunswick
NF Newfoundland
NT Northwest Territories
NS Nova Scotia
ON Ontario
PE Prince Edward Island
QC Quebec
SK Saskatchewan
YT Yukon
_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546


EG 4.2, 4.3, and 5.1 Turning on logging


Link

Usage Note 17730: Turning on logging in SAS® Enterprise Guide® 4.2, 4.3, and 5.1

DetailsAboutRate It
To start the logging feature, copy the logging.config file from your SAS Enterprise Guide home directory (see below) to this directory:

%appdata%\SAS\EnterpriseGuide\x.x\
SAS Enterprise Guide generates one log file for each SAS Enterprise Guide session. The logs reside in this directory:

%appdata%\SAS\EnterpriseGuide\x.x\Logs
The following are the default SAS Enterprise Guide home directories:
ProductLocation
SAS Enterprise Guide 4.2C:\Program Files\SAS\EnterpriseGuide\4.2\
SAS Enterprise Guide 4.3C:\Program Files\SAS\EnterpriseGuide\4.3\
SAS Enterprise Guide 5.1C:\Program Files\SASHome\SASEnterpriseGuide\5.1\

To display the %APPDATA% Windows variable, submit the SET APPDATA command from a Windows command prompt, as shown below:
set appdata
The following table shows the default locations:
Windows EditionLocation
Windows XP / Windows 2003 ServerC:\Documents and Settings\user-id\Application Data
Windows Vista / Windows 7 / Windows 2008 ServerC:\Users\user-id\AppData\Roaming
To stop logging, delete the logging.config file from %appdata%\SAS\EnterpriseGuide\x.x.
For instructions on starting and stopping logging in SAS Enterprise Guide 4.1, see SAS Note 47873: "Turning on logging in SAS® Enterprise Guide® 4.1."


Operating System and Release Information


Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise GuideMicrosoft Windows 2000 Professional4.19.1 TS1M3 SP1
Microsoft Windows XP Professional4.19.1 TS1M3 SP1
Microsoft Windows NT Workstation4.19.1 TS1M3 SP1
Microsoft® Windows® for x644.2
Microsoft Windows Server 2003 Datacenter Edition4.2
Microsoft Windows Server 2003 Enterprise Edition4.2
Microsoft Windows Server 2003 Standard Edition4.2
Microsoft Windows Server 2003 for x644.2
Microsoft Windows Server 20084.2
Microsoft Windows Server 2008 for x644.2
Windows 7 Enterprise 32 bit4.2
Windows 7 Enterprise x644.2
Windows 7 Home Premium 32 bit4.2
Windows 7 Home Premium x644.2
Windows 7 Professional 32 bit4.2
Windows 7 Professional x644.2
Windows 7 Ultimate 32 bit4.2
Windows 7 Ultimate x644.2
Windows Millennium Edition (Me)4.2
Windows Vista4.2
Windows Vista for x644.2

SAS BI server performance Monitoring

A practical Approach to Solving Performance Problems with the SAS system

Solving SAS Performance Problems: Employing Host based tools


_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546


Friday, March 15, 2013

All SAS procedures by Name

http://support.sas.com/documentation/cdl/en/allprodsproc/63883/HTML/default/viewer.htm#procedures.htm

SAS Procedures by Name

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | SAS Procedures by Product

A



Procedure
Location of Procedure Documentation
SAS/ACCESS for Relational Databases: Reference
SAS/ACCESS Interface to ADABAS: Reference
SAS/ACCESS Interface to CA-Datacom/DB: Reference
SAS/ACCESS(R) 9.3 Interface to IMS: Reference
SAS/ACCESS Interface to PC Files: Reference
SAS/ACCESS Interface to SYSTEM 2000: Reference
SAS/STAT User's Guide
SAS/Genetics User's Guide
SAS/QC User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/IntrNet: Application Dispatcher
SAS/ETS User's Guide
SAS/ETS User's Guide

B



Procedure
Location of Procedure Documentation
SAS Companion for z/OS
SAS/OR User's Guide: Bill of Material Processing
SAS/STAT User's Guide
SAS/Genetics User's Guide
SAS/AF Procedure Guide

C



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS/ACCESS Interface to R/3: User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/QC User's Guide
SAS/Genetics User's Guide
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/STAT User's Guide
SAS CDISC Procedure: User's Guide
SAS CDISC Procedure: User's Guide
Base SAS Procedures Guide
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/OR User's Guide: Constraint Programming
SAS/STAT User's Guide
Base SAS Procedures Guide
COMPILE
See SAS Risk Dimensions: Procedures Guide
SAS/ETS User's Guide
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
See SAS/ETS User's Guide
Base SAS Procedures Guide
Base SAS Procedures Guide: Statistical Procedures
SAS/STAT User's Guide
SAS/ETS User's Guide
SAS/OR User's Guide: Project Management
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/QC User's Guide
SAS/ACCESS for Relational Databases: Reference

D



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/ETS User's Guide
SAS/ACCESS for Relational Databases: Reference
SAS/ACCESS for Relational Databases: Reference
SAS National Language Support (NLS): Reference Guide
SAS/ACCESS Interface to PC Files: Reference
SAS Companion for z/OS
SAS/ACCESS for Relational Databases: Reference
SAS/ACCESS Interface to PC Files: Reference
SAS/ACCESS Interface to SYSTEM 2000: Reference
SAS/ACCESS Interface to PC Files: Reference
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS Data Quality Server Reference
SAS Data Quality Server Reference
SAS Data Quality Server Reference
DOCPARSE
See the SAS Text Miner Help
SAS Output Delivery System: User's Guide
SAS/CONNECT User's Guide
SAS Data Quality Server Reference
SAS Data Quality Server Reference
SAS/OR User's Guide: Project Management

E



Procedure
Location of Procedure Documentation
SAS/ETS User's Guide
SAS/ETS User's Guide
SAS/ETS User's Guide
SAS documentation on support.sas.com
Base SAS Procedures Guide

F



Procedure
Location of Procedure Documentation
SAS/QC User's Guide
SAS/STAT User's Guide
SAS/Genetics User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS Companion for z/OS
SAS/ETS User's Guide
Base SAS Procedures Guide
SAS Companion for z/OS
SAS documentation on support.sas.com
Base SAS Procedure's Guide: Statistical Procedures
SAS/STAT User's Guide
SAS/FSP Procedures Guide
SAS/FSP Procedures Guide
SAS/FSP Procedures Guide
Base SAS Procedures Guide
SAS/FSP Procedures Guide

G



Procedure
Location of Procedure Documentation
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/OR User's Guide: Local Search Optimization
SAS/STAT User's Guide
SAS/GRAPH: Reference
SAS/OR User's Guide: Project Management
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/Genetics User's Guide
SAS/STAT User's Guide
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GIS: Spatial Data and Procedure Guide
SAS/GRAPH: Reference
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
SAS/GRAPH: Reference
Base SAS Procedures Guide
SAS/GRAPH: Reference
SAS/GRAPH: Reference

H



Procedure
Location of Procedure Documentation
SAS/Genetics User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS High-Performance Forecasting: User's Guide
SAS/STAT: User's Guide
SAS/Genetics User's Guide
Base SAS Procedures Guide

I



Procedure
Location of Procedure Documentation
SAS/IML User's Guide
Base SAS Procedures Guide
SAS/Genetics User's Guide
SAS/STAT User's Guide
Base SAS Guide to Information Maps
SAS/OR User's Guide: Mathematical Programming Legacy Procedures
IOMOPERATE
SAS Intelligence Platform: Application Server Administration Guide on support.sas.com
SAS/QC User's Guide
SAS Companion for z/OS

J



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide

K



Procedure
Location of Procedure Documentation
SAS/STAT User's Guide
SAS/STAT User's Guide

L



Procedure
Location of Procedure Documentation
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/OR User's Guide: Mathematical Programming Legacy Procedures

M



Procedure
Location of Procedure Documentation
SAS/QC User's Guide
SAS/GRAPH: Reference
SAS/STAT User's Guide
SAS/ETS User's Guide
MDDB
See SAS/MDDB Server Help in SAS Help and Documentation
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS Language Interfaces to Metadata
SAS Language Interfaces to Metadata
SAS Language Interfaces to Metadata
SAS/STAT User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
SAS/QC User's Guide
SAS/QC User's Guide

N



Procedure
Location of Procedure Documentation
SAS/STAT User's Guide
SAS/OR User's Guide: Project Management
SAS/OR User's Guide: Mathematical Programming Legacy Procedures
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/OR User's Guide: Mathematical Programming Legacy Procedures
SAS/STAT User's Guide

O



Procedure
Location of Procedure Documentation
SAS OLAP Server: User's Guide
SAS OLAP Server: User's Guide
SAS/SHARE User's Guide
SAS/QC User's Guide
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
Base SAS Procedures Guide
SAS/OR User's Guide: Mathematical Programming
SAS/OR User's Guide: Mathematical Programming
SAS/OR User's Guide: Mathematical Programming
SAS/OR User's Guide: Mathematical Programming
Base SAS Procedures Guide
SAS/STAT User's Guide

P



Procedure
Location of Procedure Documentation
SAS/ETS User's Guide
SAS/QC User's Guide
SAS/ETS User's Guide
SAS Companion for z/OS
SAS Companion for z/OS
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS/OR User's Guide: Project Management
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS Companion for z/OS
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS/STAT User's Guide
Base SAS Procedures Guide
Base SAS Procedures Guide
Base SAS Procedures Guide
SAS/Genetics User's Guide
Base SAS Procedures Guide

Q



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
SAS/ACCESS Interface to SYSTEM 2000: Reference

R



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
RDC
SAS Risk Dimensions: Procedures Guide
RDPOOL
SAS Risk Dimensions: Procedures Guide
RDSEC
SAS Risk Dimensions: Procedures Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS Companion for z/OS
SAS/QC User's Guide
Base SAS Procedures Guide
RISK
SAS Risk Dimensions: Procedures Guide
SAS/STAT User's Guide
SAS/STAT User's Guide

S



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/SHARE User's Guide
SAS/ETS User's Guide
SAS ODS Graphics: Procedures Guide
SAS ODS Graphics: Procedures Guide
SAS ODS Graphics: Procedures Guide
SAS ODS Graphics: Procedures Guide
SAS ODS Graphics: Procedures Guide
SAS/QC User's Guide
SAS/STAT User's Guide
SAS/ETS User's Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
Base SAS Procedures Guide
SAS Companion for UNIX Environments
SAS Companion for Windows
SAS Companion for z/OS
SAS Companion for z/OS
SAS/ETS User's Guide
SAS SQL Procedure User's Guide
SAS/ETS User's Guide
Base SAS Procedures Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS Stored Processes: Developer's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/ETS User's Guide

T



Procedure
Location of Procedure Documentation
Base SAS Procedures Guide
SAS Companion for z/OS
SAS Companion for z/OS
SAS/ETS User's Guide
SAS Output Delivery System: User's Guide
SAS Output Delivery System: User's Guide
SAS Output Delivery System: User's Guide
SAS Output Delivery System: User's Guide
SAS Output Delivery System: User's Guide
SAS Output Delivery System: User's Guide
SAS/ETS User's Guide
Base SAS Procedures Guide
SAS/ETS User's Guide
SAS/STAT User's Guide
Base SAS Procedures Guide
SAS/STAT User's Guide
SAS National Language Support (NLS): Reference Guide
SAS/STAT User's Guide
SAS/ETS User's Guide
SAS/STAT User's Guide

U



Procedure
Location of Procedure Documentation
SAS/ETS User's Guide
Base SAS Procedure's Guide: Statistical Procedures
SAS/CONNECT User's Guide

V



Procedure
Location of Procedure Documentation
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/STAT User's Guide
SAS/ETS User's Guide

X



Procedure
Location of Procedure Documentation
SAS/ETS User's Guide
SAS/ETS User's Guide
Base SAS Procedures Guide
_____________________________________________________________________
Dan Strickland
Inland Fisheries Division
Texas Parks and Wildlife
3407-A S.Chadbourne Street
San Angelo, TX  76903

Phone:  512-666-4546