installation instructions for version 8 (ts m1) of the sas system … · 2007. 10. 24. · page 2...

i

Installation Instructions forVersion 8 (TS M1) of the SAS® System for

Microsoft® Windows®

Table of Contents

Chapter 1, Introduction......................................................................................................1Terminology and Symbols Used in this Document................................................................1

SASROOT Directory ..............................................................................................1Types of Installation Configurations .......................................................................1

Pre-installation Checklist .....................................................................................................2Proper Handling of Your Media ...........................................................................................3SAS Setup Help for Installing the SAS System.....................................................................3Online Help for Using the SAS System.................................................................................3

The Help System.....................................................................................................4HTML Viewer ........................................................................................................4

Exiting SAS Setup................................................................................................................4Additional Documentation....................................................................................................4

Chapter 2, Installing the SAS® System .............................................................................5Before Starting SAS Setup....................................................................................................6Starting the SAS System Installation Process........................................................................8Installation Scenario Examples.............................................................................................9

Performing a Complete Personal Installation..........................................................9Performing a Custom Personal Installation...........................................................10Performing a Client Installation............................................................................11Performing a Complete File Server Installation ....................................................12Performing a Custom File Server Installation .......................................................13

Chapter 3, Applying Updates to the SAS® System V8...................................................17Before Starting SAS Setup..................................................................................................17Starting the SAS System Update Process ............................................................................18Example Update Scenarios .................................................................................................19

Updating a Local SAS Version 8 Installation ........................................................19Updating a SAS Version 8 Server and Subsequent Clients ....................................19

Chapter 4, Invoking the SAS® System ............................................................................23

Chapter 5, Technical Support Services............................................................................25TSNEWS-L Mail and File List ...........................................................................................25Anonymous FTP.................................................................................................................25Electronic Fax Service........................................................................................................26

ii

Appendix A, Installing SAS/ACCESS® Interface to ODBC Software ........................... 27SAS/ACCESS ODBC Conversion Utilities......................................................................... 28

AS/400 Users........................................................................................................ 28Microsoft SQL Server Users ................................................................................. 29

Appendix B, Installing SAS/ACCESS® Interface to ORACLE Software ...................... 31Client-Server Architecture.................................................................................................. 31Installing SQL*Net (or Net8) ............................................................................................. 32Assigning the Default Path for the ORACLE Server........................................................... 32

Windows NT ........................................................................................................ 32Windows 95 and Windows 98............................................................................... 33

Appendix C, Installing SAS/ACCESS® Interface to R/3® Software.............................. 35SAS/ACCESS Interface to R/3 Software............................................................... 35

Appendix D, Post-Installation Setup for SAS/ASSIST® Software.................................. 37Adding a Master Profile ..................................................................................................... 37

Appendix E, Post-Installation Setup for SAS/CONNECT® Software ............................ 39Storing and Locating SAS/CONNECT Script Files ............................................................ 39System Configuration for Access Methods Supported under Windows 95 and Windows 98 40

EHLLAPI ............................................................................................................. 40DECNET.............................................................................................................. 40NETBIOS............................................................................................................. 40TCP/IP ................................................................................................................. 40APPC ................................................................................................................... 40

System Configuration for Access Methods Supported under Windows NT.......................... 41EHLLAPI ............................................................................................................. 41DECNET.............................................................................................................. 41

Network Drive Restrictions ..................................................................... 41Security Considerations........................................................................... 41

NETBIOS............................................................................................................. 42TCP/IP ................................................................................................................. 42APPC ................................................................................................................... 42

Configuring the SAS Windows Spawner Program.............................................................. 42Using Encryption with the Spawner...................................................................... 43

Appendix F, Post-Installation Setup for SAS/EIS® Software ......................................... 45

Specifying the System Repository Manager Location.......................................................... 45Setting Up the System Repository Manager Files................................................................ 46Setting Up the SASHELP Repository.................................................................................. 46Converting Existing SAS/EIS Metabases............................................................................ 46

iii

Appendix G, Post-Installation Setup for SAS/GRAPH® Software .................................47ContourApplet (ctrapp.jar)....................................................................................47GraphApplet (graphapp.jar)..................................................................................47MapApplet (mapapp.jar and related map data jar files) .........................................47MetaViewApplet (metafile.zip) .............................................................................47RangeViewApplet (rvapplet.jar)............................................................................47SAS/GRAPH Control for ActiveX ........................................................................48

Client Components.............................................................................................................48

Appendix H, Installing SAS Integration Technologies ....................................................49Client Components.............................................................................................................49

Integration Technologies Documentation..............................................................49Java Client Development and Runtime Component...............................................49Windows Client Development and Runtime Component .......................................49Integration Technologies Administrator................................................................49SAS Package Reader.............................................................................................49Subscription Manager...........................................................................................49

Client Component Delivery ................................................................................................50

Appendix I, Installing SAS/IntrNet® Software ...............................................................51Introduction........................................................................................................................51Installing SAS/IntrNet Web Server or Client Components..................................................51Configuring SAS/IntrNet Components ...............................................................................51Updates to Components and Documentation.......................................................................51

Appendix J, Post-Installation Setup for SAS/MDDB Server® Software ........................53

Appendix K, Setting Up the SAS® ODBC Driver...........................................................55Installing the SAS ODBC Driver........................................................................................55

Technical Support.................................................................................................56

Appendix L, Post-Installation Setup for SAS® OLAP Server Software ........................57Setting up Access Control without SAS/EIS Software on Your Server ................................57

Starting the Access Control Setup Dialog Window................................................57Setting Your Access Control Key and Environment Programmatically..................57Doing Your Access Control Definitions (Users, Groups, ACL) Programmatically.60Write Access to SASHELP.AC and SASHELP.MB ..............................................69

Specifying OLAP Classes ...................................................................................................69

Appendix M, Installing SAS/SECURE

Software..........................................................71SAS/SECURE Client for Windows.....................................................................................71SAS/SECURE Client for Java.............................................................................................71Client-Side Components CD...............................................................................................71

iv

Appendix N, Updating Your SAS® System SETINIT..................................................... 73

Using the Update SAS V8 Product Authorization Icon ....................................................... 73Updating Your SAS SETINIT during Installation of the SAS System................................. 75Executing From the Command Line................................................................................... 75

Expired Product Authorization ............................................................................. 76

Appendix O, Post-Installation Setup for SAS/SHARE® Software.................................. 77Selecting a Communications Access Method...................................................................... 77System Configuration for the NETBIOS Access Method .................................................... 79System Configuration for the APPC Access Method........................................................... 79System Configuration for the TCP/IP Access Method......................................................... 79

Software Requirements ......................................................................................... 79Define server names in the TCP/IP SERVICES file................................. 79

System Configuration for the DECNET Access Method ..................................................... 80Client-Side Components..................................................................................................... 80

SAS/SHARE Data Provider .................................................................................. 80SAS ODBC Driver ............................................................................................... 80SAS/SHARE Driver for JDBC.............................................................................. 81SAS/SHARE SQL Library for C ........................................................................... 81

Appendix P, Using Silent Setup........................................................................................ 83Recording an Installation ................................................................................................... 83

Record Mode Options ........................................................................................... 83Playing Back an Installation............................................................................................... 84

Troubleshooting.................................................................................................... 84Recording External Setups.................................................................................... 84

Appendix Q, System Management Server....................................................................... 85Options for Silent Setup when Installing via SMS .............................................................. 85Using Package Definition Files (PDF) ................................................................................ 86

PDF for the SAS System....................................................................................... 86

Federal Government Rights Notice.................................................................................. 89

Glossary ............................................................................................................................ 91

1

Chapter 1, Introduction

