SASPairs:
Genetic modeling in SAS

Alexander Calder, Black Widow

 

Update SASPairs when a new version of SAS is installed

 

Background

If you use SASPairs in batch mode and if you have updated SAS to a new edition, then you must change a SAS macro name used by SASPairs. In Windows systems, this macro name gives the full path to the SAS executable file (sas.exe). In Unix/Linux, it gives the command that starts SAS.

 

Instructions:

  1. Locate your autoexec.sas file (how do I do this?).
  2. Make a backup of this file.
  3. Use a text editor to edit the autoexec.sas file.
  4. Find the statement from the last installation of SASPairs that starts with
    "%let SASEXE_File="
    In Windows systems, this statement gives the full path to the file that starts SAS (sas.exe). In Unix/Linux, it gives the command to start SAS. This statement is shown in red in the example autoexec.sas file given below for a Windows system.
  5. WINDOWS USERS: Change the path to the new sas.exe file to reflect the new installation. For example, if the new sas.exe file is located in C:\Programs Files\SAS\SAS 9.1\sas.exe, then change the term C:\Program Files\SAS Institute\SAS\V8\sas.exe in the red statement in the example below to reflect the new path.
  6. UNIX/LINUX USERS: Change the command for invoking SAS to the one that invokes the new version. For example, if the command "sas" invoked the previous version, but the command "sas9" invokes the new version, then change
    %let SASEXE_File=sas;
    to
    %let SASEXE_File=sas9;
    NOTE: This command is often set by a system administrator, so check with that person if you have questions.

 

 

Example autoexec.sas file.
NOTE: some of the pathnames and SAS commands are long and may wrap or be cut off depending on your browser settings.

/* --- file C:\autoexec.sas created on 15OCT2003 --- */
 options nocenter;
 libname nmtdir "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\National Merit Twins";
 libname wudir "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\wutwins";
 libname library "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\wutwins";
 /* --- the following lines were added by macro saspairs_setup_autoexec on 23SEP04 --- */
 libname saspairs "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs";
 libname spimlsrc "C:\Documents and Settings\gregory carey\My Documents\My SAS  Files\V8\SASPairs\SASPairs_IML_Source";
 libname spmdslib "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_MDS_Library" ;
 libname sproject "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_Sproject" ;
 libname spothstf "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_OtherStuff" ;
 libname spguilib "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_GUI" ;
 libname spguihlp "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_GUI\SASPairs_GUI_Help" ;
 options SASAUTOS=(SASAUTOS, "C:\Documents and Settings\gregory carey\My Documents\My SAS Files\V8\SASPairs\SASPairs_Macros");
 options mautosource multenvappl;
 %let SASEXE_File = C:\Program Files\SAS Institute\SAS\V8\sas.exe;
 /* --- end of lines added by macro saspairs_setup_autoexec on 23SEP04 --- */