The University of Michigan version of Search is currently available for personal computers using the Microsoft Windows and Linux operating systems. The SAS implementation requires SAS 6.12 or higher.
We will assume that SAS is installed in directory \\programs\sas and that Search is to be installed in directory \\programs\srclib. If this is not the case, substitute the appropriate names in what follows. The network administrator should:
1. Create the \\programs\srclib directory, copy the search_sas_windows.zip file into the directory, and unzip it with Winzip or another zip utility.
2. Edit the SAS 6.12 Config.sas, SAS 8 Sasv8.cfg or SAS 9 Sasv9.cfg configuration file found in the \\programs\sas directory to include the following lines in the user section, just above the warning "Install application edits below this line. User options should be added above this box comment."
-set SRCLIB "\\programs\srclib"
-sasautos (!SRCLIB sasautos)Advise users to download the edited configuration file and to set the -config parameter in their command line invoking SAS to point to it. The command line is usually a property of an icon or shortcut.
If users prefer not to use the edited configuration file, they can run Search by submitting the following line after they open SAS:
options set = SRCLIB "\\programs\srclib" sasautos = ('!SRCLIB' sasautos) mautosource;
3. To verify that Search is installed correctly, copy the search_sas_example.zip file into a work directory and unzip it with Winzip or another zip utility. Run the search_examples_command.sas file from a command line or the SAS Enhanced Editor or the search_examples_editor.sas file from the SAS Program Editor, changing the current directory to the one in which the example files were unzipped. The SAS compare procedure at the end of the run should indicate that the expected and actual output datasets are identical.
We will assume that Search is to be installed in directory "C:\Program Files\Srclib". If this is not the case, substitute the appropriate name in what follows. The user should:
1. Create the "C:\Program Files\Srclib" directory, copy the search_sas_windows.zip file into the directory, and unzip the file with Winzip or another zip utility.
2. Locate the SAS 6.12 Config.sas, SAS 8 Sasv8.cfg or SAS 9 Sasv9.cfg configuration file controlling your SAS runs. This is usually set by the -config parameter in the command line invoking SAS, which is usually a property of an icon or shortcut. If the file is a network file, you will need to copy it to a local file and alter the -config parameter in the command line invoking SAS to point to it.
Edit the configuration file to include the following lines in the user section, just above the warning "Install application edits below this line. User options should be added above this box comment."
-set SRCLIB "C:\Program Files\Srclib"
-sasautos (!SRCLIB sasautos)If you prefer not to edit the configuration file, you can run Search by submitting the following line after you open SAS:
options set = SRCLIB "C:\Program Files\Srclib" sasautos = ('!SRCLIB' sasautos) mautosource;
3. To verify that Search is installed correctly, copy the search_sas_example.zip file into a work directory and unzip it with Winzip or another zip utility. Run the search_examples_command.sas file from a command line or the SAS Enhanced Editor or the search_examples_editor.sas file from the SAS Program Editor, changing the current directory to the one in which the example files were unzipped. The SAS compare procedure at the end of the run should indicate that the expected and actual output datasets are identical.
Notice to SAS 7+ users: The SAS Enhanced Editor cannot be used when running IVEware with the "setup=new" option. The Program Editor must be used instead.
IVEware will block attempts to use the "setup=new" option with the Enhanced Editor, if it can identify them. SAS 7 and 8 provide no way to determine which editor is being used. SAS 9 provides a way to identify setups opened or saved in the Enhanced Editor, but not setups merely run from it. If the Enanced Editor has never been used, the test for this will produce a harmless message: "WARNING: The argument to macro function %SYSGET is not defined as a system variable."
If you use the Enhanced Editor by mistake and IVEware fails to catch it, SAS may crash or become unstable. If it doesn't crash immediately, you should shut it down and start over.To open the SAS Program Editor click on View on the Toolbar and then click Program Editor.
To make the Program Editor your default editor, either include "-noenhancededitor" in the SAS invocation or do the following:
1. Click on Tools on the SAS Toolbar, then
2. Click on Options, then
3. Click on Preferences, then
4. Click on the Edit tab, then
5. Remove the check in the box labeled "Use Enhanced Editor," then
6. Click on OK.
We will assume that SAS is installed in directory /opt/local/sas and that Search is to be installed in directory /opt/local/srclib. If this is not the case, substitute the appropriate names in what follows. The system administrator should:
1. Create the /opt/local/srclib directory, copy the appropriate .tgz file into the directory, and unzip and untar the file with gzip or another zip utility.
2. Edit the SAS 6.12 config.sas, SAS 8 sasv8.cfg or SAS 9 sasv9.cfg configuration file found in the /opt/local/sas directory to include the following lines:
-set SRCLIB /opt/local/srclib
-sasautos ('!SRCLIB' '!SASROOT/sasautos')If you prefer not to edit the configuration file, users can run Search by creating an autoexec.sas file in the directory from which they run SAS (if it doesn't already exist) and editing it to include the following line(s):
For SAS 6.12:
x'setenv SRCLIB /opt/local/srclib';
options sasautos = (SRCLIB '!SASROOT/sasautos') mautosource;For SAS 8 or 9:
options set = SRCLIB '/opt/local/srclib' sasautos = ('!SRCLIB' '!SASROOT/sasautos') mautosource;
Users who prefer not to edit the autoexec.sas file can run Search by submitting the line(s) after they open SAS.
3. To verify that Search is installed correctly, copy the search_sas_example.tgz file into a work directory and unzip and untar it. Run the search_examples_command.sas file from a command line or the search_examples_editor.sas file from the SAS Program Editor, changing the current directory to the one in which the example files were unzipped. The SAS compare procedure at the end of the run should indicate that the expected and actual output datasets are identical.
We will assume that Search is to be installed in directory ~/srclib. If this is not the case, substitute the appropriate name in what follows. The user should:
1. Create the ~/srclib directory, copy the appropriate .tgz file into the directory, and unzip and untar the file with gzip or another zip utility.
2. Create a file autoexec.sas in the directory from which you run SAS (if it doesn't already exist) and edit it to include the following line(s):
For SAS 6.12:
x'setenv SRCLIB ~/srclib';
options sasautos = (SRCLIB '!SASROOT/sasautos') mautosource;For SAS 8 or 9:
options set = SRCLIB '~/srclib' sasautos = ('!SRCLIB' '!SASROOT/sasautos') mautosource;
If you prefer not to edit the autoexec.sas file, you can run Search by submitting the line(s) after you open SAS.
3. To verify that Search is installed correctly, copy the search_sas_example.tgz file into a work directory and unzip and untar it. Run the search_examples_command.sas file from a command line or the search_examples_editor.sas file from the SAS Program Editor, changing the current directory to the one in which the example files were unzipped. The SAS compare procedure at the end of the run should indicate that the expected and actual output datasets are identical.
Please report bugs or send comments via e-mail to Peter Solenberger.
Last updated 2 August 2007