This document provides the instructions for installing Version 8 (TS M1) of the SASSystem under Windows, Windows NT, and Windows NT Server. Please read theseinstructions before you attempt to install any Version 8 SAS software component inthe Windows environment.

Terminology and Symbols Used in this Document

As you use these installation instructions, you will encounter terminology withwhich you may not be familiar. The following terms are specific to your SAS Systeminstallation and are provided here to facilitate the installation process. Please lookfor other unfamiliar terms in the glossary at the end of this document.

SASROOT Directory

This directory is also referred to as destination. It is the directory where youinstall the SAS System. The CORE directory and several predefinedsubdirectories are created under the SASROOT directory. For mostinstallations, you may choose any directory as the SASROOT directory for theSAS System, but for a server installation, you must not specify the root level of adrive or a subdir that will be used as a network share.

The following are examples of valid SASROOT directories:

• C:\SAS• D:\SAS_WIN• E:\SAS\APPS

For the examples in this manual, the SASROOT directory always appears asSASROOT.

Types of Installation Configurations

The SAS System Setup is targeted at two different types of users. First and mostcommon are individuals who wish to install the SAS System for their own personaluse. The Setups related to this type of installation are referred to as Personal andClient installs.

The second targeted user type is usually network administrators who want to installthe SAS System to a centralized server. Other users are expected to perform theirrespective installations using the server’s shared image. This type of installation ona centralized server is referred to in this documentation as a Server install.

Installation Instructions for the SAS System for Microsoft Windows

q Installing the SAS System for Personal Use

Most users will choose to perform a Personal installation for their individualuse. This type of installation was designed to copy the SAS System programfiles onto the user’s local hard drive. A Personal install renders a fullyoperational SAS System and provides optimal performance.

q Installing the SAS System as a Client

The Client type of installation is used to run the SAS System on a PC from SASSystem files that are present on a network file server. All of the user’s data ismaintained on their local PC, and the CPU in the user’s PC runs the program,but it relies on an external file source. This configuration preserves drive spaceon the local PC by minimizing the number of files required for programexecution. However, performance may be reduced due to access time issueswhen an operation calls upon external file sources.

q Installing SAS onto a File Server

A network administrator may install the SAS System onto a file server. Fromthat location, the SAS System can be installed onto a PC using either thePersonal or Client installations described above. The SAS System created usinga Server install may be directly executed if the administrator of the file serverchooses to install the SAS System as an Application Server. This option isavailable at the time of installation. The destination chosen on the networkserver must not be at the root level of a drive or a subdir that will be used as anetwork share.

The following icon is used throughout this document to identify a particular type ofinformation:

4 The CHECKMARK symbol indicates a set of items that should beverified before proceeding with the installation.

Pre-installation Checklist

Before you begin installing the SAS System, make sure you review the followingchecklist and perform the tasks requested. Once you have completed the checklist,turn to the section appropriate for your installation.

4 Review all the items in your product package.

4 Make sure your hardware meets the specifications indicated on the SystemRequirements sheet contained in your installation package.

4 Verify the release of Windows you are running. Version 8 of the SAS Systemrequires Windows NT, Version 4.0 or later, or Windows 95 or later. Refer tothe System Requirements document for a detailed description of operatingsystem requirements.

Installation Instructions for the SAS System for Microsoft Windows Page 3

4 Read the FEDGOVT.TXT file (U.S. Federal Government employees only).This file is located on the CD-ROM in the \sas directory.

Unless otherwise noted, your product package from SAS Institute contains all theitems listed in the Transmittal Letter. The product package is shipped to the SASInstallation Representative at your site. If you think any items are missing from yourpackage, contact your SAS Installation Representative, who in turn may need tocontact SAS Institute.

Proper Handling of Your Media

Before you begin your installation, review the following tips for proper handling ofyour SAS System CD-ROM.

• Clean the CD and the CD drives regularly with head cleaning kits• Return your CD to its protective packaging when not in use.

SAS Setup Help for Installing the SAS System

The online help should be considered the primary source of installation instructionsand should be consulted for assistance prior to and during the installation process.It contains a number of helpful installation examples.

The online help also contains useful information for administrators, such as how theSAS System handles the Windows registry, operating Silent Setup, Silent Setupsupport for System Management Server, and other topics.

The installation program provides online help for you to use at any point during theinstallation. The help is provided in a native Windows environment. To access theonline help, select the Help button or F1 at any time while the SAS Setup programis running. The Help button is available in the lower right corner of your screen inthe SAS Setup program.

Online Help for Using the SAS System

To take advantage of the latest features in Version 8 (TS MO)of the SAS System, it isstrongly recommended that you install Internet Explorer 5,. This version of InternetExplorer is included on the SAS System media.

You can elect to have SAS Setup install Internet Explorer 5 if it is not already onyour PC. This installation does not modify your desktop and will not change yourdefault Web browser. You will have the option of removing this release of InternetExplorer and returning to your previous release (if one was previously installed) bymeans of the Add/Remove Programs menu option in the Windows Control Panel.The new SAS System features described below make use of features in this releaseof Internet Explorer.


The Help System

The recommended and highest quality Help System takes advantage of Microsoft’sHTMLHelp technology. This new technology provides advanced search capabilities,easier indexing and compressed files that consume less disk space. (Should youchoose not to take advantage of Microsoft’s HTMLHelp technology, simple HTMLhelp is installable and is viewable through any Web browser.)

HTML Viewer

When generating HTML output using the SAS System, you will have the ability toview output in the format of HTML from within a SAS System window. WithoutInternet Explorer, you will still be able to create output in HTML format, but youwill have to use an external browser to view the results.

Exiting SAS Setup

At any time while SAS Setup is running, you can select Cancel or press the F3 keyto terminate the installation. SAS Setup will terminate after removing any files thathave been installed.

If you are installing SAS over an existing SAS System and you exit SAS Setupprematurely, you may jeopardize the integrity of the existing SAS System.

Additional Documentation

For additional information, refer to the SAS OnlineDoc CD in your package for acomplete library of SAS software documentation.

5

Chapter 2, Installing the SAS® System

Chapter 2 provides an introduction to installing the SAS System for Windows, TSM1, on a machine where the SAS System, TS M0, is not currently installed. Once theinstallation process described in this chapter is finished, the process described inChapter 3 should be used to apply the TS M1 update. If the TS M0 system is alreadyinstalled, you should skip to Chapter 3 to apply the update.

Information in this chapter will assist you in making some decisions prior to startingthe installation process, and installation scenario examples are included. A morecomplete set of installation scenario examples is provided in the online helpprovided in the SAS System Setup program (referred to as SAS Setup in theseinstructions). To access the online help, press F1 or click the Help icon once SASSetup is running.

SAS Setup should be run during an initial SAS System installation and when you areadding additional components to an existing SAS System installation. If you have anexisting installation of a previous version of the SAS System, SAS Setup will allowyou to continue to have that version of the SAS System registered, or it will allowyou to register Version 8 of the SAS System.

If a previous version of the SAS System is found and SAS Setup determines that fileextensions are registered to that release, a dialog will be presented to allow you toselect to which release you want to register file extensions. If you select a previousrelease, existing SAS registry entries will not be changed.

You can use SAS Setup to perform three types of installation configurations:

• Complete• Client• Custom

A Complete installation provides a SAS System containing all components your sitehas registered. Within the Complete category, you may perform either a Setup toyour local machine or to a fileserver that other users may use as a source of eitherPersonal or Client installs. The option of installing the SAS System on a file server isintended for network administrators who wish to install the SAS System at a centrallocation so it can be shared with others via the network. The most commoninstallation method is for personal use and will provide optimal performance.

