Hot Topics

Related Links

Step 3


Best Practices Migration with PROC MIGRATE: Install SAS

Step 4: Customize the Installation

Before you begin this step, make a backup copy of any file that you plan to modify.

Customizing for Operating Environment Dependencies

You might have to alter the target configuration if operating environment dependencies have changed from the source release to the target release. For example, some dependencies might be eliminated while new ones arise. Or if an old dependency remains, its interaction with operating environment parameters might be different. To determine whether you have any dependencies, review the SAS System Requirements document, including the system requirements for all of your SAS products. The System Requirements document is shipped in your Installation Kit and is also available at the Install Center.

Making the needed operating environment changes is often outside the domain of the SAS Installation Representative. Products such as SAS/CONNECT, SAS/SHARE, SAS/IntrNet, and SAS Integration Technologies have networking and security requirements. These requirements might be controlled by a department or individuals other than those who install or use SAS. These individuals must collaborate effectively during the migration process.

To check your changes, repeat the initial validation that you performed during installation.

Customizing for Third-Party Software

In the SAS System Requirements document, read about requirements for any third-party software (that is, not a SAS product) that interacts with SAS. Confirm that you are running the required release of the product and that the product's settings are correct. The quintessential example is SAS/ACCESS engines, which are dependent on third-party DBMS software. Other examples are Web browsers, Java components, and networking access methods (tcp, xms, and so on).

To check your changes, repeat the initial validation.

Customizing SAS Configuration Settings

When you have finished altering the operating environment configuration and product configurations, you can modify the SAS configuration and autoexec files. However, you cannot simply copy the source versions to the target installation. That could have disastrous effects, because, for example, options might be deprecated or renamed, and defaults or optimal settings might be different.

Instead, open configuration and autoexec files in a text editor. Carefully review each option and statement in the source configuration and autoexec files on a case-by-case basis before making a change in the target settings. This enables you to determine whether an option and its setting are appropriate to use in the target file.

The SAS registry is another storage area for configuration data. The registry's file type is item store. It should not be migrated, and you can usually ignore it. But if desired, an experienced SAS user or administrator can examine the source environment's settings and determine whether they should be applied to the target. See instructions and important cautions in the "The SAS Registry" chapter in the book SAS Language Reference: Concepts in the SAS online documentation. See also "The REGISTRY Procedure" in the Base SAS Procedures Guide.

To check your changes, repeat the initial validation.

Best practice

Document all settings in the source configuration and autoexec files during the Planning stage. Consult SAS online documentation to be sure the settings are appropriate for the target installation.

Proceed to step 5.