• support.sas.com
• KNOWLEDGE BASE
• SUPPORT
• LEARNING CENTER
• COMMUNITY

Hot Topics

• Migration for Metadata-Based Deployments (February 2009)
  The SAS Migration Utility analyzes and prepares your SAS 9.1.3 deployment for migration. See SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide for a complete guide to planning and execution.
  
  
• The SAS 9.2 Value Proposition
  • Why Upgrade to SAS 9.2 Software? (PDF)
  • Ten Great Reasons Why a Statistician Should Update to SAS 9.2
• Coexistence
  Read about running multiple versions of SAS on one computer.
  • Peaceful Coexistence: SAS®9 and SAS 8.2
  • Peaceful Coexistence: SAS 9.2 and SAS 9.1.3
• Sample Validation SOP
  See an example SOP: SAS Installation Qualification / Operational Qualification (PDF) (updated 19 May 2008) for the pharmaceutical industry.
  
  
• Calculators
  • Compatibility Calculator
  • PROC MIGRATE Calculator
• SAS Notes
  • Data Migration and Compatibility
  • Migration for Metadata-Based Deployments

Related Links

• Glossary
• Install Center
• Section 508 Accessibility
• Expanded Table of Contents
• Contact Us

Papers

Migration

Peaceful Coexistence: SAS®9 and SAS 8.2

It is possible to run SAS®9 on the same computer as SAS 8.2. This topic lists all known issues, to help you avoid any conflicts. In this topic, SAS®9 refers to all SAS 9 releases including SAS 9.2. If you want to run two SAS 9 relases on the same computer, see Peaceful Coexistence: SAS 9.2 and SAS 9.1.3.

Known Issues for Coexistence

• Data sets and other SAS files: SAS strives wherever possible to support cross-release compatibility.
  • Use the interactive Compatibility Calculator (support.sas.com/rnd/migration/planning/files/calculator/) to determine whether you can use your SAS 8.2 files in SAS®9 without migrating them to SAS®9 format.
  • If you use certain SAS®9 file features (support.sas.com/rnd/migration/planning/files/forward.html), then those SAS®9 files are incompatible with SAS 8.2. The features are optional.
  • If needed, you can run a SAS®9 file in a compatible SAS 6, 7, or 8 session or regress the file to the previous version (support.sas.com/rnd/migration/planning/files/regression.html).
  • It is recommended to not store SAS 8.2 files in the same library with SAS®9 files. The file format is virtually unchanged in SAS®9, so the file extension remains the same as in SAS 8.2. This means you could accidentally overwrite an existing file with the same name that was created under the other release. Read about this and other details involved in maintaining files from different releases (support.sas.com/rnd/migration/planning/files/mixed.html).
  • If you make a copy of a data set to test the new release of SAS and the data set is live (that is, continually updated), then you must either update the two data sets concurrently or designate one data set to be frozen and later discarded.
  
  
• Syntax (PROCs, DATA steps, macros, and so forth): You can use SAS or SCL code from SAS 8.2 in SAS®9 and vice versa. However, some syntax has changed. Research the known issues in code compatibility (support.sas.com/rnd/migration/planning/files/programs.html) as well as changes and enhancements.
  
  
• Installation and configuration:
  • If you are installing both SAS 8.2 and SAS®9, install SAS 8.2 first. Otherwise, you might run into problems with the shared files directory.
  • Make sure SAS®9 doesn't use the same TCP/IP port numbers as SAS 8.2.
  • Install SAS 8.2 and SAS®9 in separate locations on the machine.
  • It is recommended that you use the SAS configuration file (sasv8.cfg or sasv9.cfg) to separate the locations of SASWORK.
  
  
• Operating environment:
  • Some SAS 8.2 operating environments (support.sas.com/rnd/migration/planning/platform/sas9platforms.html) are no longer supported in SAS®9.
  • Updates made to an operating environment for SAS®9 system requirements (support.sas.com/documentation/installcenter/) might conflict with SAS 8.2, although this has not been reported.
  • Running two versions of SAS on a machine might require additional disk space or CPU time.
  
  
• Invoking SAS:
  • You can run SAS 8.2 and SAS®9 simultaneously in batch.
  • You can run SAS 8.2 and SAS®9 simultaneously in interactive sessions from the SAS windowing environment (aka Display Manager).
  • The SAS command can be set to one or the other release of SAS by the operating environment. This setting might be done by search paths, registry settings, or operating environment conventions. Take care when invoking SAS to ensure that you are getting the release of SAS that you want.
  • Encoded passwords used in the LIBNAME statement and created by the PWENCODE procedure for SAS®9 do not work in SAS 8.2 programs.
  • SAS environment variables can differ between SAS 8.2 and SAS®9. Failure to set the environment can result in errors, including incorrect user-ID authentication with the SAS®9 Metadata Server. A recommended solution is to write a script that sets the environment variables when SAS is invoked. Here is a sample environment-setting program for UNIX, provided by a customer:

    PATH=/usr/local/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:$HOME:.
    export SASROOT=/usr/local/sas/sas913
    export PATH=$PATH:/usr/local/sas:$SASROOT:$HOME/bin
    

Product-Specific Guidelines

SAS has developed coexistence guidelines for selected products:

• SAS AppDev Studio (support.sas.com/rnd/migration/planning/software/appdev.html)
• SAS Data Integration Studio (support.sas.com/rnd/migration/planning/software/etlstatement.html)
• SAS Enterprise Guide (support.sas.com/rnd/migration/planning/software/entguide.html)
• SAS Integration Technologies (support.sas.com/rnd/migration/planning/software/inttech.html)
• SAS/ACCESS software (support.sas.com/rnd/migration/planning/software/access.html)
• SAS/IntrNet software (support.sas.com/rnd/migration/planning/software/intrnet.html)
• SAS/CONNECT or SAS/SHARE software (support.sas.com/rnd/migration/planning/software/shareconnect.html#cam)
• SAS/Warehouse Administrator (support.sas.com/rnd/migration/planning/software/etlstatement.html)

Any new information will be made available from this page. If you encounter problems in your deployment, please contact SAS Technical Support (support.sas.com/ctx/supportform/index.jsp) for assistance.