The Client installation allows the SAS System to be run from a network location witha minimum of space required on the local machine.

A Custom installation provides a SAS System containing only SAS components thatyou have selected and that your site has registered. Within the Custom category,you may perform either a Setup to your local machine or to a fileserver that other


users may use as a source of either Personal or Client installs. The option ofinstalling the SAS System on a file server is intended for network administratorswho wish to install the SAS System at a central location so it can be shared withothers via the network.

Before Starting SAS Setup

Before you start SAS Setup, ensure that you have sufficient disk space on theinstallation target. Refer to the System Requirements document for descriptions of theamount of space needed to install each component of the SAS System. Keep in mindthat the disk-blocking factor and drive compression settings may affect the actualamount of required space. If sufficient space is available, a Complete Personalinstallation will provide the best performance.

Complete the following steps:

1. Decide where the user files should be stored during execution of the SASSystem. The default for the SASUSER library is the following location:

q On Windows NT\Profiles\\Personal\My SAS Files\V8

q On Windows 95 and Windows 98\My SAS Files\V8

SAS Setup will allow you to change the location of the SASUSER library. Pleasenote that the default provides a unique SASUSER library for each user on aWindows NT system.

2. Choose a location for the SAS System temporary work file. The default for thework files is the following location:

%TEMP\SAS Temporary Files

3. If you want to use an alternative location for the work files, SAS Setup willallow you to do so.

4. If you are installing to a Windows NT, Version 4.0 system, SAS Setup willdetermine whether you have the required Windows NT, Version 4.0, ServicePack installed. Make sure you install it before running SAS Setup. Without thisService Pack, SAS Setup will not present the option of installing InternetExplorer. See the System Requirements to determine the Service Packrequirement.

5. SAS Setup will determine whether Microsoft Internet Explorer Version 5 isinstalled. If it is not installed, SAS Setup will give you the option of installing it.It is strongly recommended that you do so. On Windows NT, systemsadministrative privileges are required to install Internet Explorer. If you do notinstall Internet Explorer, you must have a Web browser installed. The Web


browser should be installed prior to running SAS Setup. Refer to the SystemRequirements to determine acceptable Web browser requirements.


Starting the SAS System Installation Process

The SAS System is dependent on the presence of several Microsoft components forproper operation. At the beginning of the setup process, Setup will examine yoursystem and determine which updates are necessary. Setup will then assist you withupgrading these components by installing them. Many of the components mayrequire a reboot. If a reboot is required, Setup will automatically continue after yoursystem has restarted and you have logged in.

While rebooting is necessary to ensure the stability of your system, you canminimize the number of reboots required by closing all non-essential Windowsapplications before starting Setup.

To start the SAS System installation process, complete the following steps:

1. Insert the CD-ROM labeled “Disk 1” into the source drive. The SAS SystemAutoPlay should appear if AutoPlay is enabled on your computer. If this doesnot happen, select the Run menu option from the Start menu and type:

:\SETUP

where is the drive containing the SAS System installationmedia.

2. At this point, there are a number of choices:

q The SAS System may be installed by selecting the SAS System Setupoption on this startup screen.

q The installation instructions may be viewed on your screen in PortableDocument Format (.PDF) using Adobe Acrobat Reader. If this software isnot installed on your computer, you will be prompted to install it.

q SAS Viewer can be installed by selecting SAS Viewer Setup .

q SAS ODBC Driver can be installed by selecting SAS ODBC Driver Setup .

q Selecting Browse the CD will launch a Microsoft Explorer window. Thedefault display shows the root directory of the CD or other source media ifthe image has been copied.


Installation Scenario Examples

This section describes the typical steps for each of the following types ofinstallations:

• Complete Personal Installation• Custom Personal Installation• Client Installation• Complete File Server Installation• Custom File Server Installation

Please choose the section that is appropriate for the type of installation you areperforming. The Back buttons on any screen can be used to return to the previousscreen to alter any choices.

Performing a Complete Personal Installation

The following steps are typically followed when performing a Complete Personalinstallation:

1. Carefully read the Welcome screen and then click on Next. To minimizerequired reboots during SAS Setup, it is highly recommended that you exit allother applications while installing the SAS System.

2. Verify that the default setting of Complete setup type is selected and then clickon Next.

3. This dialog is used to decide between a Personal Complete install and a FileServer Complete install. Make sure that No is selected on the Server Optionsdialog. When you are certain the selection is correct, click Next.

4. If this is the first product from SAS Institute you have installed on your system,you will be presented with the SAS Institute Shared Files dialog. It isrecommended that you use the default destination. Once this selection has beenmade, all Shared Files related to the SAS System will be stored in that location.Once you have selected the desired location, click on Next.

5. The Choose Destination Location dialog is now displayed. Carefullyselect the destination for the SAS System. Be sure the destination has sufficientdisk space since you will be installing a complete SAS System. Once you haveselected the location, click on Next.

6. The Select Data Files Folder dialog is now displayed. Either accept thedefault location, or enter the desired location for the user Data FilesFolder. Then, click on Next.

7. The Select Temporary Files Folder dialog is displayed next. Once thedesired location for the SAS work area is displayed, click on Next. For some


types of SAS processing, large files may be used in this location so ensure thatyou have adequate space in the selected location.

8. The SAS Help Options dialog is displayed next. Here you may selectwhether you wish to have Internet Explorer style help or simple HTML help.Setup will suggest a suitable option for your system. When you are pleased withthe selection, click on Next.

9. If necessary, an Additional Installation Options dialog may bedisplayed. Make the desired choices. Online help is available for assistance bypressing F1. When finished, click on Next.

10. The Review Installation Choices dialog is now displayed. Verify thatthe correct choices are displayed. If not, use the Back buttons to step backthrough the dialogs to make any necessary corrections. Once you are satisfiedwith your choices, click on Next.

SAS Setup will now begin copying files and creating the SAS System installation.

Performing a Custom Personal Installation

The following steps are typically followed when performing a Custom Personalinstallation:


2. After SAS Setup finishes initializing, verify that the Custom installation isselected and then click on Next.

3. This dialog is used to decide between a Personal Custom install and a FileServer Custom install. Make sure that No is selected on the Server Optionsdialog. When you are certain the selection is correct, click Next.


5. The Choose Destination Location dialog is now displayed. Carefullyselect the destination for the SAS System. Be sure that the destination hassufficient disk space to install all of the SAS System components. Once thelocation is selected, click on Next.



7. The Select Temporary Files Folder dialog is displayed next. Once thedesired location for the SAS work area is displayed, click on Next. For sometypes of SAS System processing, large files may be used in this location, soensure that you have adequate space in the selected location.

8. The Custom installation component listbox is displayed next. By default, allcomponents are selected. Either deselect the components that are not desired, orclick on the Unselect All button and then individually select the desiredcomponents. SAS Setup will recompute the estimated disk space requirement asyou select or deselect components. When you are finished, click on Next.

9. The SAS Help Options dialog is displayed next. Here you may selectwhether you wish to have Internet Explorer style help or simple HTML help.Setup will suggest a suitable option for your system. When you are satisfiedwith the selection, click on Next.


11. The Select Program Folder dialog is displayed. Choose the folder wherethe SAS System icons are to be installed. Once the desired folder is chosen, clickon Next.

12. Finally, the Review Installation Choices dialog is displayed. Verify thatthe correct choices are displayed. If not, use the Back buttons to step backthrough the dialogs and make any necessary corrections. Once you are satisfiedwith your choices, click on Next.


Performing a Client Installation

The following steps are typically followed when performing a Client installation:


2. After SAS Setup finishes initializing, select the Client installation and thenclick on Next.



