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

Hot Topics

• Updates for SAS 9.2 (March 2008)
  See the compatibility calculator to determine whether you need to migrate your libraries to SAS 9.2. Use the PROC MIGRATE calculator to find the right example code for your migration.
  
  
• Get a Smarter COMPARE
  Validation tools for the MIGRATE procedure now work with CEDA and provide additional details about catalogs, indexes, and integrity constraints.
  
  
• Start Planning
  See Getting Started for the most efficient pathway through all of the SAS®9 migration documentation.
  
  
• Coexistence
  Many SAS®9 products can install side-by-side with SAS 8.2 with very good compatibility. See Peaceful Coexistence: SAS®9 and SAS 8.2 for details.
  
  
• Sample Validation SOP
  See an example SOP: SAS Installation Qualification / Operational Qualification (PDF) (updated 19 May 2008) for the pharmaceutical industry.

Related Links

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

Product-Specific Compatibility

Migration

SAS/IntrNet Software

The SAS/IntrNet documentation provides requirements and setup for upgrading to the latest release. See the What's New topics for changes and enhancements in SAS 9.

See also information about compatibility in other SAS products, in SAS syntax, and in SAS files.

Peaceful Coexistence of SAS 8.2 and SAS 9

You can run SAS/IntrNet 8.2 and SAS/IntrNet 9 on the same machine. Take care with the following issues.

• Application Servers and other components must be configured so that TCP/IP ports do not overlap.
  
  
• Each service is tied to a specific release. Name your services based on the application or applications they support and not the version of SAS. For example, naming your services "default8" and "default9" will make it difficult or confusing when you want to move an application to the next release. All references to the service name will need to be changed or the service name will be misleading.
  
  
• It is generally recommended that SAS 9 Application Broker and Load Manager be used to control both SAS 8.2 and SAS 9 servers. This allows the standard URLs to be used to access and manage both sets of servers. A single broker.cfg file can contain both SAS 8.2 and SAS 9 server definitions. It is possible to install both SAS 8.2 and SAS 9 versions of the CGI Tools, but they must be installed to different locations on the Web server.
  
  
• The SAS/GRAPH components installed in the /sasweb/graph are not compatible across SAS 8.2 and SAS 9. If you use the JAVA driver in your SAS/IntrNet applications and need to support both releases, you must install both versions of SAS/GRAPH components on your Web server. Use the ServiceSet directive in your broker.cfg to define _GRAFLOC as appropriate for each service. Verify that your applications use &GRAFLOC (and not the fixed value /sasweb/graph) as the codebase for JAVA graphics.
  
  
• SAS/IntrNet 9 Application Dispatcher samples may not be fully compatible with a SAS 8.2 Application Server. If you want to use the samples, verify that the "default" service is a SAS/IntrNet 9 service; otherwise, you must modify all of the sample HTML files to use a SAS/IntrNet 9 service.