Resources

What's New Table of Contents  

What's New in the SAS 9.0 and 9.1 Companion for UNIX

Overview

New and enhanced features for Base SAS improve ease of use and SAS performance under the UNIX operating environment:

Note:   


Migrating 32-Bit SAS Files to 64-Bit SAS Files

Starting in SAS 9.0, SAS for the AIX, HP-UX, and Solaris operating environments is 64-bit only. Consequently, some SAS files (such as your SAS catalogs) that were created in 32-bit releases of SAS cannot be read by the V9 engine. You can read and write to your 32-bit SAS data sets, SAS/ACCESS views from Oracle or SYBASE, SQL views, or MDDB files from a 64-bit SAS session using CEDA. However, you cannot update these files.

You can use the MIGRATE procedure to convert all of your SAS files to 64-bit. For more information about the MIGRATE procedure, see the Migration Community at support.sas.com/rnd/migration.

Note:   If you use Remote Library Services (RLS) to access SAS files on a server, see the SAS/CONNECT User's Guide for information about accessing Version 6 SAS files.


Accessing SAS Files from Previous Releases

On the 64-bit AIX, HP-UX, and Solaris platforms, the V6 and V6TAPE read-only engines provide read-only access to your Release 6.12 data sets. See SAS Language Reference: Concepts for more information about the compatibility of V6 files with SAS 9.1.

On the Tru64 and Linux platforms, you still have read and write access to your Release 6.12 data sets.


Restricted System Options

Your site administrator can specify SAS system options for your site, a specific group, or an individual user in a restricted configuration file. Because these options are restricted, you cannot change the specified value. Use the new RESTRICT option in the OPTIONS procedure to see all the system options that have been restricted. For information about creating a restricted configuration file, see the SAS System Configuration Guide for UNIX.


Executing UNIX Commands within a SAS Session

umask is added to the list of UNIX commands cd , pwd, or setenv that SAS checks before executing the SAS equivalent in a session when you use the X command, X statement, CALL system routine, or %SYSEXEC.


Sending E-mail from within Your SAS Session


Accessing Shared Executable Libraries from SAS

Shared libraries in UNIX contain executable programs that are written in various programming languages. These libraries store useful routines that might be needed by many applications. Using the MODULE family of SAS functions and CALL routines, you can invoke a routine that resides in an external shared library from within SAS. You can access the shared library routines by using a DATA step, the IML procedure, and SCL code.


Changes to the cleanwork Command

The cleanwork command can now be used to delete utility directories whose associated SAS process has ended.


SAS Resources


SAS Language Elements

Commands

The following commands are obsolete:

Functions and CALL Routines

Statements

Procedures

System Options

The UNBUFLOG system option has been replaced by the LOGPARM system option, which is available in all operating environments. For details, see SAS Language Reference: Dictionary