4. The Choose Destination Location dialog is now displayed. This locationwill be used for configuration files. Carefully select the desired location andclick on Next.


6. The Select Temporary Files Folder dialog is displayed next. Once thedesired location for the SAS work area is displayed, click on Next. For sometypes of SAS processing, large files may be used in this location so ensure thatyou have adequate space in the selected location.


8. The Select Program Folders dialog is displayed. Choose the folder wherethe SAS System icons are to be installed. Once the desired folder is chosen, clickon Next.

9. Finally, the Review Installation Choices dialog is displayed. Verify thatthe choices displayed are correct. If not, use the Back buttons to step backthrough the dialogs to make any necessary corrections. Once you are satisfiedwith your choices, click on Next.


Performing a Complete File Server Installation

The following steps are typically followed when performing a Complete File Serverinstallation:


2. After SAS Setup finishes initializing, select the Complete installation and clickNext.

3. This dialog is used to decide between a Personal Complete install and a FileServer Complete install. Make sure that Yes is selected on the Server Optionsdialog. When you are certain the selection is correct, click Next.

4. Next, you will be presented with the Enterprise Options dialog, whichallows you to indicate if this machine will be an Application Server. If you donot have an NT Enterprise SETINIT, select No on this dialog. If you select No,only steps 6 and 11 will be displayed.



6. The Choose Destination Location dialog is now displayed. Carefullyselect the destination for the SAS System. Be sure that the destination hassufficient disk space to install all of the SAS System components, and that it isnot at the root level of a drive or of a subdir to be used as a network share.Remember that both help systems will be installed. Once the location is selected,click on Next.



9. The SAS Help Options dialog is displayed next. Here you may selectwhether you wish to have Internet Explorer style help or simple HTML help.Setup will suggest a suitable option for your system. When you are pleased withthe selection, click on Next.


11. Finally, the Review Installation Choices dialog is displayed. Verify thatthe correct choices are displayed. If not, use the Back buttons to step backthrough the dialogs and make any necessary corrections. Once you are satisfiedwith your choices, click on the Next button.

SAS Setup will now begin copying files and creating a re-installable SAS Systemimage. Other users will now be able to run SAS Setup from the re-installable imagejust created and perform either a Client or Personal install.

Performing a Custom File Server Installation

The following steps are typically followed when performing a Custom File Serverinstallation:



2. After SAS Setup finishes initializing, select the Custom installation and clickNext.

3. This dialog is used to decide between a Personal Custom install and a FileServer Custom install. Make sure that Yes is selected on the Server Optionsdialog. When you are certain the selection is correct, click Next.

4. Next, you will be presented with the Enterprise Options dialog, whichallows you to indicate if this machine will be an Application Server. If you donot have an NT Enterprise SETINIT, select No in this dialog. If you select No,only steps 6 and 14 will be displayed.


6. The Choose Destination Location dialog is now displayed. Carefullyselect the destination for the SAS System. Be sure that the destination hassufficient disk space to install all of the SAS System components, and that it isnot at the root level of a drive or of a subdir to be used as a network share.Once the location is selected, click on Next.



9. The Custom installation component listbox is displayed next. By default, allcomponents are selected. Either deselect the components that are not desired, orclick on the Unselect All button and then individually select the desiredcomponents. SAS Setup will recompute the estimated disk space requirement asyou select or deselect components. When you are finished, click on Next.

10. The SAS Help Options dialog is displayed next. Here you may selectwhether you wish to have Internet Explorer style help or simple HTML help.Setup will suggest a suitable option for your system. When you are satisfiedwith the selection, click on Next.



12. The Select Program Folders dialog is displayed. Choose the folder wherethe SAS System icons are to be installed. Once the desired folder is chosen, clickon Next.

13. Finally, the Review Installation Choices dialog is displayed. Verify thatthe correct choices are displayed. If not, use the Back buttons to step backthrough the dialogs and make any necessary corrections. Once you are satisfiedwith your choices, click on Next.

SAS Setup will now begin copying files and creating a re-installable SAS Systemimage. Other users will now be able to run SAS Setup from the re-installable imagejust created and perform either a Client or Personal install.

17

Chapter 3, Applying Updates to theSAS® System V8

This chapter provides an introduction to applying updates to the SAS System V8 forWindows. In addition, information is provided to assist you in making somedecisions prior to starting the installation process and various installation scenarioexamples are included.

The SAS V8 (update-level) Setup (referred to as SAS Setup in these instructions)must only be run if SAS System V8 is installed on your system. If you intend to addadditional Version 8 components to your SAS System, you must first add thesecomponents by installing them from the SAS System V8 media (see Chapter 2,“Installing the SAS System”). Once you are satisfied with the installed components,you may then install the SAS System V8 Update to have them all updated.

Before Starting SAS Setup

Before you start SAS Setup, ensure that you have sufficient disk space on theinstallation target. SAS Setup will provide you the opportunity to backup theoriginal versions of the files to be updated. This backup will require, at most, 170megabytes of disk space. Keep in mind that the disk-blocking factor and drivecompression settings may affect the actual amount of required space. You will notbe required to backup your files if you do not wish to have the ability to revert tothe original SAS System V8.


1. If you are installing to a Windows NT, Version 4.0 system, SAS Setup willdetermine whether you have the required Windows NT, Version 4.0, ServicePack installed. Make sure you install it before running SAS Setup. Without thisService Pack, SAS Setup will not present the option of installing InternetExplorer. See the System Requirements to determine the Service Packrequirement.

2. SAS Setup will determine whether Microsoft Internet Explorer Version 5 isinstalled. If it is not installed, SAS Setup will give you the option of installing it.It is strongly recommended that you do so. On Windows NT, systemsadministrative privileges are required to install Internet Explorer. If you do notinstall Internet Explorer, you must have a Web browser installed. The Webbrowser should be installed prior to running SAS Setup. Refer to the SystemRequirements to determine acceptable Web browser requirements.


Starting the SAS System Update Process

The SAS System is dependent on the presence of several Microsoft components forproper operation. At the beginning of the setup process, Setup will examine yoursystem and determine which updates are necessary. Setup will then assist you withupgrading these components by installing them. Many of the components mayrequire a reboot. If a reboot is required, Setup will automatically continue after yoursystem has restarted and you have logged in.

While rebooting is necessary to ensure the stability of your system, you canminimize the number of reboots required by closing all non-essential Windowsapplications before starting Setup.

To start the SAS System update process, complete the following steps:

1. Insert the CD-ROM labeled Disk 3 into the source drive. The SAS SystemAutoPlay should appear if AutoPlay is enabled on your computer. If this doesnot happen, select the Run menu option from the Start menu and type:

:\SETUP


Note: If you are an administrator and you are updating a file server copy ofthe SAS System Version 8 from a machine other than the one where youoriginally installed the SAS System Version 8, you must provide theforcemaint option on the setup command-line as follows:

:\SAS\SETUP forcemaint

Please see “Updating a SAS Version 8 Server and Subsequent Clients”on page 19 for more information.

2. At this point, there are a number of choices:

q The SAS System Update may be installed by selecting the SAS SystemSetup option on this startup screen.

q The installation instructions may be viewed on your screen in PortableDocument Format (.PDF) using Adobe Acrobat Reader. If this software isnot installed on your computer, you will be prompted to install it.

q SAS Viewer can be installed by selecting SAS Viewer Setup .

q Selecting SAS Version 8 will launch the existing SAS Version 8.


q Selecting Browse the CD will launch a Microsoft Explorer window. Thedefault display shows the root directory of the CD or other source media ifthe image has been copied.

Example Update Scenarios

This section describes the typical steps for each of the following types ofinstallations:

• Updating a Local SAS Version 8 Installation• Updating a SAS Version 8 Server and Subsequent Clients

Please choose the section that is appropriate for the type of update you areperforming. The Back buttons on any screen can be used to return to the previousscreen to alter any choices.

Updating a Local SAS Version 8 Installation

The following steps are typically followed when performing an update to a localSAS System V8 Installation:


2. At this point, you will be presented with a list containing all the componentsinstalled on your system. Review this listing to ensure that all of the productsyou wish to update are installed. Once you have reviewed this information,click on Next.

3. Now you are provided with the opportunity to backup the files that are to beupdated. Backing up these files will provide you the ability to revert back toSAS System V8 by means of the Add/Remove Programs Control Panel. SelectYes if you would like to have the ability to remove this update at a later time. Ifyou do not wish to have this ability, and wish to preserve hard drive space,select No. When you are satisfied with your selection, click on Next.

4. If you selected to perform a backup of the SAS System V8 files to be updated,you will be prompted to enter the location to which these files should be copied.Once you have indicated the desired destination, click Next. If you chose not tobackup your SAS System V8 files, this dialog will not be displayed.

SAS Setup will now begin copying files required to update your SAS Systeminstallation.

Updating a SAS Version 8 Server and Subsequent Clients

This section is intended for network administrators who wish to update a SASSystem V8 Server and subsequent clients. Use the forcemaint command-lineoption to update the Server only when updating from a machine other than the one


originally used to install the Server image. If the update is being performed from thesame machine used to install the original Server image, follow the instructions inUpdating a Local SAS Version 8 Installation on page 19.

Updating the Server

1. Before beginning the update process, make certain that all clients of the serverbeing updated are disconnected. This is necessary to ensure that all updatedfiles can be copied to the SAS System Server.

The update process should be performed from a PC that does not have the SASSystem V8 currently installed. If the SAS System V8 is installed, it should beuninstalled by highlighting it from the Add/Remove item list in ControlPanel, and clicking the Add/Remove button before performing the updateprocess.

When updating the server, SAS Setup should be started with the forcemaintcommand-line option as follows:

:\SAS\SETUP forcemaint


The forcemaint option tells SAS Setup to prompt you for your server’s configfile location.


3. When prompted to supply the directory containing the SASV8.CFG file for theinstallation you are updating, enter the SASROOT folder for the Serverinstallation.

4. At this point, you will be presented with a list containing all the componentsinstalled on your system. Review this listing to ensure that all of the productsyou wish to update are installed. Once you have reviewed this information,click on Next.

5. You are then provided with the opportunity to backup the files that are to beupdated. Backing up these files will provide you the ability to revert to SASSystem V8 by means of the Add/Remove Programs Control Panel. Select Yes ifyou would like to have the ability to remove this update at a later time. If youdo not wish to have this ability, and wish to preserve hard drive space, selectNo. When you are satisfied with your selection, click on Next.

6. If you selected to perform a backup of the SAS System V8 files to be updated,you will be prompted to enter the location where these files should be copied.


Once you have indicated the desired destination, click Next. If you chose not tobackup your SAS System V8 files, this dialog will not be displayed.

SAS Setup will now begin copying files required to update your SAS Systeminstallation.

Updating Subsequent Clients

1. Once the Server has been updated, each Client system must be updated.Uninstalling the current SAS System V8 on each Client is recommended beforeperforming the update. To uninstall the current installation, highlight the SASSystem V8 entry in the Add/Remove item list in Control Panel and clickthe Add/Remove button.

2. Run Setup from the SASROOT folder on the server. This initiates the installationprocess for the SAS System V8 TS M1. Please see “Installation ScenarioExamples” starting on page 9 for instructions about each type of installation.

3. Repeat this process on every Client system.

23

Chapter 4, Invoking the SAS® System

After it is properly installed, Version 8 (TS0M1) of the SAS System under Windowscan be invoked in the following ways:

q Click on Start, select Programs, and choose The SAS System. Then, click onthe icon labeled The SAS System for Windows Version 8 (TS M1) .

q Select the Run command from the Start button menu. Supply the full pathto both the SAS.EXE and the SASV8.CFG files for the SAS System installationyou want to execute as shown in the following example:

C:\Program Files\SAS\SAS.EXE

When you invoke the SAS System, it searches for a SASV8.CFG file in the currentdirectory.

For more information on running the SAS System under Windows, refer to SASCompanion for the Windows Environment, Version 8, Second Edition, and WindowsEnvironment: Changes and Enhancements to the SAS System, Version 8.

25

Chapter 5, Technical Support Services

Direct technical support is provided by SAS Institute to the designated SASInstallation Representative and SAS Support Consultant at your site. Theseindividuals should be the initial contacts for any user who needs technicalassistance. Many programming problems result from a misunderstanding of howthe software works, or a failure to use correct syntax. An experienced SAS SupportConsultant can spot these errors quickly. These individuals can also search the SASNotes database to see if a solution for your problem is provided. If the SASInstallation Representative or SAS Support Consultant cannot solve your problem,they can contact the Institute for further assistance.

SAS Institute provides technical support via the World Wide Web, by phone, mail,electronic mail, or dial-up computer access.

For technical support via the World Wide Web, use the following URL:

http://www.sas.com/ts/

For technical support by phone, call (919) 677-8008 between the hours of 9 a.m. and8 p.m., Eastern Standard Time, weekdays. For technical support by mail, send allcorrespondence to this address:

SAS InstituteTechnical Support DivisionSAS Campus DriveCary, NC 27513-2414

Electronic mail access is available to SAS Installation Representatives and SASSupport Consultants through the Electronic Mail Interface to Technical Support(EMITS). This facility allows you to track a technical support problem or addinformation to a previously reported problem. The following lists additionalelectronic support that the Technical Support Division provides:

TSNEWS-L Mail and File List

allows you to receive the latest information from SAS Institute’s Technical SupportDivision.

Anonymous FTP

allows you to send or receive information from SAS Institute Technical Supportusing FTP.


Electronic Fax Service

allows you send and receive faxes more quickly.

27

Appendix A, Installing SAS/ACCESS® Interface toODBC Software

Before you can use SAS/ACCESS Interface to ODBC software, the followingproducts are required:

• Base SAS Software• SAS/ACCESS Interface to ODBC Software• A 32-bit ODBC driver for the source from which you want to access data

The ODBC solution allows different technologies to be used by defining a standardinterface. SAS/ACCESS Interface to ODBC software with ODBC drivers providesyou with access to different databases. An ODBC driver processes ODBC functioncalls from and returns results to SAS/ACCESS software. You can get drivers fromMicrosoft, your database vendor, or other third party software vendors.

To run SAS/ACCESS software on 32-bit Windows, you need 32-bit drivers. Theapplication calls the 32-bit Driver Manager (ODBC32.DLL), which in turn calls the32-bit drivers. The following figure illustrates the architecture:

SAS/ACCESS

32-Bit Driver Manager(ODBC32.DLL)

32-Bit Driver32-Bit Driver 32-Bit Driver

Data Source Data Source Data Source

The ODBC Driver Manager and Administrator are Microsoft products that areincluded with all ODBC drivers. When you install an ODBC driver, the ODBCDriver Manager and Administrator are also installed. The ODBC Administratorshould appear as an icon in the control panel. However, it can also appear as an iconin the Start menu instead.

After you install the ODBC driver, you can use the ODBC Administrator to defineand manage the data sources. A data source associates a particular ODBC driverwith the data you want to access through that driver. It can consist of informationabout the data you want to access and its associated operating system, DBMS, andnetwork platform (if any) used to access the DBMS. For information about how to


configure your data sources, refer to the documentation provided with your ODBCdrivers.

For more information about SAS/ACCESS to ODBC, refer to the ODBC chapter inSAS/ACCESS Software for Relational Databases: Reference, Version 8, First Edition. Formore information about ODBC, refer to Microsoft ODBC 3.0 Programmer’s Referenceand SDK Guide.

SAS/ACCESS ODBC Conversion Utilities

The SAS/ACCESS ODBC Conversion Utilities are included in the SAS/ACCESSInterface to ODBC software. It helps users of Version 6 SAS/ACCESS Interface toAS/400 and SAS/ACCESS Interface to Microsoft SQL Server move from a nativeDBMS interface connection to an ODBC interface connection on Version 8 of theSAS System.

AS/400 Users

Before you can use the ODBC Conversion Utilities for AS/400 Interface, you need toinstall IBM’s Client Access ODBC Driver (32-bit) V3.00.0004 or above. If yourAS/400 Client Access installation loaded a Client Access ODBC Driver prior to thisversion, you can download Program Temporary Fix (PTF) SF59504 or later fromftp.software.ibm.com for an update. This service pack for the Client Access productcan be found in the/as400/products/clientaccess/win32/v3rlm2/servicepack/ directory.When this update is applied, Version 3.00.0004 or later of the ODBC driver shouldbe installed.

You are also required to create a data source name. You can use the ODBCadministrator to add it. The data source name AS400 is recommended. If you wantto use another data source name, set the SAS environment variable AS400DSN,located in your sasv8.cfg, to the data source name you assigned. Quotes arerequired if blanks or special characters are included. You may want to create it as asystem DSN instead of a user DSN if you have more than one user who may wantto use the same workstation to access the AS/400 database.

Complete the following steps to create a data source for AS/400 database access:

1. Run ODBC Administrator from the Control Panel or Start menu.

2. Click the User DSN or System DSN tab, depending on the number of users..

3. Click the Add button and then choose Client Access ODBC driver(32-bit) from the pop-up windows.

4. Click Finish. This brings up the Setup dialog.

5. Click the General tab and enter AS400 (or another name) in the DataSource Name field. This name needs to match the value you set for the SASenvironment variable AS400DSN.


6. From the pull-down menu, choose an AS/400 system that you want to connectto using this data source.

7. Click on Connection Options . Next, under Signon Information , chooseEnter ID. Click OK.

8. Click the Server tab. Leave blanks or enter your default libraries for search.

9. Click the Format tab. Choose Naming Convention .

10. Click the Package(s) tab. Uncheck the box for Enable Extended DynamicSupport.

11. Click OK to close the Setup window.

Microsoft SQL Server Users

An OBDC Conversion Utility is provided that will allow you to read SAS SystemVersion 6 views to access data in Microsoft SQL Server which were created withSAS/ACCESS Interface to Sybase and SQL Server software on Windows. TheConversion Utility helps users migrate to SAS/ACCESS Interface to ODBC softwareon Windows.

Note: The Conversion Utility applies only to views that access data in MicrosoftSQL Server. It does not apply to SYBASE SQL Server.

The ODBC Conversion Utility requires the Microsoft SQL Server ODBC driver (32-bit) from Microsoft. This driver is installed as part of Microsoft Data AccessComponents (MDAC).

It is recommended, but not required to create a data source name. You can useODBC administrator to add it. You must set the SAS environment variableMSSQLDSN, located in the sasv8.dfg, as the data source name you assigned.Quotes are required if blanks or special characters are included. You can create it asa system DSN instead of a user DSN if you have more than one user who may usethe same workstation to access the Microsoft SQL Server database.

Complete the following steps to create a data source for Microsoft SQL Serverdatabase access:

1. Run ODBC Administrator from the Control Panel or Start menu.

2. Click the User DSN or System DSN tab, depending on the number of users,as stated above.

3. Click the Add button and choose SQL Server from the pop-up window.

4. Enter any name in the Name field. This name needs to match the value you setfor the SAS environment variable MSSQLDSN.


5. Choose or enter the Server field which you defined using SQL ClientConfiguration Utility.

6. Click Next. Select the radio button that describes your login method. Ifnecessary, enter a login ID and password.

7. Click Next. A connection will be initiated. If the connection succeeds, pleaserefer to Step 8 below. If the connection fails, an error message will provide areason for the failure.

8. After a connection succeeds, your default databases may be changed. ClickNext to leave this screen.

9. After changing your default databases, other options may be selected. ClickFinish when this screen is correct.

10. Click Test Data Source . After a message appears indicating that the test wassuccessful, click Okay. Click Okay on the following message as well.

Note: The SAS System will automatically install Microsoft Data AccessComponents (MDAC) when you install SAS/ACCESS Interface to ODBCsoftware.

31

Appendix B, Installing SAS/ACCESS® Interface toORACLE Software

Before you can use SAS/ACCESS Interface to ORACLE software, the followingproducts are required:

q Base SAS softwareq SAS/ACCESS Interface to ORACLE softwareq The appropriate ORACLE Client:

• Oracle8i Client, Version 8.1.5.0 or later• Oracle8 Client, Version 8.0.5.0.0 or later• Oracle7 Client, Version 7.3.4.0 or later

Before using SAS/ACCESS Interface to ORACLE software, you must install theORACLE SQL*Net Client, Version 7.3.4 or above on the same PC whereSAS/ACCESS Interface to ORACLE software will be used.

Note: In order to use the Bulk Load feature of this SAS product, you must haveOracle’s SQL*Loader data-loading utility installed on your PC. This can beobtained by running the Oracle Installer and selecting the Oracle Utilitiesproduct. Please refer to your Oracle documentation for information onSQL*Loader.

If you are using ORACLE, Version 7.3.4 client, you need:

• ORACLE SQL*Net Client, Version 2.3 for Windows NT and Windows 95• ORACLE Protocol Adapter(s), Version 2.3 for Windows NT and Windows 95

If you are using ORACLE Net8 Client, you will need to use Version 8.0.5 or later,with:

• ORACLE Net8 Client, Version 8.x for Windows NT and Windows 95/98• ORACLE Protocol Adapter(s), Version 8.x for Windows NT and Windows

95/98

Client-Server Architecture

SAS/ACCESS Interface to ORACLE software runs on the client machine(Windows). It accepts user input and sends requests to ORACLE SQL*Net (or Net8)client to be transported across the network to the server.

The ORACLE database and ORACLE SQL*Net (or Net8) listener are running on theserver machine (Windows NT, UNIX, or others). The listener accepts the connectionfrom the client on the network. It then delivers SAS/ACCESS requests to theORACLE database.


SAS/ACCESS Interface to ORACLE software only supports ORACLE client V7.3.4or above. However, it can interface to any version of ORACLE databases running onthe server.

Client Side Server Side

SAS/ACCESS Software ORACLE DBMS↓ ↑ ↓ ↑

SQL*Net or Net8 SQL*Net or Net8↓ ↑ ↓ ↑

ORACLE ProtocolAdapter

ORACLE ProtocolAdapter

↓ ↑ ↓ ↑Network

Installing SQL*Net (or Net8)

Run the ORACLE Installer and select SQL*Net Client (or Net8 Client) andone or more ORACLE protocol adapters. It is strongly recommended that youinstall/use ORACLE TCP/IP Adapter for your database connection.

If you are using Version 7.3.4 or Version 8.0.5 Client for database connection, youmay have to set the ORACLE system variable ORAOCI as the name for an ORACLEclient DLL. For example, if you are using ORACLE, Version 8.0.5 for Windows NT,you can create and set the value of ORAOCI as C:\ORANT\BIN\ORA805.DLL in theWindows Registry Editor’s (REGEDIT or REGEDT32) HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE Key .

Assigning the Default Path for the ORACLE Server

After you install ORACLE SQL*Net Client software, you may want to specify thedefault connect string by defining the default path for ORACLE Server. When youuse SAS/ACCESS interface software without specifying any PATH statement/field,SAS/ACCESS software uses the defined default path.

Windows NT


1. Run Windows registry editor (REGEDT32)2. Select HKEY_LOCAL_MACHINE...SOFTWARE...Oracle3. Select Edit...Add Value4. Enter LOCAL as the Value Name and then select OK5. Enter your connect-string for the String field in the pop-up dialog box6. Select OK.


Windows 95 and Windows 98


1. Run Windows registry editor (REGEDIT).2. Select HKEY_LOCAL_MACHINE...SOFTWARE...Oracle .

Note: If you are using the ORACLE8i client, the sequence in Step 2 above endswith an additional selection …HOME0

3. Select Edit...New...String Value .4. Enter LOCAL as the Value Name and then select Edit...Modify.5. The Value Name field now says Local.6. Enter your connect-string for the Value Data field in the pop-up dialog box.7. Select OK.

For more information about SAS/ACCESS Interface to ORACLE, refer to theORACLE chapter in SAS/ACCESS Software for Relational Databases: Reference, Version8, First Edition.

35

Appendix C, Installing SAS/ACCESS® Interface toR/3® Software

SAS/ACCESS Interface to R/3 software requires extensive installation setup beforethe product can be used. You can view or download the detailed setup instructionsfrom the SAS Institute web site:

http://www.sas.com/software/enclosures/installation.html

Select the SAS/ACCESS link under the Products heading.

From this page, you can locate information regarding configurations, system &machine requirements, and upgrades.

SAS/ACCESS Interface to R/3 Software

The following products are required:

• Base SAS software• SAS/ACCESS Interface to R/3 software

Additional functionality is obtained if the following products are installed:

• SAS/Warehouse Administrator• SAS/CONNECT software• SAS/SHARE software

SAS/ACCESS Interface to R/3 Software requires the use of communicationprotocols such as TCP/IP to function properly.

The following SAP R/3 products are required:

• SAP R/3 Release 2.2 or higher• SAP R/3 Remote Function Call Software Development Kit (RFCSDK)

37

Appendix D, Post-Installation Setup for SAS/ASSIST®

Software

This appendix describes how to add an optional master profile to SAS/ASSISTsoftware. You can use a master profile to override the default settings as sent bySAS Institute. This allows you to provide a customized setup for SAS/ASSISTsoftware. With the master profile, you can control the profile options of allSAS/ASSIST users from one central place. For information on the profile options,refer to SAS/ASSIST Software Administrator’s Guide.

Adding a Master Profile

Complete the following steps to add a master profile to SAS/ASSIST software:

1. Specify the location of the master profile by creating a new directory that allusers of SAS/ASSIST software will have read access to.

All users with write access to this directory will automatically also have writeaccess to the master profile in SAS/ASSIST software. Select a name thatconforms to the naming conventions at your installation. The name of this newdirectory must be stored in an entry in the SASHELP library. This requires thatyou have write access to the SASHELP library.

On line 1 of the Program Editor window of the SAS Display ManagerSystem, type the physical pathname of the master profile directory. Execute theSave command to store this in the SASHELP.QASSIST catalog. For example:

SAVE SASHELP.QASSIST.PARMS.SOURCE00001 S:\SAS\ASSIST\PARMS0000200003

The location of the master profile is now known by SAS/ASSIST software.

2. Create the master profile.

The first time SAS/ASSIST software is started, a master profile is created ifSASHELP.QASSIST.PARMS.SOURCE contains the name of an existing physicalpathname, and the person who starts SAS/ASSIST software has write access tothis physical pathname.

3. Customize the master profile by starting SAS/ASSIST software and selectingSetup … Profiles ... Master/group ...


If you have write access to the SAS library containing the master profile, youcan specify default values for your installation. New users will use these valuesas they start SAS/ASSIST software.

Note: If you restrict values by typing R in Status, users will not beallowed to change the values you define.

You can run SAS/ASSIST software in two different styles - workplace or blockmenu. The block menu can be new style or old style. You can control this usingthe profile options below.

Run workplace:

SAS/Assist style: Workplace

Run block menu new style:

SAS/Assist style: Block MenuSave selections on end: YesMenu Style: New

Run old style:

SAS/Assist style: Block MenuSave selections on end: YesMenu Style: Old

By setting the default values in the master profile, you can control if usersshould use the new or old style of SAS/ASSIST software. In addition, there aremany other profile options. For more information on these options, refer toSAS/ASSIST Software Administrator’s Guide.

4. Create group profiles.

From the master profile, it is possible to create group profiles to allow groups ofusers to have different setups. The master profile controls group profiles anduser profiles when a user is not a member of any group. All users are indirectlycontrolled by the master profile when option values are set to a restricted (R)status.

From Setup...Master/Group... , select Locals...Create GroupProfile. To add users to a group profile, select Locals...Update UserGroup. By default, the userid is found in the macro variable &SYSJOBID. Thisvalue is set in the option Userid in the master profile (option type SystemAdministration). Change the value if your site uses another variable to keepthe userid. If the value name starts with &, it is a macro variable; otherwise, it isan environment variable, which is set before the start of the SAS System.

39

Appendix E, Post-Installation Setup forSAS/CONNECT® Software

The first section in this appendix, “Storing and Locating SAS/CONNECT ScriptFiles,” describes the use of the sample script files shipped with SAS/CONNECTsoftware. The next sections in this appendix list supported software for accessmethods available on Windows and Windows NT respectively, and outlineconfiguration procedures for those access methods requiring additionalconfiguration. The final section documents installing and configuring the WindowsSpawner program.

The access methods supported for the SAS System on both Windows andWindows NT are EHLLAPI, DECNET, NETBIOS, TCP/IP, and APPC. Thesemethods are described below in the order listed here. For information about therequirements of a particular access method, please refer to the section thataddresses the method.

Refer to Communications Access Methods for SAS/CONNECT and SAS/SHARE Softwarefor information on the access methods supported by other systems.

Storing and Locating SAS/CONNECT Script Files

Several sample script files are shipped with SAS/CONNECT software.SAS/CONNECT software uses these script files to establish a connection to aremote SAS session.

The SASSCRIPT configuration option points to the location of theSAS/CONNECT script files. The SASSCRIPT option is used by SAS/ASSISTsoftware and can be used by user-written SCL applications.

Under Windows, the script files are installed into the!SASROOT\CONNECT\SASLINK directory by default. The following line is added tothe SASV8.CFG file when SAS/CONNECT software is installed:

-SASSCRIPT !SASROOT\CONNECT\SASLINK

If you want to move the script files to another directory, you must edit theSASV8.CFG file and update the SASSCRIPT option with the new directorylocation. This option can also be specified from theTools/Options/System/Communications/Networking and encryptionselection in DMSEXP mode.


System Configuration for Access Methods Supported under Windows95 and Windows 98

The access methods supported for the SAS System on Windows are described belowin this order: EHLLAPI, DECNET, NETBIOS, TCP/IP, and APPC.

EHLLAPI

For the EHLLAPI access method, a supported emulation package must be installedon the Windows node. The following emulation products are supported:

• Attachmate’s EXTRA Personal Client, Version 6.1+• Exceed, Version 6.1+• IBM’s PCOMM (Personal Communications) Version 4.1+• Wall Data’s Rumba 2000, Version 6+• Any Windows 32-bit emulation program that supports the EHLLAPI or

WinHLLAPI standards.

The EHLLAPI access method requires that the supported emulation package belisted in the Autoexec Path statement as shown in the following example:

path=C:\ehllapi_package;%Path%

DECNET

Use of the DECnet access method requires Digital Equipment Corporation’sPathworks 32 with Microsoft’s Winsock Version 2.0.

NETBIOS

For the NETBIOS access method, SAS/CONNECT software supports the NETBIOSprotocol that is included with Windows.

TCP/IP

For the TCP/IP access method, SAS/CONNECT software supports Microsoft’sTCP/IP System Driver, which is provided with Windows.

APPC

One of the following software packages is required to use the APPC access methodwith the SAS System under Windows:

• IBM’s Communications Server/NT, Version 5.0+• IBM’s Personal Communications Version 4.11 or subsequent versions• Microsoft SNA Server, Version 2.11 SP1 (Service Pack 1) or subsequent versions• Any program that supports WOSA (Windows Open Services Architecture)

APPC (Win APPC) standard.


System Configuration for Access Methods Supported under WindowsNT

The access methods supported for the SAS System on Windows NT are describedbelow in this order: EHLLAPI, DECNET, NETBIOS, TCP/IP, and APPC.

EHLLAPI

The EHLLAPI access method requires one of the following emulation packages:• Attachmate’s EXTRA Personal Client, Version 6.1+• IBM’s PCOMM (Personal Communications) Version 4.1+• Exceed Version 6.1+• Wall Data’s Rumba 2000, Version 6+• Any Windows NT 32-bit emulation program that supports the EHLLAPI or

WinHLLAPI standards.

The EHLLAPI access method requires that the supported emulation package belisted in the Autoexec Path statement as shown in the following example:

path=C:\ehllapi_package;%Path%

DECNET

With Windows 4.0 installed, use the of the DECnet access method requires DigitalEquipment Corporation’s Pathworks 32 software package.

Network Drive Restrictions

Remote SAS/CONNECT sessions cannot access any network drives. This is due tosecurity concerns under Windows NT. The Microsoft Development Library containsmore information. See the Windows NT Knowledge Base articles #Q124184,Q132679, and Q122702. This may be addressed in a future release of the SAS Systemand/or Pathworks. If you require access to a network file, that file can be accessedby copying it to a local drive.

Security Considerations

Signing into a Windows NT system or out of a Windows NT system requires thatuser information be supplied. This information is called the Access ControlInformation (ACI) and is specified as part of the REMOTE= value for the DECnetaccess method. If default user information has been configured, you only need tospecify the remote nodename; otherwise, you must include username and passwordinformation in the ACI. The complete form of the ACI is:

%let rmtnode=node"user pass"::;options remote=rmtnode;


where user can be a valid username for the remote system, or a question markcan be used and you will be prompted for the username at signon time; and wherepass can either be a valid password for the username, or a question mark can beused, and you will be prompted for the password at signon time.

Note: If a password is not required for an account, it can be omitted from the ACI.

Refer to your Pathworks documentation for information on setting up defaultaccounts.

NETBIOS

For the NETBIOS access method, SAS/CONNECT software supports the NETBIOSprotocol that is included with Windows NT.

TCP/IP

For the TCP access method, SAS/CONNECT software supports Microsoft’s TCP/IPSystem Driver, which is provided with Windows NT.

APPC

One of the following software packages is required to use the APPC access methodwith the SAS System under Windows NT:

• IBM’s Communications Server/NT, Version 5.0+• IBM’s Personal Communications Version 4.11 or subsequent version.• Microsoft SNA Server, Version 2.11 SP1 (Service Pack 1) or subsequent versions• Any program that supports WOSA (Windows Open Services Architecture)

APPC (Win APPC) standard.

Configuring the SAS Windows Spawner Program

The SAS Windows Spawner is stored in the !SASROOT directory and can beexecuted manually from the !SASROOT directory at any time. You can run the SASWindows Spawner as an NT service by executing SPAWNER.EXE with thefollowing options:

q install

causes the SAS Windows Spawner to install itself as an Windows NT service. Bydefault, the SAS Windows Spawner will be installed to run with security.

q comamid protocol_name

protocol_name can be TCP, DECnet, or NETBIOS. You must specify at leastone. If more than one is specified, then you must include more than one -comamid option on the command line. There is no default value for this option.


q netname name

name can be a 1 to 8-character string and is the network name that is used byNETBIOS.

q nosecurity

causes the SAS Windows Spawner to run without security. Bydefault, the SAS Windows Spawner will be installed to run with security.

By default, when the SAS Windows Spawner is installed as a Windows NT service,it runs under the LocalSystem userid that has all required User Rights for runningthe SAS Windows Spawner. If you do not install the SAS Windows Spawner as aWindows NT service (run it from your system prompt), the Windows NT, Version4.0 userid used to start the SAS Windows Spawner must be a member of theAdministrator group and must have the following User Rights:

• act as part of the operating system• bypass traverse checking (the default is everyone)• increase quotas• replace a process level token• log on locally (the default is everyone)

The Windows NT, Version 4.0 userid specified at signon needs only the User Right“log on as a batch job.”

Using Encryption with the Spawner

If you are using encryption with the PC spawner, you must take one of thefollowing actions:

• invoke the spawner with the -path option in order to tell the spawner where tofind the encryption modules.

• add the directory to the OS path.• copy the modules to the directory from which you run the spawner.

The DLL for the CryptoAPI support is installed in:

!sasroot\securwin\sasexe\tcpdcapi.dll

and the DLL for the SAS support is installed in:

!sasroot\core\sasexe\tcpdencr.dll

45

Appendix F, Post-Installation Setup forSAS/EIS® Software

Starting with Version 7 of the SAS System, the SAS/EIS Metabase facility has beenconverted to the new Common Metadata Repository. The Common MetadataRepository is a general-purpose metadata management facility that providescommon metadata services to different SAS/EIS applications. The CommonMetadata Repository enables SAS/EIS software to share metadata with other SASSystem products.

For SAS/EIS software users who were using a release prior to Version 7, using theCommon Metadata Repository requires a one-time setup and conversion. Completeall of the steps in the following sections before you attempt to use SAS/EISsoftware.

Note: You must have write access to the SASHELP directory to complete the stepsin the sections below.

Specifying the System Repository Manager Location

Complete the following steps to update the SAS System registry item,REPOSITORY_MGR, with the location of the default repository manager path at yoursite.

1. Create a directory that will be dedicated exclusively to the storage of repositorymanager files, !SASROOT\RPOSMGR for example. This directory should not beused to store other SAS files.

2. Type REGEDIT from a SAS command line. From the toolbar, select Tools, thenOptions, and then Registry Editor. From the Select Registry Viewwindow, select View All, then select OK. Select OK in the dialog window.From the toolbar, select File and then Close to close the Registry Editor.

3. Type REGEDIT again from a SAS command line. Under theHKEY_SYSTEM_ROOT tree, expand CORE and REPOSITORY. Select theREPOSITORY_MGR node. From the toolbar, select Tools, then Options, thenRegistry Editor. Select Open HKEYS_SYSTEM_ROOT for write access.Then, select OK.

4. Select the Path item in the right window. From the right mouse button pop-upmenu, select Modify. Enter the path from step 1. For example,!SASROOT\RPOSMGR . Select OK to close the Edit String Value window.From the toolbar, select File and then Close to close the Registry Editorand save the changes.


Setting Up the System Repository Manager Files

Complete the following steps to set up the necessary system repository managerfiles:

1. From a SAS command line type REPOSMGR and then select the SetupRepository Manager icon.

2. From the Repository Manager Setup window, verify the path as being the

installation instructions for version 8 (ts m1) of the sas system … · 2007. 10. 24. · page 2...

Documents