What’s New in

®
SAS 9.0, 9.1, 9.1.2, and 9.1.3
 ®
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. What’s New in SAS 9.0, 9.1,
9.1.2, and 9.1.3
What’s New in SAS® 9.0, 9.1, 9.1.2, 9.1.3

Copyright © 2004, SAS Institute Inc., Cary, NC, USA

All rights reserved. Produced in the United States of America. No part of this publication may be reproduced, stored
in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise,
without the prior written permission of the publisher, SAS Institute Inc.
U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related
documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in
FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987).

SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.

1st printing, July 2004

2nd printing, December 2004
3rd printing, March 2005
4th printing, June 2005
5th printing, July 2005

SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software
to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit
the SAS Publishing Web site at support.sas.com/pubs or call 1-800-727-3228.
®
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS
Institute Inc. in the USA and other countries. ® indicates USA registration.

Other brand and product names are trademarks of their respective companies.
● SAS 9.0, 9.1, 9.1.2, and 9.1.3 Highlights
● New Products in SAS 9.1, 9.1.2, and 9.1.3
❍ SAS Adapters for SAP

❍ SAS Data Surveyor

❍ SAS e-Data ETL

❍ SAS Intelligence Platform

❍ SAS Web Analytics

● What's New Documentation for Previous Releases of SAS

● Base SAS
❍ Overview

❍ SAS Procedures

❍ SAS Language Features

❍ SAS Windowing Environment

❍ Moving and Accessing SAS Files

❍ Output Delivery System

❍ Data Security Technologies in SAS

❍ SAS Macro Language Facility

❍ SAS Metadata LIBNAME Engine

❍ SAS Scalable Performance Data Engine

❍ SAS XML LIBNAME Engine

❍ Companion for Windows

❍ Companion for UNIX

❍ Companion for OpenVMS Alpha

❍ Companion for z/OS

● SAS/ACCESS
❍ For ADABAS

❍ For CA-Datacom/DB

❍ For IMS

❍ For PC Files

❍ For Relational Databases

❍ For R/3

❍ For SAP BW

● SAS/ASSIST
● SAS/CONNECT
❍ SAS/CONNECT

❍ Communications Access Methods

● SAS Data Providers

● SAS Data Quality Server
● SAS Data Surveyor 4.1 for SAP
● SAS Enterprise Guide 3.0
● SAS Enterprise Miner
❍ SAS Enterprise Miner 4.3

❍ SAS Enterprise Miner 5.1

❍ SAS Text Miner

● SAS ETL Studio

● SAS/ETS
● SAS/Genetics
● SAS/GRAPH
● SAS High-Performance Forecasting
● SAS/IML
● SAS Information Delivery Portal
● SAS Information Map Studio
● SAS Integration Technologies
● SAS Inventory Replenishment Planning
● SAS/IntrNet
❍ Application Dispatcher

❍ htmSQL

● SAS Management Console

● SAS National Language Support
● SAS OLAP Server
● SAS Open Metadata Architecture
● SAS/OR
● SAS/QC
❍ SAS/QC User's Guide

❍ ADX Interface for Design of Experiments

● SAS/SHARE
❍ SAS/SHARE

❍ Communications Access Methods

● SAS/STAT
● SAS Web Report Studio
What's New

SAS 9.0, 9.1, 9.1.2, and 9.1.3 Highlights

The Cornerstones of SAS

SAS®9 is built on four cornerstones: Scalability, Interoperability, Manageability, and Usability.

These cornerstones are the foundation for the future of SAS.

Scalability

● SAS now runs in many 64-bit operating environments, which allows SAS to scale in-
memory processes.
● Parallel processing takes advantage of multiple CPUs by dividing processing among the
available CPUs, which provides performance gains for two types of SAS processes:
threaded I/O and threaded application processing. Some areas that use parallel
processing include:

Indexing
When creating an index that requires sorting, SAS attempts to sort the data using
the thread-enabled sort. By dividing the sorting task into separately executable
processes, the time needed to sort the data can be reduced.
Selected analytic procedures
The following are thread-enabled:
Base SAS procedures
MEANS, REPORT, SORT, SQL, SUMMARY, TABULATE
SAS/STAT procedures
GLM, LOESS, REG, ROBUSTREG
SAS/SHARE procedure
SERVER (with the experimental THREADEDTCP option)
Enterprise Miner procedures
DMINE, DMREG
SAS/ACCESS engines
The following engines use multiple threads to access data from the DBMS server:
■ Oracle

■ Sybase

■ DB2 (UNIX and PC)

■ ODBC

■ SQL Server
 ■ Teradata
Scalable Performance Data (SPD) Engine
The Scalable Performance Data Engine provides parallel I/O by using multiple
CPUs to read SAS data and deliver it rapidly to applications.
SAS/CONNECT
MP CONNECT gives you the ability to exploit SMP (Symmetric Multi-Processing)
hardware as well as network resources to perform parallel processing and easily
coordinate all the results into a single client SAS session.
SAS Metadata Server
The SAS Metadata Server uses threads to enable the best response time for
delivering metadata as requested by any number of clients.
SAS OLAP Server
The SAS OLAP Server provides a new multi-threaded data storage and server
functionality that provides faster cube performance. The data can be stored in a
multidimensional form (MOLAP) or in a form that includes existing aggregations
from presummarized data sources.
● SAS/CONNECT supports pipeline parallelism, which allows multiple DATA steps or
procedures to execute in parallel and to pipe the output from one process as the input to
the next process in a pipeline. Piping improves performance and reduces the demand
for disk space.
● The time required for transferring large amounts of data when using SAS/CONNECT
has been significantly reduced as a result of improvements to the file compression
algorithm.

Interoperability

● SAS Open Metadata Architecture provides common metadata services to all SAS
applications, which improves communication among applications.
● The SAS Add-In for Microsoft Office is an integral part of a complete end-to-end
business intelligence solution that enables you to harness the power of SAS analytics,
access relational data sources directly from Microsoft Word and Microsoft Excel, and
create reports within Microsoft Office.
● SAS/CONNECT libref inheritance eliminates the need to duplicate data for use in
multiple SAS sessions. Server sessions can inherit client-defined librefs, which allows
multiple sessions to read and write data in a single library.
● SAS Integration Technologies now includes support for creating Web services that
enable cross-platform integration, an enhanced publishing framework that supports the
generation and publication of explicit and implicit events, and a new set of core
infrastructure services that Java programmers can use to write applications that are
integrated with the SAS platform.
 ● The XML LIBNAME engine imports and exports a broader variety of XML documents.

Manageability

● SAS Management Console provides a single point-of-control for SAS administrative

tasks.
● SAS ETL Studio is a thin-client system, developed by using Java technology, that
enables you to manage the Extraction, Transformation, and Loading (ETL) of data.
● SAS Personal Login Manager is an application that enables you to manage the
metadata that describes your user accounts. You can use the SAS Personal Login
Manager to add, update, and remove your logins.
● Application Response Measurement (ARM) enables you to check the availability and the
transaction rates of SAS applications.
● Secure Sockets Layer (SSL) provides network security and privacy. SSL is used in Base
SAS, SAS/CONNECT, SAS/SHARE, and Integration Technologies.
● The new Integration Technologies Windows Object Manager and Java Connection
Service create and manage workspace objects that support new types of IOM servers.
● New IOM options are provided to support load balancing
.

Usability

● SAS Information Map Studio is an application that enables you to create, manage, and
view SAS Information Maps—business metadata about your physical data. Information
maps are user-friendly metadata definitions of physical data sources that enable your
business users to query a data warehouse in order to meet specific business needs.
● SAS Web Report Studio is a Web-based application that enables you to create, view,
and organize reports.
● The MIGRATE procedure simplifies the process of migrating your libraries.
● New SAS/GRAPH styles provide a consistent look for output created by the Output
Delivery System (ODS), which enhances readability and usability.
● The metadata LIBNAME engine enables you to read and create metadata in a SAS
Metadata Repository. By incorporating metadata, this engine makes it easier to control
access to the data.
● The Output Delivery System writes to more destinations and provides a greater variety
of formatting selections, which enables you to select an output destination and format
that best meets your reporting needs.
● User-created formats and informats can have names that are longer than eight
characters, which allows you to provide names that are more descriptive.
● New SAS functions improve how you can search for character strings and regular
expressions, which makes it easier for you to search your data for specific results.
● SAS Data Quality Server has been re-engineered to add increased accuracy and
 usability to your data.
● All help and reference documentation is accessible within a SAS session. Selecting SAS
Help and Documentation from the Help menu enables you to view both online Help
information and the full SAS reference library. Prior to SAS 9.0, the reference library was
available only on the SAS OnlineDoc CD-ROM or in hard-copy format.
● SAS has been enhanced with accessibility features for SAS users who have disabilities.
● National Language Support (NLS) enhancements enable customers in regions around
the world to process data successfully in their native languages and environments.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

New Products in SAS 9.1.3: SAS Adapters for SAP

The following SAS Adapters for SAP are available in SAS 9.1.3:

● SAS Activity-Based Management Adapter 6.2 for SAP R/3

● SAS IT Management Adapter 2.7 for SAP

SAS Activity-Based Management Adapter 6.2 for SAP R/3

The SAS Activity-Based Management Adapter 6.2 for SAP R/3 facilitates the sharing of
ABC/M data between SAP R/3 and SAS Activity-Based Management software. This
adapter performs the complex moving of data between SAP Controlling module
components and SAS Activity-Based Management software modules. Additionally, the
adapter supports the development of ABC/M models that are compatible with R/3 and
SAS Activity-Based Management. The SAS Activity-Based Management Adapter 6.2 for
SAP R/3: User's Guide gives you step-by-step instructions for configuring and using the
adapter. The user's guide is located in PDF format at support.sas.com/
sapadapters.

SAS IT Management Adapter 2.7 for SAP

The SAS IT Management Adapter 2.7 for SAP provides ready-to-use code that reads
performance data from generic SAP servers, and transforms the data into a format that
can be used by SAS IT Resource Management Solutions. A typical SAP installation can
have many separate application servers that monitor various selected SAP instances.
Because some instances are not critical (for example, development and test instances),
the SAS IT Management Adapter for SAP enables you to choose and customize which
SAP instances to monitor for performance. The adapter also reads BW cube
performance statistics.

The complete solution consists of three major software components:

❍ SAS/ACCESS Interface to R/3

❍ The adapter, which consists of SAS macros for SAP R/3 and SAP BW

❍ SAS IT Resource Management software.

 The SAS IT Management Adapter 2.7 for SAP: User's Guide gives you step-by-step
instructions for configuring and using the adapter. The user's guide is located in PDF
format at support.sas.com/sapadapters.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

New Products in SAS 9.1: SAS Data Surveyor

The following SAS Data Surveyor products are new in SAS 9.1:

● SAS Data Surveyor for PeopleSoft

● SAS Data Surveyor for Oracle Applications
● SAS Data Surveyor for SAP
● SAS Data Surveyor for Siebel

SAS Data Surveyor for PeopleSoft

The SAS Data Surveyor for PeopleSoft consists of a set of software plug-ins that
provide a faster and easier way for you to access and transform your PeopleSoft data
using SAS ETL Studio and SAS Management Console. It enables you to extract
metadata from PeopleSoft that you can use to query PeopleSoft records. These queries
enable you to

❍ more easily locate and use your PeopleSoft data in SAS

❍ browse the extracted metadata
❍ search the metadata to locate records that contain specific values
❍ query the metadata to build SAS views of PeopleSoft tables and save these views
as permanent SAS views, SAS data files, or SAS source code
❍ specify how you want to handle PeopleSoft effective dates and effective
sequencing in the source data that you extract from PeopleSoft.
SAS Data Surveyor for Oracle Applications

The SAS Data Surveyor for Oracle Applications consists of a set of software plug-ins
that provide a faster and easier way for you to access and transform your Oracle
application data using SAS ETL Studio. It enables you to

❍ extract metadata from Oracle applications that you can use to query Oracle
application tables. These queries enable you to more easily locate and use your
Oracle application data in SAS.
❍ browse the extracted metadata.
❍ search the metadata to locate tables that contain specific values, query the
metadata to build SAS views of Oracle application tables, and save these views
as permanent SAS views, SAS data files, or SAS source code.
 Software plug-ins for SAS Management Console enable you to select or define an
Oracle application server, a library to access this server, and a library to reference the
metadata after it is extracted from Oracle applications.

SAS Data Surveyor for SAP

The SAS Data Surveyor for SAP consists of several software plug-ins to SAS ETL
Studio and SAS Management Console that enable you to

❍ extract metadata from your SAP BW system and write that metadata to SAS data
sets.
❍ browse the extracted SAP BW metadata, write metadata about selected ODS
objects and InfoCubes to your metadata repository, and create jobs that load the
data from the ODS objects and InfoCubes into a specified SAS library.
❍ use Changed Data Capture (CDC) processing to identify and extract only the data
in your ODS tables and InfoCubes that has changed since your last extraction.
❍ dynamically extract metadata from SAP R/3 system tables and write that
metadata to SAS data sets or create a job that can be used to extract metadata
from SAP R/3 hierarchies and groups.
❍ browse the extracted SAP R/3 metadata, select SAP R/3 data sources for your
SAS ETL Studio data warehouse, and write metadata about those data sources
to your metadata repository.
❍ use the SAP LIBNAME engine, which supports load balancing, user validation at
logon, more efficient handling of projections, server-side joins, and directory
processing.

After the SAP metadata is written to the metadata repository, you can use SAS ETL
Studio to further analyze your SAP data.

SAS Data Surveyor for Siebel

The SAS Data Surveyor for Siebel consists of a set of software plug-ins to SAS ETL
Studio that enables you to

❍ read metadata from tables in your Siebel database and browse the extracted
metadata to analyze your Siebel tables and identify which tables contain the
source data that you want to use in your SAS ETL Studio data warehouse.
❍ save metadata about selected Siebel tables into your metadata repository.
❍ use the Siebel Enterprise Integration Manager (EIM) to update the data in either
the Siebel EIM tables or the base tables in your Siebel database, and specify
whether you want to overwrite or append to the data in existing Siebel EIM tables.
 ❍ generate a job in SAS ETL Studio that you can use either to repeat or to schedule
the process of writing data to the specified Siebel EIM tables.
❍ generate a Siebel Server Manager script to submit an EIM job that imports data
from the EIM tables to the appropriate Siebel base tables.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

New Products in SAS 9.1.3: SAS e-Data ETL

SAS 9.1.3 e-Data ETL, a component of SAS Web Analytics, is a clickstream-data-sourcing tool
that enables businesses to read and process their Web data. SAS e-Data ETL provides a
powerful and scalable component that gathers large volumes of Web-traffic data and provides
the following features:

● the SAS e-Data ETL Administrator interface, which enables you to define and manage
the webmarts in which the Web-traffic data is saved.

● the %WEBHOUND macro, which enables you to extract and transform your Web-traffic
data, then save the data into webmarts.

Note: SAS e-Data ETL is available only with SAS Web Analytics.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

New Products in SAS 9.1, 9.1.2, and 9.1.3: SAS Intelligence

Platform

SAS creates and delivers enterprise intelligence through the SAS Intelligence Platform. This
cohesive platform is based on an architecture that fully integrates SAS technologies in data
extraction, transformation, and loading (ETL); data storage; business intelligence; and analytic
intelligence. These capabilities provide the end-to-end infrastructure necessary for exploring,
analyzing, optimizing, reporting, and understanding your data.

For documentation about how to install and administer the SAS® Intelligence Platform, see
http://support.sas.com/documentation/configuration/index.html.

The following SAS Intelligence Platform products are new in SAS 9.1, 9.1.2, and 9.1.3:

● SAS Information Map Studio

● SAS Web Report Studio
● SAS ETL Studio
● SAS Management Console
● SAS Add-In for Microsoft Office
● SAS Personal Login Manager

SAS Information Map Studio

SAS Information Map Studio is an application that enables you to create and manage
SAS Information Maps—business metadata about your physical data. SAS Information
Map Studio provides a graphical user interface that enables you, the information
architect, to create and view information maps.

Information maps are user-friendly metadata definitions of physical data sources that
enable your business users to query a data warehouse in order to meet specific
business needs. Information maps enable business users to easily access enterprise-
wide data by providing the following benefits:

❍ Users are shielded from the complexities of the physical data.

❍ Data storage is transparent to the users, regardless of whether the data is

 relational or multidimensional or whether the data is in a SAS data set or in a third-
party database system.

❍ Business formulas and calculations are predefined, which makes them usable on
a consistent basis.

❍ Users can easily query data for answers to business questions without having to
know query languages.

For more information about the current release, see What's New in SAS Information
Map Studio 2.1.

SAS Web Report Studio

SAS Web Report Studio is a Web-based application that enables you to create, view,
and organize reports. You can use SAS Web Report Studio for the following tasks:

Creating reports

❍ Beginning with a simple and intuitive view of your data provided by SAS
Information Maps (created in SAS Information Map Studio), you can create
reports based on either relational or multidimensional data sources.

❍ You can use the Report Wizard to quickly create simple reports or the Edit Report
view to create sophisticated reports that have multiple data sources, each of
which can be filtered. These reports can include various combinations of list
tables, crosstabulation tables, and graphs. Using the Edit Report view, you can
adjust the style to globally change colors and fonts.

❍ You can also insert stored processes that take the results from a block of SAS
code and embed those results directly into a report.

Viewing and working with reports

While viewing reports by using a thin client (a Web browser), you can filter, sort, and
rank the data that is shown in list tables, crosstabulation tables, and graphs. With
multidimensional data, you can drill down on data in crosstabulation tables and graphs
and drill through to the underlying detail.

Organizing reports
 Reports can be shared with others or kept private. You can create folders and sub-
folders for organizing your reports. Information consumers can use keywords to find the
reports that they need.

Printing and exporting reports

You can preview reports in PDF and print the report, or save and e-mail it later. You
have control over many printing options, including page orientation, page range, and
size of the tables and graphs. You can also export data as a spreadsheet.

For more information about the current release, see What's New in SAS Web Report
Studio 2.1.

SAS ETL Studio

SAS ETL Studio is an application that enables you to manage ETL process flows—
sequences of steps for extracting, transforming, and loading data. SAS ETL Studio
enables ETL designers and developers to quickly build, deploy, and manage their ETL
process flows, extract data from diverse sources, standardize data, perform in-depth
transformations with minimal programming, and deploy near real-time data to meet the
business intelligence needs of an enterprise.

Users can import, export, and store shareable metadata in a repository that describes
and tracks the entire ETL process. SAS Data Surveyors enable direct data access from
systems such as Siebel and SAP. To facilitate metadata exchange from within and
outside the enterprise, the Common Warehouse Metamodel (CWM) standard and Meta
Integration Technology Inc. (MITI) bridges are supported. Extraction, transformation,
and load processes can be run immediately or scheduled to run at another time by using
the integrated scheduling software that is provided (Load Sharing Facility by Platform
Computing) or a scheduler of your choice.

SAS data warehousing includes the following elements:

❍ SAS ETL Studio for ETL design and process management

❍ fully integrated job scheduling capabilities to automate the ETL process

❍ optional, integrated data quality management to simplify ETL efforts

❍ SAS Data Surveyors that enable you to build SAS ETL Studio jobs that read data
from SAP, Siebel, PeopleSoft, Oracle, and other enterprise application vendors
 ❍ SAS Management Console for managing metadata replication, privileges, and
authorizations, and hardware and software deployment

❍ SAS Metadata Server, which is a CWM-compliant enterprise metadata server

❍ SAS application servers for SAS analytics, data access, and process execution.

The SAS ETL Studio: User's Guide is available at support.sas.com.

For more information about the current release, see What's New in SAS ETL Studio.

SAS Management Console

SAS Management Console is a Java application that provides a single point of control
for managing resources that are used throughout the SAS Intelligence Platform. Rather
than using a separate administrative interface for each application in your computing
environment, you can use the single interface in SAS Management Console to perform
the administrative tasks that are required in order to create and maintain an integrated
environment across multiple platforms. For more information about SAS Management
Console, see What's New in SAS Management Console 9.1.2 and 9.1.3.

SAS Add-In for Microsoft Office

The SAS Add-In for Microsoft Office is an integral part of a complete end-to-end
business intelligence solution. The SAS add-in is a Component Object Model (COM)
add-in that extends Microsoft Office by enabling you to harness the power of SAS
analytics, access relational data sources directly from Microsoft Word and Microsoft
Excel, and create reports within Microsoft Office. You can use the SAS add-in for the
following tasks:

Running analyses

❍ Dynamically execute stored processes and SAS tasks.

❍ Search for stored processes by name, date, or keyword.

❍ Analyze SAS or Excel data by using SAS tasks.

Working with results from your stored processes and SAS tasks

❍ Embed the results in your documents and spreadsheets.

 ❍ Refresh the results to include the most up-to-date information.

❍ Send the results from Microsoft Excel to Microsoft Word.

❍ Create reports that include the results, and apply custom styles to the reports.

Working with data

❍ Access and view SAS data sources or any data source that is available from your
SAS server. There is no size limit on the SAS data sources that you can open.

❍ Filter your data by using an intuitive user interface or an advanced SQL editor.

❍ Sort your data by an unlimited number of variables.

❍ Refresh your data sets to incorporate changes while retaining any Excel formulas
that your data might contain.

SAS Personal Login Manager

SAS Personal Login Manager is an application that enables you to manage the
metadata that describes your user accounts. In a SAS Metadata Server, the user ID and
password for each user account can be stored as a login. Each login should correspond
to a user account that has been established for you in the operating system (or with an
alternative authentication provider such as Microsoft Active Directory Server or
Lightweight Directory Access Protocol Server). You can use the SAS Personal Login
Manager to add, update, and remove your logins. For example, after you change the
password for your operating system user account, you can use the SAS Personal Login
Manager to update that password in the SAS Metadata Server. This enables you to
keep the logins that you own in the metadata synchronized with your user accounts. For
more information, see the Help for the SAS Personal Login Manager.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.
What's New

New Products in SAS 9.1.3: SAS Web Analytics 5.0 and 5.1

SAS Web Analytics takes huge volumes of e-data sources and loads them into a flexible Web
mart. Business intelligence reports are created by using advanced patent-pending analytics.
Information is made available through interactive reporting and visualization tools.

New Report Interface

A new Web-based report interface in SAS Web Analytics enables users to create their own
reports even if they have no programming skills. In addition, reports are easier to locate and
customize. Now users can add newly created reports to the system, and reports can be linked
to other reports, for a greater exploration of information.

Types of Reports

Reports in SAS Web Analytics are grouped for better accessibility; the reports provide
improved metrics and enable more thorough analytics. The following types of reports can be
created:

● The Scorecard enables you to monitor strategic Key Performance Indicators (KPIs) that
are related to specific business goals, taking into account seasonality and unobserved
patterns. For example, you can create a scorecard to find out the number of people who
return to your Web site during a 15-day period.

● The Dashboard provides an early warning system for potential problems or opportunities
based on key forecasting metrics in traffic, customer segments, page errors, conversion
rates, and other parameters. Dial-type graphical indicators display favorable,
unfavorable, and neutral business trends.

● The Segmentation report shows the statistically derived segments (identified groups of
Web site visitors) that are analyzed against a business target such as total revenue or
total number of new memberships. Segmentation reports show what metric defines the
segments of a population with the highest propensity to contribute to the business
target. Customer segmentation enables you to determine who your most profitable and
least profitable customers are, and it helps you to more specifically target your ads and
your Web content.
 ● Dynamic Funnel Analysis reports enable you to track visitors as they change levels of
identification during successive visits to your Web site. For example, customers can be
tracked when they initially view your Web site anonymously, when they become
registered visitors, and again when they become buyers. Funnel analysis also calculates
the drop-off rate of visitors for specific online processes (a process is a predefined set of
consecutively visited pages).

● Pathing Analysis reports enable you to better understand how customers traverse the
site.

Improved Analytic Capabilities

● Now you can report on search keywords, banner ads, and referrals, and use this
information to motivate customers to view your Web site, to reduce the costs of e-
marketing campaigns, and to achieve ROI objectives.

● The Report wizard enables you to easily build a custom report and preview it without
having to load the data and run all the reports concurrently, as was required in earlier
releases.

● The SAS System automatically detects and parses the most common Web logs: CLF,
ELF from Apache, iPlanet from Sun Microsystems, and IIS from Microsoft.

● A patent-pending algorithm identifies unique sessions and ensures the accurate

reconstruction of sessions to deliver accurate reports.

● The metadata-driven Web mart structure is newly designed for the SAS Web Analytics
solution. Although the structure uses the familiar summary tables, the open architecture
now enables you to introduce custom tables and third-party data as part of your Web
mart.

● The LSF scheduler, which enables you to easily schedule the ETL batch processes, is
included in the SAS Web Analytics solution.

● The SAS Web Analytics solution uses a multi-tiered architecture to improve

performance. The extraction, transformation, and loading processes occur on a backend
 server, while content delivery is performed on a middle-tier server.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.
What's New

What's New Documentation for Previous Releases of SAS

To view the What's New documentation for previous releases of SAS, see support.sas.
com/documentation/onlinedoc.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in Base SAS 9.0 and 9.1: Overview

Open Metadata Architecture

The SAS Open Metadata Architecture enables you to set up a metadata server, create
metadata repositories, and write applications (clients) that use, store, or manage the metadata.

SAS Management Console

SAS Management Console is a Java application that provides a single point of control for
administering SAS metadata. The application provides a flexible administrative environment
through the use of plug-ins.

Procedures

New multi-threading capabilities improve processing time for the SORT, SQL, MEANS,
TABULATE and REPORT procedures.

The new DOCUMENT procedure enables you to customize or modify your output hierarchy
and replay your output to different destinations without rerunning the PROC or DATA step.
Enhancements to the TEMPLATE procedure enable you to customize or create your own
markup language for your output.

Other enhancements to Base SAS procedures improve ODS formatting, enable import and
export of Microsoft Excel 2002 spreadsheets and Microsoft Access 2002 tables, support long
format and informat names, list and compare SAS registries, enhance statistical processing,
and enhance printer definitions.

Language Elements

New language elements enable the monitoring of application transactions and performance,
enable parallel process using threaded technology, provide Secure Sockets Layer (SSL)
access to files as well as access to files using directory services, improve searching and
manipulating of data, and provide new statistical and mathematical functions.
New engines enable the use of a broader variety of XML documents, provide access to
metadata in a SAS Metadata Repository, and improve performance by using multiple CPUs to
read SAS data.

In the Output Delivery System, SAS 9.0 and 9.1 provide an array of markup languages
including HTML4 and XML. The new ODS GRAPHICS statement (Experimental) now enables
you to produce graphics output. The new ODS DOCUMENT destination gives you more
control over the structure and hierarchy of your output.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in Base SAS 9.0, 9.1, and 9.1.3 Procedures

Overview

Base SAS procedures in SAS 9.0 (and later) include the following features and enhancements:

● improved ODS formatting

● ability to import and export Microsoft Excel 2002 spreadsheets and Microsoft Access
2002 tables

● support for long format and informat names

● ability to list and compare SAS registries

● support for parallel sorting operations

● improved statistical processing

● improved printer definitions.

A list of ODS table names is now provided for each procedure that supports ODS. You can use
these names to reference the table when using the Output Delivery System (ODS) to select
tables and create output data sets.

Note:

● This section describes the features of Base SAS procedures that are new or enhanced
since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 (and later) is supported
on OS/390 and z/OS operating systems and, throughout this document, any reference
to z/OS also applies to OS/390, unless otherwise stated.

Details
The CONTENTS Procedure

The new look for output from the CONTENTS procedure and the CONTENTS statement in
PROC DATASETS provides a better format for the Output Delivery System (ODS). PROC
CONTENTS output now displays the data representation of a file by reporting the native
platform for each file, rather than just showing whether the data representation is native or
foreign. Also, PROC CONTENTS output now provides the encoding value, whether a
character variable is transcoded if required, and whether the data set is part of a generation
group. A new example shows how to insert PROC CONTENTS output into an ODS output
data set for processing.

The new ORDER= option in the CONTENTS statement enables you to print a list of variables
in alphabetical order even if they include mixed-case names.

The COPY Procedure

The following options are new or enhanced in the COPY procedure and the COPY statement
in PROC DATASETS:

● The FORCE option enables you to use the MOVE option for a SAS data set that has an
audit trail.

● The CLONE option now copies the data representation and encoding data set attributes.

The CORR Procedure

The CORR procedure has the following new features:

● The FISHER option in the PROC CORR statement requests confidence limits and p-
values for Pearson and Spearman correlation coefficients based on Fisher's z
transformation. Using the FISHER option, you can specify an alpha value and a null
hypothesis value. You can also specify the type of confidence limit (upper, lower, or two-
sided) and whether the bias adjustment should be used for the confidence limits.

● The PLOTS=MATRIX option in the PROC CORR statement uses ODS graphics to
produce either a rectangular matrix plot (if you also specify a WITH statement) or a
symmetric matrix plot (if you do not specify a WITH statement) for variables.

● The PLOTS=SCATTER option in the PROC CORR statement uses ODS graphics to
 produce scatter plots for variables. By default, the scatter plot also includes a 95%
prediction ellipse. You can use the ELLIPSE= option with the PLOTS=SCATTER option
to include prediction ellipses for new observations, confidence ellipses for the mean, or
no ellipses.

The DATASETS Procedure

Directory listings from the DATASETS procedure provide a new look for output, which
improves the format for the Output Delivery System (ODS).

The following statements are enhanced in the DATASETS procedure:

● The AUDIT_ALL= option in the AUDIT statement specifies whether logging can be
suspended and whether audit settings can be changed. In addition, the LOG option in
the AUDIT statement now enables you to control the logging of administrative events to
the audit file by using the ADMIN_IMAGE= setting.

● The ICCREATE statement now enables you to create overlapping constraints. This
means that variables in a SAS data set are part of both a primary key definition and a
foreign key definition.

● The CORRECTENCODING= option in the MODIFY statement changes the encoding

indicator (which is stamped in the file's descriptor information) in order to match the
actual encoding of the file's data.

The DOCUMENT Procedure

The new DOCUMENT procedure enables you to customize or modify your output hierarchy,
and replay your output to different destinations without re-running the PROC or DATA step.
For complete information, see SAS Output Delivery System: User's Guide.

The EXPORT Procedure

The EXPORT procedure now enables you to perform the following tasks:

● export to Microsoft Excel 2002 spreadsheets and Microsoft Access 2002 tables. The
new data sources are available for the Windows operating environment on 32-bit
platforms if your site has a license for the SAS/ACCESS Interface for PC Files.
 ● specify SAS data set options in the DATA= argument when you are exporting to all data
sources except for delimited, comma-separated, and tab-delimited external files. For
example, if the data set that you are exporting has an assigned password, use the
ALTER=, PW=, READ=, or WRITE= data set option. To export only data that meets a
specified condition, use the WHERE= data set option.

● identify a specific spreadsheet in a workbook by specifying the SHEET= option.

Exporting to multiple sheets is available for Microsoft Excel 97, 2000, and 2002
spreadsheets for the Windows operating environment on 32-bit platforms if your site has
a license for the SAS/ACCESS Interface for PC Files.

The FCMP Procedure

The new FCMP procedure enables you to create, test, and store SAS functions and
subroutines for use by other SAS procedures.

For more information about the FCMP procedure, see http://support.sas.com/

documentation/onlinedoc. Select Base SAS from the Product-Specific Documentation
list.

The FONTREG Procedure

The new FONTREG procedure enables you to add system fonts to the SAS registry.

The FORMAT Procedure

● The maximum length for character format names is now 31. The maximum length for
numeric format names is now 32.

● The maximum length for character informat names is now 30. The maximum length for
numeric informat names is now 31.

The FREQ Procedure

In the PROC FREQ statement, the new NLEVELS option displays a table that shows the
number of levels for each variable that is named in the TABLES statement(s).
The new ZEROS option in the WEIGHT statement enables you to include observations that
have 0 weight values. The frequency and crosstabulation tables will display any levels that
correspond to observations that have 0 weights. PROC FREQ includes levels that have 0
weights in the chi-square goodness-of-fit test for one-way tables, in the binomial computations
for one-way tables, and in the computation of kappa statistics for two-way tables.

The following new options are available in the TABLES statement:

● The CONTENTS= option enables you to specify the text for the HTML contents file links
to crosstabulation tables.

● The BDT option enables you to request Tarone's adjustment in the Breslow-Day test for
homogeneity of odds ratios when you use the CMH option to compute the Breslow-Day
test for stratified 2×2 tables.

● The NOWARN option suppresses the log warning message that indicates that the
asymptotic chi-square test might not be valid when more than 20% of the table cells
have expected frequencies that are less than 5.

● The CROSSLIST option displays crosstabulation tables in ODS column format. This
option creates a table that has a table definition that you can customize by using the
TEMPLATE procedure.

Additionally, PROC FREQ now produces exact confidence limits for the common odds ratio
and related tests.

The IMPORT Procedure

The IMPORT procedure now enables you to perform the following tasks:

● import Microsoft Excel 2002 spreadsheets and Microsoft Access 2002 tables. The new
data sources are available for the Windows operating environment on 32-bit platforms if
your site has a license for the SAS/ACCESS Interface for PC Files.

● specify SAS data set options in the OUT= argument when you are importing from all
data sources except for delimited, comma-separated, and tab-delimited external files.
For example, in order to assign a password for a resulting SAS data set, use the
ALTER=, PW=, READ=, or WRITE= data set option. To import only data that meets a
specified condition, use the WHERE= data set option.
The MEANS and SUMMARY Procedures

The new THREADS|NOTHREADS option enables or prevents the activation of multi-threaded

processing.

When you format class variables by using user-defined formats that are created with the
MULTILABEL and NOTSORTED options, specifying the three options MLF, PRELOADFMT,
and ORDER=DATA in a CLASS statement now orders the procedure output according to the
label order in the format definition.

The MIGRATE Procedure

The new MIGRATE procedure is available specifically for migrating a SAS data library from a
previous release to the most recent release. For migration, PROC MIGRATE offers benefits
that PROC COPY does not. For PROC MIGRATE documentation, see the Migration
Community at http://support.sas.com/rnd/migration.

The PROTO Procedure

The PROTO procedure, which has been available in SAS Risk Dimensions software, is now a
Base SAS procedure. The PROTO procedure enables you to register, in batch, external
functions that are written in the C or C++ programming languages for use in SAS programs
and C-language structures and types. For PROC PROTO documentation, go to http://
support.sas.com/documentation/onlinedoc. Select Base SAS from the Product-
Specific Documentation list.

The PRTDEF Procedure

There are 15 new variables to control the default printer settings.

The PRTEXP Procedure

The new PRTEXP procedure enables you to write attributes, which are used by PROC
PRTDEF to define a printer, either to a SAS data set or to the SAS log. With this capability you
can replicate and modify those attributes easily.
The PWENCODE Procedure

The new PWENCODE procedure enables you to encode a password. You can use the
encoded password in place of plain-text passwords in SAS programs that access relational
database management systems (RDBMS) and SAS servers (such as the SAS Metadata
Server).

The REGISTRY Procedure

The REGISTRY procedure has three new options:

● The LISTREG option lists the contents of the registry in the log.

● The COMPAREREG1 and COMPAREREG2 options are used together to compare two
registries. The results appear in the log.

The REPORT Procedure

The REPORT procedure has the following new features:

● The new THREADS|NOTHREADS option enables or prevents the activation of multi-

threaded processing.

● Numeric class variables that do not have a format assigned to them are automatically
formatted with the BEST12. format.

● PROC REPORT now writes the value _PAGE_ for the _BREAK_ variable in the output
data set for observations that are derived from a COMPUTE BEFORE _PAGE_ or
COMPUTE AFTER _PAGE_ statement.

The SORT Procedure

The SORT procedure has the following new options:

● The DATECOPY option copies to the output data set the SAS internal date and time
when the input data set was created, and the SAS internal date and time when it was
last modified prior to the sort.
 ● The DUPOUT= option specifies an output data set that contains duplicate observations.

● The OVERWRITE option deletes the input data set before the replacement output data
set is populated with observations.

● The THREADS|NOTHREADS option enables or prevents the activation of multi-

threaded sorting.

The SQL Procedure

The SQL procedure has the following new features:

● The PROC SQL statement now has a THREADS | NOTHREADS option. THREADS
enables PROC SQL to take advantage of the new parallel processing capabilities in
SAS when performing sorting operations.

● The PROC SQL and RESET statements now contain the BUFFERSIZE option, which
enables PROC SQL to specify a buffer page size for the output.

● There are new DICTIONARY tables, new columns in existing DICTIONARY tables, and
SASHELP views of the new tables. For DICTIONARY.TABLES and SASHELP.VTABLE,
if a table is read-protected with a password, the only information that is listed for that
table is the library name, member name, member type, and type of password protection;
all other information is set to missing.

● You can now reference a permanent SAS data set by its physical filename.

● When using the INTO clause to assign values to a range of macro variables, you can
now specify leading zeroes in the macro variable names.

● PROC SQL now supports TRANSCODE=YES|NO as a column modifier.

The SYLK Procedure (Experimental)

The new SYLK procedure enables you to read an external SYLK-formatted spreadsheet into
SAS, including data, formulas, and formats. You can also use PROC SYLK as a batch
spreadsheet, using programming statements to manipulate data, perform calculations,
generate summaries, and format the output.
For more information about the SYLK procedure, see http://support.sas.com/
documentation/onlinedoc. Select Base SAS from the Product-Specific Documentation
list.

The TABULATE Procedure

The TABULATE procedure has the following new features:

● The new THREADS|NOTHREADS option enables or prevents the activation of multi-

threaded processing.

● Available statistics include upper and lower confidence limits, skewness, and kurtosis.
PROC TABULATE now supports the ALPHA= option, which enables you to specify a
confidence level.

● Numeric class variables that do not have a format assigned to them are automatically
formatted with the BEST12. format.

● The new FORMAT_PRECEDENCE and STYLE_PRECEDENCE options in the TABLE

statement enable you to specify which formats and styles (defined for the column, row,
or page dimensions) are applied.

Additionally, when you format class variables by using user-defined formats that are created
with the MULTILABEL and NOTSORTED options, specifying the three options MLF,
PRELOADFMT, and ORDER=DATA in a CLASS statement now orders the procedure output
according to the label order in the format definition.

The TEMPLATE Procedure

The TEMPLATE procedure now enables you to customize or create your own markup
language for your output. For complete information, see the SAS Output Delivery System:
User's Guide.

The TIMEPLOT Procedure

The TIMEPLOT procedure now supports the SPLIT= option, which enables you to specify a
character which causes labels to be split into multiple lines.
The UNIVARIATE Procedure

The UNIVARIATE procedure has the following new features:

● The LOWER= and NOUPPER= suboptions in the KERNEL option in the HISTOGRAM
statement specify the lower and upper bounds for fitted kernel density curves.

● The FRONTREF option in the HISTOGRAM statement draws reference lines in front of
the histogram bars instead of behind them.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the Base SAS 9.0, 9.1, and 9.1.3 Language
Overview of Base SAS

New and enhanced features in Base SAS save you time, effort, and system resources by
providing faster processing and easier data access and management, more robust analysis,
and improved data presentation.

● By using new SAS system options that enable threading and the use of multiple CPUs,
the following SAS procedures take advantage of multi-processing I/O: SORT, SQL,
MEANS, TABULATE, and REPORT.

● The LIBNAME statement now supports secure access to SAS libraries on a WebDAV
server.

● You can now use longer, easier-to-read names for user-created formats and informats.

● Two pre-defined component objects for the DATA step enable you to quickly store,
search, and retrieve data based on lookup keys.

● The FILENAME statement now supports directory services, multiple FTP service
commands, and Secure Sockets Layering (SSL).

● The Application Response Measurement (ARM) system enables you to monitor the
availability and performance of transactions within and across diverse applications.

● The Perl regular expression (PRX) functions and CALL routines use a modified version
of Perl as a pattern-matching language to enhance search-and-replace operations on
text.

● New character functions search and compare character strings in addition to

concatenating character strings.

● There are several new descriptive statistic functions and mathematical functions.

● New formats, informats, and functions support international and local values for money,
datetime, and Unicode values. All data set options, formats, informats, functions, and
system options that relate to national language support are documented in the new SAS
National Language Support (NLS): User's Guide.
 ● A new ODS statement enables you to render multiple ODS output formats without re-
running a PROC or a DATA step. See the SAS Output Delivery System: User's Guide.

Note:

● This section describes the features of Base SAS that are new or enhanced since SAS
8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 (and later) is supported
on both OS/390 and z/OS operating systems and, throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

SAS System Features

Application Response Measurement (ARM)

Application Response Measurement (ARM) enables you to monitor the availability and
performance of transactions within and across diverse applications. The SAS ARM interface
consists of the implementation of the ARM API as ARM macros and an ARM agent. An ARM
agent generates calls to the ARM macros. New ARM system options enable you to manage
the ARM environment and to log internal SAS processing transactions.

Cross-Environment Data Access (CEDA)

CEDA processes SAS files that were created on a different host. This is especially useful if you
have upgraded from a 32-bit platform to a 64-bit platform. Messages in the SAS log notify you
when CEDA is being used to process a SAS file. See "Processing Data Using Cross-
Environment Data Access (CEDA)" in SAS Language Reference: Concepts.

DATA Step Object Attributes and Methods

SAS now provides two pre-defined component objects for use in a DATA step: the hash object
and the hash iterator object. These objects enable you to quickly and efficiently store, search,
and retrieve data based on lookup keys.
The DATA step component object interface enables you to create and manipulate these
component objects by using statements, attributes, and methods. You use the DATA step
object dot notation to access the component object's attributes and methods.

The hash and hash iterator objects have one attribute, fourteen methods, and two statements
associated with them. See DATA Step Object Attributes and Methods.

Engines

● The default BASE engine in SAS supports longer format and informat names, thread-
enabled procedures such as the SORT and SUMMARY procedures, and more than
32,767 variables in a SAS data set.

● The metadata LIBNAME engine enables you to use metadata in order to access and
augment data that is identified by the metadata. The metadata engine retrieves
information about the target SAS data library from metadata objects in a specified SAS
Metadata Repository on the SAS Metadata Server. The metadata engine provides a
consistent method for accessing many data sources. That is, SAS provides different
engines that have different options, behavior, and tuning requirements. By taking
advantage of metadata, the necessary information that is required to access data can be
created in one central location so that applications can use the metadata engine to
access different sources of data, without having to understand the differences and
details of each SAS engine. See the SAS Metadata LIBNAME Engine: User's Guide.

● The XML LIBNAME engine imports and exports a broader variety of XML documents.
The XMLMAP= option specifies a separate XML document that contains specific
XMLMap syntax. The XMLMap syntax, Version 1.2, tells the XML engine how to
interpret the XML markup in order to successfully import an XML document. See the
SAS Metadata LIBNAME Engine: User's Guide.

● The new SASEDOC LIBNAME engine enables you to bind output objects that persist in
an ODS document. See the SAS Output Delivery System: User's Guide.

● The new character variable padding (CVP) engine expands character variable lengths,
using a specified expansion amount, so that character data truncation does not occur
when a file requires transcoding. Character data truncation can occur when the number
of bytes for a character in one encoding is different from the number of bytes for the
same character in another encoding, such as when a single-byte character set (SBCS)
is transcoded to a double-byte character set (DBCS). See the SAS National Language
Support (NLS): User's Guide.
Indexing

When creating an index that requires sorting, SAS tries to sort the data by using the thread-
enabled sort. By dividing the sorting task into separately executable processes, the time that is
required to sort the data can be reduced. See the topic "Creating an Index" in Understanding
SAS Indexes in SAS Language Reference: Concepts.

Integrity Constraints

Variables in a SAS data file can now be part of both a primary key (general integrity constraint)
and a foreign key (referential integrity constraint). However, there are restrictions when
defining a primary key constraint and a foreign key constraint that use the same variables. See
the topic "Overlapping Primary Key and Foreign Key Constraints" in Understanding Integrity
Constraints in SAS Language Reference: Concepts.

Restricted System Options

System administrators can restrict system options from being modified by a user. You can use
the RESTRICT option in the OPTIONS procedure to list the restricted options. The
implementation of restricted options is specific to the operating environment. For details about
how to restrict options, see the configuration guide for your operating environment. For
information about listing restricted options, see the OPTIONS procedure in the Base SAS
Procedures Guide.

SAS Utility Macro

The SAS utility macro, %DS2CSV, is available now in Base SAS. This macro converts SAS
data sets to comma-separated values (CSV) files. Prior to SAS 9.1, this macro was available
only for SAS/IntrNet users.

Universal Unique Identifiers

A Universal Unique Identifier (UUID) is a 128-bit identifier that consists of date and time
information, and the IEEE node address of a host. UUIDs are useful when objects such as
rows or other components of a SAS application must be uniquely identified. For more
information, see Universal Unique Identifiers in SAS Language Reference: Concepts.
SAS Language Elements

Descriptions of the new and enhanced language elements for national language support can
be found in What's New for SAS 9.0 and 9.1 National Language Support in the SAS National
Language Support (NLS): User's Guide.

Data Set Options

● The following data set options are new:

OBSBUF=

determines the size of the view buffer for processing a DATA step view.

SPILL=

specifies whether to create a spill file for non-sequential processing of a DATA

step view.

● The following data set options are enhanced:

BUFNO=

supports the same syntax as the BUFNO= system option in order to specify the
number of buffers to be allocated for processing a SAS data set.

BUFSIZE=

supports the same syntax as the BUFSIZE= system option in order to specify the
permanent buffer page size for an output SAS data set.

FIRSTOBS=

supports the same syntax as the FIRSTOBS= system option in order to specify
which observation SAS processes first.

OBS=

supports the same syntax as the OBS= system option in order to specify when to
 stop processing observations.

Formats

● The maximum length for character format names is increased to 31. The maximum
length for numeric format names is increased to 32.

● Several formats have been enhanced with default and range values.

● The following formats are new:

MMYY

writes date values in the form mmM<yy>yy, where M is the separator and the
year is written in either 2 or 4 digits.

YYMM

writes date values in the form <yy>yyMmm, where the year is written in either 2 or
4 digits and M is the separator.

YYQ

writes date values in the form <yy>yyQq, where the year is written in either 2 or 4
digits, Q is the separator, and q is the quarter of the year.

YYQR

writes date values in the form <yy>yyQqr, where the year is written in either 2 or 4
digits, Q is the separator, and qr is the quarter of the year expressed in Roman
numerals.

● The PVALUE format now returns missing values that are specified by the MISSING=
system option.

Functions and CALL Routines

New functions and CALL routines include character, mathematical, descriptive statistical, and
special functions, and character-string matching functions that can use PERL expressions.
● The following character functions are new:

ANYALNUM

searches a character string for an alphanumeric character and returns the first
position at which it is found.

ANYALPHA

searches a character string for an alphabetic character and returns the first
position at which it is found.

ANYCNTRL

searches a character string for a control character and returns the first position at
which it is found.

ANYDIGIT

searches a character string for a digit and returns the first position at which it is
found.

ANYFIRST

searches a character string for a character that is valid as the first character in a
SAS variable name under VALIDVARNAME=V7, and returns the first position at
which that character is found.

ANYGRAPH

searches a character string for a graphical character and returns the first position
at which it is found.

ANYLOWER

searches a character string for a lowercase letter and returns the first position at
which it is found.

ANYNAME
 searches a character string for a character that is valid in a SAS variable name
under VALIDVARNAME=V7, and returns the first position at which that character
is found.

ANYPRINT

searches a character string for a printable character and returns the first position
at which it is found.

ANYPUNCT

searches a character string for a punctuation character and returns the first
position at which it is found.

ANYSPACE

searches a character string for a white-space character (blank, horizontal tab,

vertical tab, carriage return, line feed, or form feed), and returns the first position
at which it is found.

ANYUPPER

searches a character string for an uppercase letter and returns the first position at
which it is found.

ANYXDIGIT

searches a character string for a hexadecimal character that represents a digit

and returns the first position at which that character is found.

CAT

concatenates character strings without removing leading or trailing blanks.

CATS

concatenates character strings and removes leading and trailing blanks.

CATT

concatenates character strings and removes trailing blanks only.

CATX

concatenates character strings, removes leading and trailing blanks, and inserts
separators.

CHOOSEC

returns a character value that represents the results of choosing from a list of
arguments.

CHOOSEN

returns a numeric value that represents the results of choosing from a list of
arguments.

COMPARE

returns the position of the left-most character by which two strings differ, or
returns 0 if there is no difference.

COMPGED

compares two strings by computing the generalized edit distance.

COMPLEV

compares two strings by computing the Levenshtein edit distance.

COUNT

counts the number of times that a specific substring of characters appears within
a character string that you specify.

COUNTC

counts the number of specific characters that either appear or do not appear
within a character string that you specify.

FIND
 searches for a specific substring of characters within a character string that you
specify.

FINDC

searches for specific characters that either appear or do not appear within a
character string that you specify.

IFC

returns a character value that matches an expression.

IFN

returns a numeric value that matches an expression.

LENGTHC

returns the length of a character string, including trailing blanks.

LENGTHM

returns the amount of memory (in bytes) that is allocated for a character string.

LENGTHN

returns the length of a non-blank character string, excluding trailing blanks, and
returns 0 for a blank character string.

NLITERAL

converts a character string that you specify to a SAS name literal (n-literal).

NOTALNUM

searches a character string for a non-alphanumeric character and returns the first
position at which it is found.

NOTALPHA

searches a character string for a non-alphabetic character and returns the first
 position at which it is found.

NOTCNTRL

searches a character string for a character that is not a control character and
returns the first position at which it is found.

NOTDIGIT

searches a character string for any character that is not a digit and returns the
first position at which that character is found.

NOTFIRST

searches a character string for an invalid first character in a SAS variable name
under VALIDVARNAME=V7, and returns the first position at which that character
is found.

NOTGRAPH

searches a character string for a non-graphical character and returns the first
position at which it is found.

NOTLOWER

searches a character string for a character that is not a lowercase letter and
returns the first position at which that character is found.

NOTNAME

searches a character string for an invalid character in a SAS variable name under
VALIDVARNAME=V7, and returns the first position at which that character is
found.

NOTPRINT

searches a character string for a non-printable character and returns the first
position at which it is found.

NOTPUNCT
 searches a character string for a character that is not a punctuation character and
returns the first position at which it is found.

NOTSPACE

searches a character string for a character that is not a white-space character

(blank, horizontal tab, vertical tab, carriage return, line feed, or form feed), and
returns the first position at which it is found.

NOTUPPER

searches a character string for a character that is not an uppercase letter and
returns the first position at which that character is found.

NOTXDIGIT

searches a character string for a character that is not a hexadecimal digit and
returns the first position at which that character is found.

NVALID

checks a character string for validity for use as a SAS variable name in a SAS
statement.

PROPCASE

converts all words in an argument to proper case.

PRXCHANGE

performs a pattern-matching replacement.

PRXPOSN

returns the value for a capture buffer.

SCANQ

returns the nth word from a character expression and ignores delimiters that are
enclosed in quotation marks.
 STRIP

returns a character string with all leading and trailing blanks removed.

SUBPAD

returns a substring that has a length you specify, using blank padding if
necessary.

SUBSTRN

returns a substring that allows a result with a length of 0.

● The following descriptive statistics functions are new:

GEOMEAN

returns the geometric mean.

GEOMEANZ

returns the geometric mean without fuzzing the values of the arguments that are
approximately 0.

HARMEAN

returns the harmonic mean.

HARMEANZ

returns the harmonic mean without fuzzing the values of the arguments that are
approximately 0.

IQR

returns the interquartile range.

LARGEST

returns the kth largest non-missing value.

 MAD

returns the median absolute deviation from the median.

MEDIAN

computes median values.

MODZ

returns the remainder from the division of the first argument by the second
argument; uses 0 fuzzing.

PCTL

computes percentiles.

RMS

returns the root mean square.

SMALLEST

returns the kth smallest non-missing value.

● The following External Files function is new:

DCREATE

creates an external directory.

● The following macro functions are new:

SYMEXIST

indicates the existence of a macro variable.

SYMGLOBL

indicates whether a macro variable has global scope in the DATA step during
DATA step execution.
 SYMLOCAL

indicates whether a macro variable has local scope in the DATA step during
DATA step execution.

● The following mathematical functions are new:

BETA

returns the value of the beta function.

COALESCE

returns the first non-missing value from a list of numeric arguments.

COALESCEC

returns the first non-missing value from a list of character arguments.

LOGBETA

returns the logarithm of the beta function.

● The following probability function is new:

LOGCDF

returns the logarithm of a left cumulative distribution function.

● The following quantile function is new:

QUANTILE

returns the quantile from the specified distribution.

● The following special function is new:

UUIDGEN
 returns the short or the binary form of a Universal Unique Identifier (UUID).

● The following state and ZIP code function is new:

ZIPCITY

returns a city name and the two-character postal code that corresponds to a ZIP
code.

● The following trigonometric function is new:

ATAN2

returns the arc tangent of two numeric variables.

● The following truncation functions are new:

CEILZ

returns the smallest integer that is greater than or equal to the argument; uses 0
fuzzing.

FLOORZ

returns the largest integer that is less than or equal to the argument; uses 0
fuzzing.

INTZ

returns the integer portion of the argument; uses 0 fuzzing.

ROUND

rounds the first argument to the nearest multiple of the second argument, or to the
nearest integer when the second argument is omitted.

ROUNDE

rounds the first argument to the nearest multiple of the second argument, and
returns an even multiple when the first argument is halfway between the two
nearest multiples.
 ROUNDZ

rounds the first argument to the nearest multiple of the second argument; uses 0
fuzzing.

● The following variable information functions are new:

VVALUE

returns the formatted value that is associated with the variable that you specify.

VVALUEX

returns the formatted value that is associated with the argument that you specify.

● Using Perl regular expression (PRX) functions and CALL routines is new. The following
PRX functions are new. For more information, see Pattern Matching Using SAS Regular
Expressions (RX) and Perl Regular Expressions (PRX).

PRXMATCH

searches for a pattern match and returns the position at which the pattern is found.

PRXPAREN

returns the last bracket match for which there is a match in a pattern.

PRXPARSE

compiles a Perl regular expression that can be used for pattern-matching a

character value.

CALL PRXCHANGE

performs a pattern-matching substitution.

CALL PRXDEBUG

enables Perl regular expressions in a DATA step to send debug output to the
SAS log.
 CALL PRXFREE

frees unneeded memory that was allocated for a Perl regular expression.

CALL PRXNEXT

returns the position and length of a substring that matches a pattern and iterates
over multiple matches within one string.

CALL PRXPOSN

returns the start position and length for a capture buffer.

CALL PRXSUBSTR

returns the position and length of a substring that matches a pattern.

● The following CALL routines are new:

CALL ALLPERM

generates all permutations of the values of several variables.

CALL CATS

concatenates character strings and removes leading and trailing blanks.

CALL CATT

concatenates character strings and removes trailing blanks only.

CALL CATX

concatenates character strings, removes leading and trailing blanks, and inserts
separators.

CALL COMPCOST

sets the costs of operations for later use by the COMPGED function.
CALL LOGISTIC

returns the logistic value of each argument.

CALL MISSING

assigns a missing value to specified character or numeric variables.

CALL RANPERK

randomly permutes the values of the arguments and returns a permutation of k

out of n values.

CALL RANPERM

randomly permutes the values of the arguments.

CALL SCAN

returns the position and length of a given word in a character expression.

CALL SCANQ

returns the position and length of a given word in a character expression, and
ignores delimiters that are enclosed in quotation marks.

CALL SOFTMAX

returns the softmax value for each argument.

CALL STDIZE

standardizes the values of one or more variables.

CALL STREAMINIT

specifies a seed value to use for subsequent random number generation by the
RAND function.

CALL SYMPUTX
 assigns a value to a macro variable and removes both leading and trailing blanks.

CALL TANH

returns the hyperbolic tangent of each argument.

CALL VNEXT

returns the name, type, and length of a variable that is used in a DATA step.

● The following functions are enhanced:

COMPRESS

accepts a third optional argument that can modify the characters in the second
argument.

EXIST

accepts all SAS data library type members. A third optional argument enables you
to specify a generation data set number.

INDEXW

accepts a third optional argument that enables you to use delimiters for inter-word
boundaries.

PRXMATCH

accepts an argument that enables you to use a Perl regular expression.

SUBSTR (left of=)

assigns a length of 8 to an undeclared variable when the function is compiled.

Informats

● The maximum length for character informat names is increased to 30. The maximum
length for numeric informat names is increased to 31.
 ● The following informats are new:

ANYDTDTE

extracts date values from DATE, DATETIME, DDMMYY, JULIAN, MMDDYY,

MONYY, TIME, or YYQ informat values.

ANYDTDTM

extracts datetime values from DATE, DATETIME, DDMMYY, JULIAN, MMDDYY,

MONYY, TIME, or YYQ informat values.

ANYDTTME

extracts time values from DATE, DATETIME, DDMMYY, JULIAN, MMDDYY,

MONYY, TIME, or YYQ informat values.

STIMERw.

reads time values and determines whether the values are hours, minutes, or
seconds; reads the output of the STIMER system option.

ARM Macros

%ARMCONV, the new ARM macro, converts an ARM log that is created in SAS 9.0 and later,
which uses a simple format, into the ARM log format that is used in SAS 8.2, which is more
detailed.

SAS Utility Macro

%DS2CSV, the new SAS utility macro, converts SAS data sets to comma-separated values
(CSV) files.

Statements

● The following statements are new:

ODS Statements
 control different features of the Output Delivery System. For more information
about these statements, see the SAS Output Delivery System: User's Guide.

FILENAME, CLIPBOARD Access Method

enables you to read text data from and write text data to the clipboard on the host
machine.

DECLARE

declares a DATA step component object; creates an instance of and initializes

data for a DATA step component object.

_NEW_

creates an instance of a DATA step component object.

PUTLOG

writes a message to the SAS log.

● The following statements are enhanced:

FILENAME, FTP Access Method

supports directory services and multiple FTP service commands.

FILENAME, URL Access Method

supports Secure Sockets Layering (SSL).

LIBNAME statement

the following options are new:

COMPRESS=

controls the compression of observations in output SAS data sets in a SAS

data library.
 CVPBYTES=

specifies the number of bytes to use in order to expand character variable

lengths when processing a SAS data set that requires transcoding.

CVPENGINE=

specifies which engine to use in order to process character variable lengths

in a SAS data set that requires transcoding.

CVPMULTIPLIER=

specifies the multiplier value to use in order to expand character variable

lengths when processing a SAS data set that requires transcoding.

INENCODING=

overrides the encoding for input processing.

OUTENCODING=

overrides the encoding for output processing.

LIBNAME Statement for WebDAV Server Access

associates a libref with a SAS library on a WebDAV server.

System Options

● The following system options are new:

ARMAGENT=

specifies an ARM agent, which is an executable module that contains a vendor's

implementation of the ARM API.

ARMLOC=

specifies the location of the ARM log.

ARMSUBSYS=

enables and disables the ARM subsystems that determine which internal SAS
processing transactions should be logged.

AUTHPROVIDERDOMAIN=

associates a domain suffix with an authentication provider.

AUTOSAVELOC=

specifies the location of the Program Editor autosave file.

BYSORTED

specifies whether observations in one or more data sets are sorted in alphabetical
or numerical order or are grouped in another logical order.

CMPLIB=

specifies one or more SAS catalogs that contain compiler subroutines that should
be included during program compilation.

CMPOPT

specifies which type of code generation optimizations should be used in the SAS
language compiler.

CPUCOUNT=

specifies the number of processors that the thread-enabled applications should

assume are available for concurrent processing.

DMSLOGSIZE=

specifies the maximum number of rows that can be displayed in the Log window
in the SAS windowing environment.

DMSOUTSIZE=

specifies the maximum number of rows that can be displayed in the Output
 window in the SAS windowing environment .

DMSSYNCHK

enables syntax checking for multiple steps in the SAS windowing environment.

DTRESET

updates the date and the time in the SAS log and in the listing file.

EMAILAUTHPROTOCOL=

specifies the authentication protocol for SMTP e-mail.

EMAILID=

specifies the identity of the individual who is sending e-mail from within SAS.

EMAILPW=

specifies your e-mail login password.

ERRORBYABEND

specifies how SAS responds to BY-group error conditions.

FONTSLOC=

specifies the location that contains the SAS fonts that are loaded by a printer to
use with Universal Printing.

HELPENCMD

specifies whether SAS uses the English version or the translated version of the
keyword list for the command-line Help.

IBUFSIZE=

specifies the buffer page size for an index file.

LOGPARM=
 controls when SAS log files are opened and closed and (in conjunction with the
LOG= system option) how they are named.

METAAUTORESOURCES=

identifies which resources should be assigned at SAS initialization.

METACONNECT=

identifies which named connection from the metadata user profiles should be
used as the default value for logging into the SAS Metadata Server.

METAENCRYPTALG=

specifies which type of encryption should be used when communicating with a

SAS Metadata Server.

METAENCRYPTLEVEL=

specifies what should be encrypted when communicating with a SAS Metadata

Server.

METAID=

identifies the current SAS version that is installed on the SAS Metadata Server.

METAPASSWORD=

specifies the default password for the SAS Metadata Server.

METAPORT=

specifies the TCP port for the SAS Metadata Server.

METAPROFILE=

specifies which file contains the SAS Metadata Server user profiles.

METAPROTOCOL=
 specifies which network protocol should be used for communicating with the SAS
Metadata Server.

METAREPOSITORY=

specifies which default SAS Metadata Repository should be used on the SAS
Metadata Server.

METASERVER=

specifies the address of the SAS Metadata Server.

METAUSER=

specifies the default user ID for logging on to the SAS Metadata Server.

PAGEBREAKINITIAL

begins the SAS log and listing files on a new page.

QUOTELENMAX

specifies that SAS write a warning to the SAS log about the maximum length that
can be used for strings that are enclosed in quotation marks.

SORTEQUALS

controls the order in which PROC SORT arranges observations that have
identical BY values in the output data set.

SYSPRINTFONT

specifies the font for the current default printer.

SYNTAXCHECK

specifies whether to validate SAS program syntax.

TERMSTMT=

specifies which SAS statements should be executed when the SAS session is
 terminated.

TEXTURELOC=

specifies the location of textures and images that are used by ODS styles.

THREADS

specifies that SAS use threaded processing if it is available.

TOOLSMENU

specifies whether to include or to suppress the Tools menu in windows that

display SAS menus.

UUIDCOUNT

specifies the number of UUIDs that should be acquired each time the UUID
Generator Daemon is used.

UUIDGENHOST

identifies the host and the port for the UUID Generator Daemon.

UTILLOC=

specifies a set of file system locations in which applications can store utility files.

VALIDFMTNAME=

specifies the length of format and informat names that can be used when creating
new SAS data sets and format catalogs.

VIEWMENU

specifies whether to include or to suppress the View menu in windows that display
menus.

V6CREATEUPDATE=

controls or monitors the creation of new, version 6 SAS data sets or the updating
 of existing, version 6 SAS data sets.

● The following system options have been enhanced:

CMPOPT=

specifies which type of code generation optimizations should be used in the SAS
language compiler.

SORTSIZE=

specifies the amount of memory that is available when using the SORT
procedure.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the Windowing Environment for Base SAS

9.0 and 9.1
Overview

The windowing environment in Base SAS 9.0 and later improves usability and SAS
performance by providing the following new and enhanced features:

● a new window for viewing ODS documents

● a new window for managing metadata objects

● two new wizards for importing files to, exporting files from, and copying and pasting files
to Microsoft Excel 2002 and Microsoft Access 2002

● new capability in the Find window that enables expanded searches of catalogs and
libraries

● improvements in the Explorer Options dialog box

● improvements in the File Shortcut Assignment dialog box.

Note:

● This section describes the features of the SAS windowing environment that are new or
enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 (and later) is supported
on both OS/390 and z/OS operating systems and, throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

Details

● The new Documents window enables you to view your ODS documents.

● The new Metadata Browser window enables you to manage your metadata objects.
 ● The new Export wizard exports data to Microsoft Excel 2002 spreadsheets and
Microsoft Access 2002 tables. The new data sources are available under the Windows
operating environment on a 32-bit platform if your site has a license for the SAS/
ACCESS Interface for PC Files.

● The Export Wizard also identifies a specific spreadsheet in a workbook. Exporting to

multiple sheets is available for Microsoft Excel 97, 2000, and 2002 spreadsheets under
the Windows operating environment on a 32-bit platform if your site has a license for the
SAS/ACCESS Interface for PC Files.

● The new Import wizard imports Microsoft Excel 2002 spreadsheets and Microsoft
Access 2002 tables. The new data sources are available under the Windows operating
environment on a 32-bit platform if your site has a license for the SAS/ACCESS
Interface for PC Files.

● Data sets can now be copied and saved into a Microsoft Excel file and saved as HTML.

● Explorer property sheets have been re-designed to make them easier to use.

● The Find window now enables you to search all the entries in the catalogs of any library
that you choose.

● The re-designed Explorer Options dialog box has tabbed pages for General, Files,
Entries, Members, and Metadata. On the General Files tabbed page, the Remember
Column Widths check box has been added.

● The File Shortcut Assignment dialog box can now be used to specify a proxy server and
related information.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in Moving and Accessing SAS 9.0 and 9.1 Files
Overview

The following strategies in Base SAS are available for moving and accessing SAS files
between operating environments that run different releases of SAS:

● Cross-Environment Data Access (CEDA)

● CPORT and CIMPORT procedures

● XPORT engine with the DATA step or the COPY procedure

● XML engine with the DATA step or the COPY procedure.

Note: This section describes the features that are new to the topic of moving SAS files since
SAS 8.2. Using SAS CONNECT and SAS/SHARE to move or access SAS files are discussed
in the SAS/CONNECT User's Guide and the SAS/SHARE User's Guide.

Details

Cross-Environment Data Access (CEDA)

CEDA is a simple strategy for file access across a network. CEDA enables you to read a
network-mounted SAS file from any directory-based operating environment that runs SAS 8 or
later, regardless of the file format of the SAS file being accessed.

CEDA dynamically converts between the native formats of the source and target operating
environments that run under different architectures (for example, UNIX and Windows). CEDA
eliminates having to convert a file to transport format.

CPORT and CIMPORT Procedures

In most cases, in order to move a SAS file between operating environments, you can use the
CPORT and CIMPORT procedures and FTP (File Transfer Protocol) to create a transport file
at the source machine, transfer that file across the network, and restore the transport file to
native format at the target machine.

CAUTION:
Moving or accessing SAS files is not the same as migrating SAS files.

Migration of SAS files (data and applications) is not discussed in this documentation. For
details about migrating SAS files, see the Migration Community at support.sas.com/rnd/
migration.

XPORT Engine with the DATA Step or the COPY Procedure

The XPORT engine creates files in transport format that can be transferred across operating
environments, and directed to multiple target operating environments that run different
releases of SAS. Transport files that are created by the XPORT engine can be transferred
across operating environments and read using the XPORT engine with the DATA step or
PROC COPY.

XML Engine with the DATA Step or the COPY Procedure

The XML engine imports and exports XML documents. The XML format provides increased
cross-architectural compatibility by storing numeric values as character data and by identifying
the character encoding in a file header. XML files can be transferred across operating
environments and read using the XML engine with the DATA step or with PROC COPY.

The XML engine was introduced in SAS 8.2 and is completely documented in the SAS 9.1
XML LIBNAME Engine User's Guide. Using the XML engine as a strategy for moving SAS
files across operating environments is introduced in this documentation for SAS 9.1.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS 9.0 and 9.1 Output Delivery System

Overview

The Output Delivery System (ODS) provides an almost limitless number of choices for
reporting and displaying analytical results with a greater variety of formatting selections and
output destinations.

SAS 9.0 and 9.1 provide an array of markup languages including HTML4 and XML. The
TEMPLATE procedure and the new tagset template enable you to modify any markup
language that SAS provides, or to create your own markup language for output.

The new experimental ODS GRAPHICS statement enables you to produce graphics output.

The new DOCUMENT procedure enables you to customize or modify your output hierarchy
and replay your output to different destinations without rerunning the PROC or DATA step.

Note:

● This section describes the features of the SAS Output Delivery System that are new or
enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 is supported on both
OS/390 and z/OS operating systems and, throughout this document, any reference to z/
OS also applies to OS/390, unless otherwise stated.

Details

SASEDOC Engine

The new SASEDOC libname engine enables you to associate a SAS libref (library reference)
with one or more output objects that are stored in an ODS document as a SAS data set.

ODS Statements
The following ODS statements are new:

ODS CHTML

produces compact, minimal HTML output with no style information.

ODS CSVALL

produces output that contains columns of data values that are separated by commas.
ODS CSVALL produces tabular output with titles, notes, and bylines.

ODS DECIMAL_ALIGN

aligns values by the decimal point in numeric columns when no justification is specified.

ODS DOCBOOK

produces XML output that conforms to the DocBook DTD by OASIS.

ODS DOCUMENT

produces a hierarchy of output objects that enables you to create multiple ODS output
formats without rerunning a PROC or DATA step.

ODS GRAPHICS (Experimental)

enables ODS automatic graphic capabilities.

ODS HTMLCSS

produces HTML output with cascading stylesheets that is similar to ODS HTML output.

ODS IMODE

produces HTML output as a column of output that is separated by lines.

ODS MARKUP

produces SAS output that is formatted using one of many different markup languages.

ODS PCL
 produces printable output for PCL (HP LaserJet) files.

ODS PDF

produces PDF output.

ODS PHTML

produces basic HTML output that uses twelve style elements and no class attributes.

ODS PS

produces PostScript (PS) output.

ODS USEGOPT

enables the use of graphics option settings for graphic output.

ODS WML

produces a Wireless Markup Language (WML) DTD with a simple list of URLs for a
table of contents.

● The ODS PRINTER statement now supports the following options:

BACKGROUND=

specifies whether background colors are printed in text.

BOOKMARKLIST=

specifies whether to generate and display the list of bookmarks for a PDF file.

BOOKMARKGEN=

controls the generation of bookmarks in a PDF file.

COLUMNS=
 specifies the number of columns to create on each page of output.

TEXT=

inserts text into your output.

● The ODS RTF statement now supports the following options:

COLUMNS=

specifies the number of columns to create on each page of output.

TEXT=

inserts text into your output.

● The ODS MARKUP statement now supports the following TAGSETS:

GRAPH

produces markup for graphical output produced by SAS/GRAPH.

SASFMT

produces user-defined format markup tags for the XML engine.

SASXMISS

produces alternate missing-value markup tags for the XML engine.

SASXMNSP

produces alternate "no space in text" value markup for the XML engine.

STATGRAPH

produces markup for statistical graphs that are generated by SAS procedures.

ODS Procedures
● DOCUMENT procedure

❍ The new DOCUMENT procedure enables you to do the following:

■ produce multiple reports with a single run of a procedure or data query.

■ modify and customize your output file hierarchy by rearranging, duplicating,

or removing specific tables.

■ modify and customize your output file hierarchy by rearranging, duplicating,

or removing the entire output of procedures and data queries.

■ generate output for one or more ODS destinations, using the newly
transformed output hierarchy.

■ store the ODS output objects in raw form. The output is kept in the original
internal representation as a data component plus a table definition.

❍ The new LIB= option in the DOC statement enables you to list documents that are
in the specified library.

❍ The #BYLINE, #BYVAL, and #BYVAR directives can now be used in seven of the
PROC DOCUMENT statements.

❍ The new AFTER option in the OBPAGE statement adds or deletes page breaks
after output objects.

● TEMPLATE procedure

❍ The following new statements are provided in the TEMPLATE procedure.

■ The DEFINE TAGSET statement creates and modifies tagset definitions

using a new definition statement and the new tagset attribute statements.

■ The DEFINE EVENT statement determines what is written to the output file
using the new definition statement and the new event attribute statements.

❍ The new boolean ABSTRACT= attribute can be applied to styles. If this attribute
is set to TRUE, then the style will not appear in the CSS files or LaTeX style files.

❍ The new ALT, LONGDESC, ACRONYM, and ABBR options in the DEFINE
 TABLE, DEFINE COLUMN, and DEFINE HEADER statements provide
accessibility features in PROC TEMPLATE.

❍ The following accessibility attributes have been added to the TEMPLATE

procedure.

ABBR= is a column, header, and footer attribute that provides an

abbreviated form of the cell's content, which can be displayed in
place of a cell's content.
SUMMARY= is a table attribute that provides a summary of the purpose and
structure of a table.
❍ The new INDENT style element enables you to specify the distance from the left
side of a cell for indentation purposes. The INDENT style element specifies where
to begin the text.

❍ The _LABEL_ keyword is now treated as a dynamic variable, and it can be used
just like any other dynamic variable in PROC TEMPLATE. Previously, _LABEL_
was a keyword that could only be used by itself in table and column headers.

❍ In the TEMPLATE procedure, if you create HTML4 output, then the

BORDERCOLORDARK and BORDERCOLORLIGHT style attributes are ignored
because they are not part of the HTML4 standard. If you want a color border, then
use the BORDER= style attribute.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in Data Security Technologies in SAS 9.1.2

and 9.1.3
Overview of Data Security Technologies

Data Security Technologies in SAS describes the technologies used by SAS to protect the
confidentiality of data that is exchanged in client/server data transfers.

Details about Data Security Technologies

Data Security Technologies in SAS consolidates the information that was previously
contained in multiple SAS documents. The data security technologies that are used by SAS
are provided by the following:

● SASProprietary

● SAS/SECURE

● SSL (Secure Sockets Layer)

● SSH (Secure Shell)

Note:

Transport Layer Security (TLS) is the successor to SSL V3.0. The Internet Engineering Task
Force (IETF) adopted SSL V3.0 as the de facto standard, modified it, renamed it TLS V1.0,
and adopted it as a standard.

SAS/SECURE SSL Add-In Package

In order to use the SAS 9.1.3 SSL software, you must review the licensing terms and
download the appropriate SAS/SECURE SSL Add-In Package from the SAS download Web
site.
SSH Functionality

Although SAS 9.1.3 software does not include a programming interface to SSH (Secure Shell)
functionality, SAS does support the tunneling feature of SSH that enables a SAS client to
make an encrypted connection to a SAS server.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS 9.0 and 9.1 Macro Language

Facility
Overview

There are several enhancements to the Macro Language Facility including a new automatic
macro variable, new comparison operators, new SAS system options, new macro statements,
new functions, and a new option for the %MACRO statement.

Note:

● This section describes the features of the SAS Macro Facility that are new or enhanced
since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 is supported on both
OS/390 and z/OS operating systems and, throughout this document, any reference to z/
OS also applies to OS/390, unless otherwise stated.

New Automatic Macro Variable

● To take advantage of the new parallel-processing abilities in SAS, the new read-only
automatic macro variable, &SYSNCPU contains the current number of CPUs that SAS
can use during the current SAS session.

New Comparison Operators

● The IN mnemonic operator is a binary comparison operator similar to that of the DATA
step, except that the operand on the right side is simply a list of values and is not
enclosed in parentheses. The IN operator compares the value of the operand on the left
side against the list of values in the operand on the right side.

● You can use the # character as an alternate spelling for the IN operator.

New SAS System Options

These are the new macro system options:

● The MPRINTNEST system option enables the macro nesting information to be

displayed in the MPRINT output in the SAS log.

● The MLOGICNEST system option enables the macro nesting information to be

displayed in the SAS log.

● The MINDELIMITER system option specifies the character to be used as the delimiter
for the macro IN operator.

● The MCOMPILENOTE system option specifies that a NOTE be issued to the SAS log
when the compilation of a macro is completed.

● The MAUTOLOCDISPLAY system option specifies that the source location of the
autocall macro be displayed in the SAS log when the autocall macro is invoked.

New Macro Statements

● The %ABORT statement stops the macro that is executing along with the current DATA
step, SAS job, or SAS session.

● The %RETURN statement causes normal termination of the currently executing macro.

● The %COPY statement copies specified items from a SAS macro library.

New Macro Functions

● The %SYMEXIST function returns an indication of the existence of a macro variable.

● The %SYMGLOBL function returns an indication as to whether a macro variable is

global in scope.

● The %SYMLOCAL function returns an indication as to whether a macro variable is local

in scope.

New Option for the %MACRO Statement

 ● SOURCE is a new option that is issued in the %MACRO statement. When used with the
existing STORE option, the SOURCE option combines and stores the source of the
compiled macro with the compiled macro code as an entry in a SAS catalog in a
permanent SAS data library.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS 9.1 and 9.1.3 Metadata LIBNAME

Engine
Overview

The SAS 9.0 (and later) metadata engine provides secure access to SAS data. By
incorporating metadata, this engine augments and controls access to the data.

Note: This section describes the features of the SAS metadata engine that are new or
enhanced since SAS 9.0.

Details

● In SAS 9.0 (and later), the metadata engine can create a new table in a data source and
create its associated metadata. It can also delete a table in a data source and delete its
associated metadata.

● In SAS 9.0 (and later), the metadata engine, in conjunction with the SAS Open Metadata
Architecture Authorization Facility, enables an administrator to specify user privileges in
order to control which data they are allowed to access. For more information, see
Metadata Requirements for Using the SAS Open Metadata Architecture Authorization
Facility to Control Data Access.

● The new LIBURI= and LIBRARY= options in the LIBNAME statement provide additional
methods for referencing the SASLibrary metadata object.

● The new METAOUT= option in the LIBNAME statement enables you to control the
results of output processing for a library.

● The new METAOUT= data set option enables you to control the results of output
processing for a specific table.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS 9.1 Scalable Performance Data

Engine
Overview

The SAS Scalable Performance Data Engine (SPD Engine) is a SAS LIBNAME engine that
provides rapid data delivery to applications by using multiple CPUs to provide parallel data I/O.
The SPD Engine is not intended to replace the default Base SAS engine. Rather it is intended
for rapid processing of very large data sets that are stored in partitions across multiple disk
volumes.

Note: z/OS is the successor to the OS/390 operating system. The SAS 9.1 Scalable
Performance Data Engine is supported on both OS/390 and z/OS operating systems and,
throughout this document, any reference to z/OS also applies to OS/390, unless otherwise
stated.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS 9.0, 9.1, and 9.1.3 XML LIBNAME
Engine
Overview

The SAS 9.1 (and later) XML engine imports and exports a broader variety of XML documents.
The XMLMAP= option specifies a separate XML document that contains specific XMLMap
syntax. The XMLMap syntax tells the XML engine how to interpret the XML markup in order to
successfully import an XML document.

Note: This section describes the features of the XML LIBNAME engine in SAS that are new
or enhanced since SAS 8.2.

Details

● The LIBNAME Statement Syntax contains the following new options:

❍ The ODSRECSEP= option controls the generation of a record separator that

marks the end of a line in the output XML document.

❍ The XMLCONCATENATE= option enables you to import an XML document that

contains multiple XML documents, which are concatenated into one file.

❍ The XMLFILEREF= option enables you to specify a fileref for the XML document
that is different from the libref. If the fileref and the libref are the same, you do not
need to specify the XMLFILEREF= option or the name of the XML document.

❍ Beginning in SAS 9.1, the option name XMLSCHEMA= specifies an external file
that contains separate schema output.

❍ The XMLPROCESS= option determines how the XML engine processes

character data that does not conform to W3C specifications.

● The LIBNAME Statement Syntax contains the following enhancements:

❍ The XMLTYPE= option now supports the MSACCESS format type. MSACCESS
is the XML format for the markup standards that are supported for a Microsoft
 Access database.

❍ In SAS 9.1, you can store and access XMLMaps as metadata objects in a SAS
Metadata Repository. The following new metadata options enable you to access a
particular XMLMap in a specific repository: METAPASS=, METAPORT=,
METAREPOSITORY=, METASERVER=, and METAXMLMAP=.

❍ Beginning in SAS 9.1.3, the XMLTYPE= option supports the CDISCODM format
type. CDISCODM is the XML format for the markup standards that are defined in
the Operational Data Model (ODM) that is created by the Clinical Data
Interchange Standards Consortium (CDISC), which conforms to the 1.2 schema
specification. The new options FORMATACTIVE=, FORMATNOREPLACE=, and
FORMATLIBRARY= are used with the CDISCODM format type to specify
transcoding preferences.

❍ The XMLMETA= option specifies whether to include metadata-related information

in the exported markup. In SAS 9.1, the values for the XMLMETA= option are
changed to DATA, SCHEMADATA, and SCHEMA.

Note: Prior to SAS 9.0, the functionality of the XMLMETA= option was
performed by using the keyword XMLSCHEMA=. In SAS 9.0 (and later), the
name of the XMLSCHEMA= option is changed to XMLMETA=.

● In the XMLMap Syntax Version 1.2, the content for the DATATYPE element (which
specifies the type of data being read from the XML document for the variable) is
changed to conform directly to the XML Schema data types specification. For example,
in earlier versions of the DATATYPE element, the form <DATATYPE>DT-8601</
DATATYPE> was accepted. In version 1.2, the form <DATATYPE>dateTime</
DATATYPE> is accepted.

● Several ISO 8601 SAS formats and informats now support the international standard for
the representation of dates and times.

● Using the LABEL= data set option no longer results in a warning message. However,
the XML engine does not persist the information.

● SAS XML Mapper (previously named XML Atlas) is a graphical interface that generates
or modifies the XML markup for an XMLMap.

● The new XMLMap Manager (a plug-in used with SAS Management Console) provides
centralized management of XMLMaps as metadata objects in a SAS Metadata
Repository.
Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

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

Windows
Overview

New and enhanced features in Base SAS improve ease of use and SAS performance under
the Windows environment:

● SAS now runs under 32- and 64- bit Windows XP and Windows Server 2003 operating
environments.

● SAS servers and PCs can use memory-based SAS libraries to process SAS data.

● Network security is enhanced by using Secure Sockets Layer (SSL).

● SAS is now able to sort data using the high-performance sorting tool SyncSort for
Windows, by Syncsort, Incorporated, if you have SyncSort installed at your site.

● Sharing files between UNIX and Windows has been simplified.

● You can start SAS with the same destination printer that was specified when you ended
your last SAS session.

● During initialization, SAS looks in the Windows user profile directory for a configuration
file if you do not specify a configuration file at SAS invocation.

● The Enhanced Editor autosave files are now saved to the Application Data folder.

● Accessibility aids can now access many of the SAS windows and dialog boxes.

Note:

● This section describes the features of SAS Companion for Windows that are new or
enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. Throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.
Basic Operation of SAS

The basic operation of SAS has been enhanced as follows:

● You can store a customized configuration file in the Windows user profile folder. During
invocation, SAS searches this folder for a configuration file named either SASV9.CFG
or .SASV9.CFG.

● Performance can be improved by processing SAS data in memory-based SAS libraries.

● Use Secure Sockets Layer (SSL) for secure networks. For information about SSL, see
the SAS/CONNECT User's Guide.

● SAS can now sort data by using SyncSort for Windows if you have Syncsort installed at
your site.

● To use the same destination printer (not the default printer) from one SAS session to the
next, use the PRTPERSISTDEFAULT system option when you start SAS.

● To send an e-mail attachment with records that contain more than 256 characters, the
ATTACH email-option in the FILENAME, EMAIL statement now supports the LRECL
and RECFM options.

● When you attach the contents of the Results Viewer to an e-mail message, the file is
attached according to its file type of either .html or .rtf.

● In 64-bit operating environments, the V6 engine is a read-only engine.

● New keyboard shortcuts are available for resizing the docking view and displaying
property sheets from a window that contains a Tree view or a List view.

● If a fatal error occurs during SAS initialization or termination and the MSG dialog box is
not available or the SAS log is not open, error messages are written to the SAS console
log.

Accessibility

The following features are new:

 ● Many of the SAS windows and dialog boxes can be read by accessibility aids.

● The ACCESSIBILITY system option enables access to the Customize Tools dialog box
Customize tab and some SAS Properties dialog boxes.

● Text can be enlarged by using the SYSGUIFONT system option.

● Accessibility aids might have fewer problems reading menus if you exclude menu icons.

● You can use the keyboard to resize the docking view.

● When a window (such as SAS Explorer) contains a List view, you can use the Sort
Columns dialog box to sort the list by the detail information.

● You can resize the details columns in a List view by using the Column Settings dialog
box.

Enhanced Editor

The following features are new:

● To open new or existing files in an Enhanced Editor window, you can select New
Program and Open Program from the File menu.

● The Enhanced Editor now recognizes XML files that have the .xml file extension.

● When you open a file in the Enhanced Editor, the tabs can be converted to spaces.

● The full path and the filename of the last submitted program or catalog entry is available
by using environment variables.

● Submit one or more lines of code without submitting your complete program by using
the SUBTOP command.

● Line numbers can be turned on and off by using the NUMS command.

The following features have been enhanced:

● The Enhanced Editor accepts lines of data in a DATALINES statement that are longer
 than 256 characters into one observation without using FILENAME statement options.

● Autosave files are saved to the Application Data folder.

● The default value for the Enhanced Editor Script appearance option is determined by the
Windows regional options.

The following feature has been removed:

● The Enhanced Editor no longer prompts you to reload a file on a disk that has been
updated.

Graphical User Interface

The following features are new in the SAS main window:

● The Universal Printing commands are available from the File menu when you specify
the UPRINTMENUSWITCH system option.

● More windowing environment workspace is available by minimizing the docking view.

● A maximum of 20 customized help files can be added to the Help menu.

● The Print and Copy toolbar buttons are always enabled if they are commands in a
customized toolbar.

● To print line numbers, page numbers, and to print in color, select the Options button in
the Print dialog box.

● The About SAS System dialog box includes information about the SAS version and the
Windows operating environment that you are currently using.

SAS Language Elements

Commands

The following SAS commands are new:

 ● When a SAS window (such as the SAS Explorer window) contains a List view, you can
resize the columns by using the DLGCOLUMNSIZE command.

● Sort the columns in a List view by using the DLGCOLUMNSORT command.

● Three new docking view commands, WDOCKVIEWMINIMIZE,

WDOCKVIEWRESTORE, and WDOCKVIEWRESIZE, enable the docking view to be
minimized, restored, and resized.

● To change the active window to the editor window that was last edited, use the WPGM
command.

Functions

The following have specific functionality in the Windows operating environment:

● The DINFO Function, the DOPTNAME Function, and the DOPTNUM Function return
directory information.

● To delete an external file, use the FDELETE Function.

● Verify the existence of an external file by using either the FEXIST Function or the
FILEEXIST Function.

● To assign or clear a fileref, use the FILENAME Function.

● Verify that a filref has been assigned by using the FILEREF Function.

● Obtain information about a file by using the FINFO Function, the FOPTNAME Function,
and the FOPTNUM Function.

● To assign or clear a libref, use the LIBNAME Function.

Statements

The following statements have been enhanced:

● Share files between the UNIX and Windows operating environments by using the
TERMSTR host option in the FILE and INFILE statements.
 ● ^Z is interpreted as character data and not as an end-of-file marker when you specify
the IGNOREDOSEOF host option in the %INCLUDE, FILENAME, FILE, and INFILE
statements.

System Options

The following system options are new:

● Accessibility features are extended for the Customize Tools dialog box and for some
Properties dialog boxes by using the ACCESSIBILITY system option.

● If you create a customized table of contents and index for the SAS Help and
Documentation, use the HELPTOC and HELPINDEX system options to specify the file
location.

● Use memory-based SAS libraries to improve SAS performance by using the

MEMBLKSZ and MEMMAXSZ system options.

● Improve the access to menus by accessibility aids when you use the NOMENUICONS
system option.

● The same destination printer can persist from one SAS session to another by using the
PRTPERSISTDEFAULT system option.

● Stop the SLEEP window from displaying when you use the SLEEP function or the
WAKEUP function by specifying the NOSLEEPWINDOW system option.

● If you have SyncSort for Windows installed at your site, use these system option to
specify sort options:

❍ SORTPGM system option specifies to sort by using SyncSort for Windows.

❍ The SORTANOM system option enables you to specify options for SyncSort for
Windows.

❍ Use SORTCUT and SORTCUTP system options to specify the number of

observations and bytes above which SyncSort for Windows is used instead of the
SAS sort.

❍ Use the SORTDEV system option to specify a temporary directory for files that
 are created by SyncSort for Windows.

❍ The SORTPARM system option enables you to specify SyncSort parameters.

● SSLCERTISS, SSLCERTSERIAL, SSLCERTSUBJ, SSLCLIENTAUTH, and

SSLCRLCHECK are new system options that support Secure Sockets Layer (SSL)
authentication.

● To enlarge text for easier readability, use the SYSGUIFONT system option.

● The Universal Print commands are available from the File menu when you specify the
UPRINTMENUSWITCH system option.

The following system option has been enhanced:

● The new default value for the SORTSIZE system option is MAX.

The EMAILID and EMAILPW options, which were previously available only in the Windows
environment, are now available in all operating environments. See SAS Language
Reference: Dictionary.

Macros

The SYSSCPL automatic macro variable returns a value for the Windows XP and Windows
Server 2003 operating environments.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

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:

● SAS for the AIX, HP-UX, and Solaris operating environments is 64-bit only.

● SMTP (Simple Mail Transfer Protocol) is now the default mail handler.

● Sharing files between UNIX and Windows has been simplified.

● 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.

● Universal Printing is the new default printing mechanism. SAS does not support host
printing functionality.

Note:

● This section describes the features of SAS software under the UNIX operating
environment that are new or enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. Throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

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

● The default mail handler is SMTP (Simple Mail Transfer Protocol), which supports
attachments.

● The new BCC option in the FILENAME statement enables you to send blind copy e-
mails during a SAS session.

● Using the Send Mail dialog box, you can now do the following:
 ❍ include the contents of an active SAS window (such as the Program Editor or
Log) in the body of your e-mail.

❍ attach the contents of a non-text window to your e-mail. Examples of non-text

windows include a graph generated by SAS/GRAPH and an image in your PROC
REPORT output.

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

● The SAS.useNativeXmTextTranslations X resource specifies whether any

XmText widget translations are inherited by all instances of the Text, Combo Box, and
Spin Box widgets that are used by the SAS X Motif user interface.

● The SAS.webBrowser resource is no longer supported. The SAS.helpBrowser

resource now specifies the pathname of the World Wide Web browser for use when
viewing the online help or when the WBROWSE command is issued.

● The following resources that were used to control your ODS results are no longer
supported:

❍ SAS.resultsHTML

❍ SAS.resultsUseWork
 ❍ SAS.resultsTmpDir

❍ SAS.resultsHTMLStyle

❍ SAS.resultsListing

❍ SAS.resultsAutoNavigate

To set the values for your ODS output, use the Results tab in the Preferences dialog
box.

SAS Language Elements

Commands

The following commands are obsolete:

● DLGPRT

● DLGPRTMODE

● DLGPRTPREVIEW

● DLGPRTSETUP.

Functions and CALL Routines

● To call a specific routine or module that resides in a shared library, you can use the
MODULE function.

● You can store the contents of a memory address in a numeric variable on 32-bit and 64-
bit platforms by using the PEEKLONG function. This function replaces the PEEK
function, which was valid only on 32-bit platforms.

Statements

● The following option is new in the FILE, FILENAME, and INFILE statements:
 ❍ TERMSTR= enables the sharing of UNIX and PC formatted files.

● The following options are new in the %INCLUDE statement:

❍ BLKSIZE= specifies the number of bytes that are physically read or written in an I/
O operation.

❍ ENCODING= specifies the encoding to use when reading from the specified
source.

❍ LRECL= specifies the record length (in bytes).

❍ RECFM= controls the record format.

Procedures

● To see all the system options that have been set by your site administrator, use the
RESTRICT option in the OPTIONS procedure.

● The BMDP procedure is obsolete.

System Options

● The following system options are new:

❍ You can specify the location of the Program Editor autosave file by using the
AUTOSAVELOC system option.

❍ If you create a customized table of contents and index for the SAS Help and
Documentation, use the HELPINDEX and HELPTOC system options to specify
the file location.

❍ SSLCALISTLOC, SSLCERTLOC, SSLCLIENTAUTH, SSLCRLCHECK,

SSLCRLLOC, SSLPVTKEYLOC, and SSLPVTKEYPASS are new system options
that support Secure Sockets Layer (SSL) authentication.

❍ To set permissions for the temporary Work library when it is created, use the
WORKPERMS system option.
 ● The following system options are enhanced:

❍ If you specify only a directory path for the ALTLOG, LOG, ALTPRINT, or PRINT
system options during SAS invocation, then the default filename for your log or
procedure output file is filename.LOG or filename.LST, where filename is the
name of your SAS job.

❍ SMTP (Simple Mail Transfer Protocol) is the new default for the EMAILSYS
system option.

❍ V9 is a new value for the ENGINE system option.

❍ MAX is the new default for the SORTSIZE system option. The value of MAX is
based on your operating environment.

● The following system options have values that are obsolete:

❍ Because the CoSort utility is no longer supported, cosort is not a valid value for
the SORTNAME system option.

● The following system options are obsolete:

❍ PROCLEAVE

❍ SORTLIB

❍ SYSLEAVE

❍ XPRINTNM.

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

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

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

OpenVMS Alpha
Overview

New and enhanced features in Base SAS improve ease of use and SAS performance under
the OpenVMS Alpha operating environment:

● SAS is built to take advantage of the OpenVMS Alpha 64-bit architecture.

● Your site administrator can restrict system options for your site.

● You can create filenames similar to those on UNIX and Windows by using Extended
(ODS-5) Syntax on ODS-5 enabled volumes.

● Support for cluster-level logicals has been incorporated into SAS in all areas where multi-
level logical definitions were previously supported.

● SMTP (Simple Mail Transfer Protocol) is now the default for sending mail from within
SAS.

Note:

● This section describes the features of SAS software under the OpenVMS Alpha
operating environment that are new or enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. Throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

Migrating Your Existing SAS Files to SAS 9.1

Starting in SAS 9.0, SAS is built to take advantage of the OpenVMS Alpha 64-bit architecture.
The following list explains the compatibility of your existing SAS files with SAS 9.1:

● All of your Version 7 and Version 8 SAS files (except SAS catalogs) are compatible with
SAS 9.1. To take advantage of the new SAS®9 features and access your existing SAS
 catalogs, convert your Version 7 and Version 8 files by using the MIGRATE procedure.

● SAS 9.1 only supports input processing for Version 6 data files using the V6 read-only
engine. To access all of your Version 6 files in SAS 9.1, you need to migrate your
Version 6 data libraries.

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

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.

Restricted System Options

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

Support for Extended (ODS-5) Syntax on ODS-5 Enabled Volumes

SAS supports the Extended (ODS-5) Syntax on ODS-5 enabled volumes. The ODS-5 syntax
allows longer filenames, supports more characters within filenames, preserves case within
filenames, and supports deeper directory structures. These extended file specifications enable
users to create filenames similar to those in UNIX and Windows. The ODS-5 and Windows file-
naming conventions are similar. For example, if a filename exists in all uppercase, then any
lowercase or uppercase reference to that file will resolve to uppercase.

When using the ODS-5 syntax, you must issue an X statement before using a DCL command
in SAS.

Support for Cluster-Level Logicals

OpenVMS 7.2 introduced the new concept of clusterwide logical definitions. Support for cluster-
level logicals has been incorporated into SAS in all areas where multi-level logical definitions
were previously supported. See the OpenVMS documentation for more information about
cluster-level logical definitions.

SAS will use a clusterwide logical when you:

● specify a cluster-level configuration file

● specify a cluster-level autoexec file

● use the GETLOG function.

Specifying an Additional Configuration File

You can specify the CONFIG= system option inside a configuration file to point to an additional
configuration file. Because the options specified in this additional file are processed at the point
of the CONFIG= specification, their precedence will be lower than the next option listed in the
original configuration file.

Functionalities That Are Unavailable from a Captive Account

Functionalities that require either a detached process or a subprocess are unavailable from a
captive account. These functionalities are:

● host-specific commands that are executed asynchronously from the SYSTASK

statement

● the PIPE device in the FILENAME statement

● remote sign-ons using SAS/CONNECT

● the SAS Help and Documentation in the SAS windowing environment

● the SAS Session Manager (xsassm)

● X commands that cannot be executed in the current process.

Changes to SAS E-mail

 ● The default mail handler is SMTP (Simple Mail Transfer Protocol), which supports
attachments.

● The BCC option in the FILENAME statement enables you to send blind copy e-mails
during a SAS session.

● Using the Send Mail dialog box, you can now do the following:

❍ include the contents of an active SAS text window (such as the Program Editor or
Log) in the body of your e-mail.

❍ attach the contents of a non-text window to your e-mail. Examples of non-text

windows include a graph generated by SAS/GRAPH and an image in your PROC
REPORT output.

Note: The VMS e-mail facility does not support attachments.

Accessing External Shareable Images

Shareable images are executable files that contain one or more routines written in various
programming languages. Shareable images store useful routines that might be needed by
many applications. Using the MODULE family of SAS CALL routines and functions, you can
invoke a routine that resides in an external shareable image from within SAS. You can access
the shareable images by using a DATA step, the IML procedure, and SCL code.

Engines

The following features are new or enhanced:

● The new V6 read-only engine enables you to read your Release 6.12 data sets. For
more information about the V6 read-only engine, see SAS Language Reference:
Concepts.

● The V5 and V6TAPE engines are no longer supported. Because of this, neither the V5
nor the V6TAPE options are valid in the LIBNAME statement or in the ENGINE= system
option.

SAS Resources
 ● The following resources are new:

❍ SAS.startSessionManager specifies whether SAS automatically starts the

session manager when a new SAS session is started.

❍ SAS.suppressTutorialDialog specifies whether SAS displays the Getting

Started Tutorial dialog box at the start of your SAS session.

❍ SAS.useNativeXmTextTranslations specifies whether any XmText widget

translations are inherited by all instances of the Text, Combo Box, and Spin Box
widgets used by the SAS X Motif user interface.

❍ SAS.VMSdisplay controls how often SAS yields processing to the X windowing

environment.

● The SAS.webBrowser resource is no longer supported. The SAS.helpBrowser now

specifies the pathname of the World Wide Web browser for use when viewing the online
help or when the WBROWSE command is issued.

SAS Language Elements

Commands

● The X command now breaks DCL commands that are longer than 256 characters into
smaller chunks before sending them to the operating environment for processing.

Functions

● To call a specific routine or module that resides in a shareable image, you can use the
MODULE function.

● You can store the contents of a memory address in a numeric variable on 32-bit and 64-
bit platforms by using the PEEKLONG function. This function replaces the PEEK
function, which was valid only on 32-bit platforms.

Procedures
 ● To see all the system options that have been set by your site administrator, use the
RESTRICT option in the OPTIONS procedure.

Statements

● The following options are new in the %INCLUDE statement:

❍ BLKSIZE= specifies the number of bytes that are physically read or written in an I/
O operation.

❍ ENCODING= specifies the encoding to use when reading from the specified
source.

❍ LRECL= specifies the record length (in bytes).

❍ RECFM= controls the record format.

● The V5 and V6TAPE options are not accepted by the LIBNAME statement.

System Options

● The following system options are new:

❍ You can specify the location of the Program Editor autosave file by using the
AUTOSAVELOC= system option.

❍ To specify that the asynchronous host command use a detached process, use the
DETACH system option. The default is DETACH.

❍ If you create a customized table of contents and index for the SAS Help and
Documentation, use the HELPTOC= and HELPINDEX= system options to specify
the file location.

❍ SSLCALISTLOC, SSLCRLLOC, SSLCERTLOC, SSLPVTKEYLOC, and

SSLPVTKEYPASS are authentication security options that are under the
OpenVMS Alpha operating environment. For details, see the SAS/CONNECT
User's Guide.

● The following system options have been changed or enhanced:

 ❍ SMTP (Simple Mail Transfer Protocol) is the new default for the EMAILSYS=
system option. SMTP supports sending attachments.

❍ V9 is a new value for the ENGINE= system option. V5 and V6TAPE are obsolete
and not accepted as valid values.

❍ The SAS$USER logical, the default for the SASUSER= system option, now
defaults to the SASUSER91 subdirectory of the SYS$LOGIN directory.

❍ MAX is the new default value for the SORTSIZE= system option.

❍ The value of stack-size for the STACK= system option must be an integer
between 65,535 and 5,242,880. The default value for most procedures is now
1,048,576 bytes.

● The following system options are obsolete or are no longer supported:

❍ DBCS

❍ DBCSLANG

❍ DBCSTYPE

❍ PROCLEAVE

❍ SYSLEAVE

❍ UNLOAD.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS 9.0, 9.1, and 9.1.3 Companion for z/
OS
Overview

New features in SAS 9.0 (and later) under z/OS include support for the following items:

● long format names

● remote help

● record-level sharing (RLS) for VSAM data sets and extended-format VSAM data sets.

Note:

● This section describes the features of SAS software under z/OS that are new or
enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS 9.1 (and later) for z/OS is
supported on both OS/390 and z/OS operating systems and, throughout this document,
any reference to z/OS also applies to OS/390, unless otherwise stated.

● For important information about new developments for SAS 9.1 (and later) for z/OS, see
support.sas.com.

Details

Long Format Names

Beginning with version 9.0, SAS supports long format names up to a maximum length of 32
bytes. Because earlier versions of SAS support format names that are only a maximum length
of 8 bytes, you will not be able to use earlier versions of SAS to read SAS 9.0 (and later) data
sets that contain long format names.
Remote Help

The remote help system enables users who access SAS by using a z/OS emulator (or a real
3270) to view SAS documentation with a Web browser on a PC that is running Microsoft
Windows. Previously, all documentation was displayed by the itemstore help in the SAS Help
window in the z/OS emulator. By displaying this documentation in your Windows Web browser,
the browsing capability is improved and the documentation content is more complete.

SAS Language Elements

● The following SAS statements have been enhanced:

❍ The NRLS option in the INFILE statement instructs SAS not to attempt to open a
VSAM data set in record-level sharing (RLS) mode, even if the data set is defined
as RLS eligible.

❍ The libref argument in the LIBNAME statement now supports library names that
contain underscores (_).

● The following SAS system options are new:

❍ The DLEXCPCOUNT option reports EXCPs (Execute Channel Program calls) to

direct access bound libraries.

❍ The DLMSGLEVEL option specifies which level of messages to generate for SAS
data libraries.

❍ The FILESPACE option at initialization specifies how the FILENAME and

LIBNAME statements should provide default values when allocating a new z/OS
data set.

● The new SAS function DSNCATLGD verifies the existence of a file in the z/OS system
catalog.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS/ACCESS 9.1 Interface to ADABAS

Overview

Prior to SAS 9.1, the ADABAS engine could not process a WHERE clause and ISN option.
The ADABAS engine read all of the records in the ADABAS table and returned the records to
SAS, then applied the WHERE clause.

Now, the ADABAS engine issues an L1 command to the ADABAS, table that enables
ADABAS to process the WHERE clause and ISN option. With this method, only one ADABAS
record is read instead of the complete table, which results in a performance enhancement.

Note:

● This section describes the only feature of the SAS/ACCESS Interface to ADABAS that
has changed since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/ACCESS 9.1 for ADABAS
is supported on both OS/390 and z/OS operating systems and, throughout this
document, any reference to z/OS also applies to OS/390, unless otherwise stated.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS/ACCESS 9.0 and 9.1 Interface to

CA-Datacom/DB
Overview

For recovery processing, the SAS/ACCESS interface to CA-Datacom/DB contains two new
data set options, and the interface view engine has been enhanced to support three new data
types.

Note:

● This section describes the features of the SAS/ACCESS interface to CA-Datacom/DB

that are new or enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/ACCESS 9.1 for CA-
Datacom/DB is supported on both OS/390 and z/OS operating systems and, throughout
this document, any reference to z/OS also applies to OS/390, unless otherwise stated.

Details

● The following data set options are new:

❍ The DDBCOMIT= data set option specifies the number of rows that are to be
processed before a database COMMIT statement is issued.

❍ The DDBERLMT= data set option specifies the number of errors that are allowed
before SAS stops processing and issues a rollback.

● The interface view engine now supports the CA-Datacom/DB data types: SQL-DATE,
SQL-TIME, and SQL-STMP.

● The special user-defined URT names USttlnnn and UWtttnnn, which were used for
loading the User Requirements Table, are obsolete.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS/ACCESS 9.0 and 9.1 Interface to

IMS
Overview

The SAS/ACCESS Interface to IMS now supports the ENCODING= data set option, which
enables you to override the encoding for processing a specific input or output file.

Note:

● This section describes the only feature of the SAS/ACCESS Interface to IMS that
changed since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/ACCESS 9.1 for IMS is
supported on both OS/390 and z/OS operating systems and, throughout this document,
any reference to z/OS also applies to OS/390, unless otherwise stated.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/ACCESS 9.0 and 9.1 for PC Files

Overview

The differences between the PC and UNIX features for SAS/ACCESS for PC files have been
significantly decreased. The documentation has also been enhanced with new sections added
for these two operating environments.

Note:

● This section describes the features of SAS/ACCESS for PC files that are new or
enhanced since SAS 8.2.

Windows Details

● The LIBNAME statement for PC files, new for SAS 9.0, provides direct, transparent
access to Microsoft Access (97, 2000, and 2002) and Microsoft Excel (5, 95, 97, 2000,
and 2002).

● PROC IMPORT and PROC EXPORT, using the SAS/ACCESS engine for PC files,
provide direct access to JMP data files.

● PROC SQL, using capabilities of the new PC files engine, enables you to communicate
with Microsoft Access and Microsoft Excel.

● Enhancements to the Import/Export wizard and procedures enable you to interact with
JMP data files and to access multiple Microsoft Excel worksheets.

UNIX Details

● The SAS/ACCESS interface to PC Files on UNIX communicates with the PC files

server. The server enables you to process requests for PC data.

● A new engine, called pcfiles, is available in SAS 9.1. This engine enables you to access
data stored on network accessible PCs. This engine, working with new UNIX features,
also enables you to directly access Microsoft Access (97, 2000, and 2002), Microsoft
 Excel (5, 95, 97, 2000, and 2002), and data from ODBC data sources on the PC (for
example, the Microsoft SQL Server).

● Enhancements to PROC IMPORT and PROC EXPORT enable you to access local JMP
data files and remote JMP data files that are stored on the PC via the client/server
model, in addition to Microsoft Access, Microsoft Excel, and ODBC data sources.

● The Pass-Through Facility for PC files uses the pcfiles engine to communicate directly
with Microsoft Access, Microsoft Excel, and ODBC data sources.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/ACCESS 9.0, 9.1, 9.1.2, and 9.1.3

Interfaces to Relational Databases
Overview

● Beginning with SAS 9.0, threaded reads enable you to complete jobs in substantially
less time than if each task is handled sequentially.

● The new CV2VIEW procedure converts SAS/ACCESS view descriptors into SQL views.

● Beginning with SAS 9.1.2, a SAS/ACCESS interface is added for MySQL databases.

● Beginning with SAS 9.1.3, several more hosts are supported for existing DBMSs.

Note: This section describes the features of SAS/ACCESS that are new or enhanced since
SAS 8.2.

All Supported SAS/ACCESS Interfaces to Relational Databases

● Threaded reads divide resource-intensive tasks into multiple independent units of work
and execute those units in parallel.

● Temporary table support enables DBMS temporary tables to persist from one SAS step
to the next. This support involves establishing a SAS connection to the DBMS that
persists across SAS procedures and DATA steps.

● The new SQL options MULTI_DATASRC_OPT= and DBMASTER= optimize the

performance of the SQL procedure. More detailed information is available about passing
joins to the DBMS, determining when joins will fail, and optimizing WHERE clauses.

● The SASTRACE= system option now provides improved debugging capabilities.

● The CV2VIEW procedure converts SAS/ACCESS view and access descriptors to the
SAS 9.0 format. It can also convert a view descriptor to a SAS 9.0 SQL view. As SAS/
ACCESS moves forward with LIBNAME enhancements and tighter integration with the
SAS Open Metadata Repository, SAS/ACCESS views will no longer be the method of
choice.
● DBMS metadata can now be accurately maintained within the SAS Open Metadata
Repository.

● The MULTI_DATASRC_OPT= option in the LIBNAME statement can be used in place

of the DBKEY= option to improve performance when you are processing a join between
two data sources.

● The DBMASTER= data set option designates which table is the master table when you
are processing a join that involves tables from two different types of databases.

● The DIRECT_EXE= option in the LIBNAME statement enables you to pass an SQL
statement directly to a database by using explicit pass-through when you are using
PROC SQL with a libref.

● You now have the ability to encode the DBMS password that appears in SAS source
code so that it does not appear as text in SAS programs.

● The CHANGE statement can be used to re-name SAS/ACCESS tables.

● Linux for Itanium-based Systems is available for DB2, Informix, Microsoft SQL Server,
MySQL, ODBC, Oracle, and Sybase, beginning with SAS 9.1.3 Service Pack 1.

● Linux for Intel Architecture is now available for MySQL, beginning with SAS 9.1.3
Service Pack 1, and for Teradata, beginning with SAS 9.1.3.

● AIX (RS/6000) is available for MySQL, beginning with SAS 9.1.3 Service Pack 2.

● HP-UX for the Itanium Processor Family Architecture is available for Sybase, beginning
with SAS 9.1.3 Service Pack 2.

● 64-bit Windows is now available for Oracle and DB2 in addition to 64-bit UNIX, which
was provided in SAS 8.2.

● Beginning with SAS 9.0, support is discontinued for the following:

SAS/ACCESS Interface to CA-OpenIngres

SAS/ACCESS Interface to Oracle Rdb under OpenVMS Alpha

 OS/2, OpenVMS VAX, MIPS ABI, Intel ABI, UNIX MP-RAS, and CMS operating
environments

CV2ODBC procedure.

SAS/ACCESS Interface to DB2 under z/OS

Note: z/OS is the successor to the OS/390 operating system. SAS/ACCESS 9.1 (and later)
for z/OS is supported on both OS/390 and z/OS operating systems and, throughout this
document, any reference to z/OS also applies to OS/390, unless otherwise stated.

The SAS/ACCESS Interface to DB2 under z/OS features stored procedure support that
includes passing input parameters, retrieving output parameters into SAS macro variables, and
retrieving result sets into SAS tables.

The following options are new:

● The BL_DB2CURSOR= data set option specifies a string that contains a valid DB2
SELECT statement that points to either local or remote objects (tables or views). After
your database administrator populates the communication database with the appropriate
entries, you can select data from a remote location to load DB2 tables directly from other
DB2 and non-DB2 objects.

● The BL_DB2LDCT3= data set option specifies a string in the LOAD utility control
statement, following the field specification.

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The DEGREE= option in the LIBNAME statement determines whether DB2 uses
parallelism.

● The TRAP151= data set option enables columns that cannot be updated to be removed
from a FOR UPDATE OF clause so that updating of columns can continue.
SAS/ACCESS Interface to DB2 under UNIX and PC Hosts

The following options are new:

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The SQL_FUNCTIONS= option in the LIBNAME statement specifies that the SQL
functions that match the functions that are supported by SAS are passed to the DBMS
for processing.

● The IGNORE_READ_ONLY_COLUMNS= data set option and option in the LIBNAME

statement specifies whether to ignore or include columns whose data types are read-
only when generating an SQL statement for inserts or updates.

SAS/ACCESS Interface to Informix

The following options are new:

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

SAS/ACCESS Interface to Microsoft SQL Server

The following options are new:

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The ERRLIMIT= option in the LIBNAME statement specifies the number of errors that
 are allowed while using the Fastload utility before SAS stops loading data to Teradata.

● The IGNORE_READ_ONLY_COLUMNS= data set option and option in the LIBNAME

statement specifies whether to ignore or include columns whose data types are read-
only when generating an SQL statement for inserts or updates.

SAS/ACCESS Interface to MySQL

Beginning in SAS 9.1.2, a SAS/ACCESS Interface to MySQL is available. MySQL software is

an open-source SQL database server that runs on 32-bit Windows systems, 64-bit HP
systems, and 64-bit Solaris systems. The SAS/ACCESS Interface to MySQL provides direct
transparent access to MySQL databases through LIBNAME statements or the Pass-Through
Facility. Various LIBNAME and data set options are supported by the LIBNAME engine, which
enables you to control the data that is returned to SAS.

SAS/ACCESS Interface to ODBC

The following feature and options are new:

● ODBC 3.x standard API is supported.

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The SQL_FUNCTIONS= option in the LIBNAME statement specifies that the SQL
functions that match the functions that are supported by SAS are passed to the DBMS.

● The IGNORE_READ_ONLY_COLUMNS= data set option and option in the LIBNAME

statement specifies whether to ignore or include columns whose data types are read-
only when generating an SQL statement for inserts or updates.

SAS/ACCESS Interface to OLE DB

The following options are new:

 ● The INSERTBUFF= option in the LIBNAME statement specifies the number of rows in a
single insert operation.

● The SQL_FUNCTIONS= option in the LIBNAME statement specifies that the SQL
functions that match the functions that are supported by SAS are passed to the DBMS.

● The IGNORE_READ_ONLY_COLUMNS= data set option and option in the LIBNAME

statement specifies whether to ignore or include columns whose data types are read-
only when generating an SQL statement for inserts or updates.

SAS/ACCESS Interface to Oracle

The following options are new:

● The BL_PARFILE= data set option creates a file that contains the SQL*Loader
command line options.

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The OR_UPD_PARTITION= data set option enables you to read, update, and delete
data from a specific partition in a partitioned table. It also enables you to insert and bulk-
load data into a specific partition in a partitioned table. It also boosts performance.

● OR_UPD_NOWHERE= is now a data set option, in addition to being an option in the

LIBNAME statement.

● The BL_INDEX_OPTIONS= data set option enables you to specify SQL*Loader Index
options with bulk-loading. You can boost performance by specifying the SORTED
INDEXES index option.

● The BL_RECOVERABLE= data set option enables you to specify whether the load
process is recoverable. It enhances the performance of the bulk load.

● The BL_SUPPRESS_NULLIF= data set option enables you to specify whether the load
process is recoverable. It enhances the performance of the bulk load.
SAS/ACCESS Interface to Sybase

The following options are new:

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

SAS/ACCESS Interface to Teradata

The following features and options are new:

● Beginning with SAS 9.1, specifying OBS=n causes the SAS/ACCESS Interface to
Teradata to append SAMPLE n to the SQL that Teradata generates.

● The interface to Teradata's FastExport utility enables faster data extraction.

● The DBSLICE= data set option specifies user-supplied WHERE clauses to partition a
DBMS query into component queries for threaded reads.

● The DBSLICEPARM= data set option and option in the LIBNAME statement controls the
scope of DBMS threaded reads and the number of threads.

● The ERRLIMIT= option in the LIBNAME statement specifies the number of errors that
are allowed while using the Fastload utility before SAS stops loading data to Teradata.

● The LOGDB= option in the LIBNAME statement specifies the name of an alternate
database in which restart log tables from Teradata's FastExport utility are to be created.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS/ACCESS Interface to R/3

Overview

The new features and enhancements for the SAS/ACCESS Interface to R/3 include the
following:

● two new RFC server options that offer enhanced performance and batch compatibility

● Unicode support for RFC servers

● a simplified process for creating an RFC server destination for a small SAP configuration

● a simplified logon process that does not require CPI-C parameters to be used

● SAP transport files that simplify the installation of the required ABAP function modules
and programs

● an updated RFC server that supports two operation modes for extracting data from your
SAP R/3 system

● a new SAP LIBNAME engine that enables you to access tables and views from SAP R/3
and SAP BW systems through a connection to the SAS RFC server

● the ability to use the %CALLRFC macro to call RFC-enabled ABAP functions

Note: The changes discussed here are from SAS/ACCESS 9.1 Interface to SAP 9.1 and
later.

For information about new features in the SAS Data Surveyor for SAP, see the What's New
section in SAS OnlineDoc.

Details

● The SAS/ACCESS Interface to R/3 is now called SAS/ACCESS 4.1 Interface to R/3. It
adds new features to the version of the SAS/ACCESS Interface to R/3 that shipped with
SAS 9.1.
● SAS/ACCESS 4.1 Interface to R/3 has two new server options:

The -B option enables you to increase performance by increasing the minimum

buffer size for data transfers.

The -b option enables batch compatibility so that you can process V8 ACCR3
requests using a V9 RFC server.

● SAS/ACCESS 4.1 Interface to R/3 can support Unicode and non-Unicode SAP R/3
servers. The Unicode RFC server can be started from Windows only, but it can support
Unicode SAP R/3 and SAS on all platforms.

● Beginning with 4.1, when creating an RFC server destination for small SAP
configuration, you can omit gateway information.

● SAP transport files that you can use to install the ABAP function modules and programs
are now included in the SAS/ACCESS Interface to R/3. It is recommended that you
import the SAP transport files rather than installing the ABAP function modules and
programs manually. For more information about using SAP transport files and installing
ABAP function modules and programs, see the Installation Instructions for SAS/
ACCESS Interface to R/3.

The new RFC server and RFC dialog server no longer use the following ABAP function
modules and programs which were previously used:

❍ Z_SAS_BATCH_INTERFACE_4

❍ Z_SAS_READ_TABLE_CPIC

❍ ZSASRDTB

❍ ZSASRDBT

Note: The transport files for the SAS/ACCESS Interface to R/3 require different ABAP
function modules and programs than the transport files for the SAS/ACCESS Interface
to SAP BW. Ensure that you use the correct files when you install your application.

● In previous versions of the SAS/ACCESS Interface to R/3, the logon utility required that
CPI-C parameters be entered when logging on to your R/3 system. Now, the CPI-C
parameters are no longer used when you log on to your R/3 system. The logon utility
enables you to access the following windows in which you will need to enter your logon
 parameters:

❍ Logon to R/3 window

❍ Advanced Parameters window

● The SAS RFC server has been updated. The RFC server command line syntax has
been modified for UNIX and Windows NT.

● The new SAP LIBNAME engine is a read-only engine that enables you to access tables
and views from SAP R/3 and SAP BW systems. The SAP LIBNAME engine accesses
an SAP system through a connection to the SAS RFC server and is part of the SAS
solution to access data in an SAP system.

The SAP LIBNAME engine supports new features such as load balancing, user
validation at logon, more efficient handling of projections, and server-side joins.
Directory processing is also supported.

Note: Unlike other LIBNAME engines in SAS, these interfaces are read-only and do
not support any forms of data set creation, deletion, or modification.

● The new CALLRFC procedure, which is used internally by the %CALLRFC macro,
enables you to call RFC enabled ABAP functions. The CALLRFC procedure uses the
RFC server to communicate with the SAP system.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS/ACCESS 9.1 Interface to SAP BW

Overview

The new features and enhancements for the SAS/ACCESS 9.1 Interface to SAP BW include

● support for SAP BW, Release 3.0

● changed data capture (CDC) processing that enables you to identify and extract only the
data in your ODS tables and InfoCubes that has changed since your last extraction

● enhanced performance when using the Load Metadata wizard to extract your SAP BW
metadata

● a logon process that no longer requires CPI-C logon parameters to be used.

Details

● The SAS/ACCESS Interface to SAP BW now supports all SAP BW releases from SAP
BW, Release 2.0B, through SAP BW, Release 3.0. The SAS/ACCESS Interface to SAP
BW is now compatible with SAP BW systems that contain transactional operational data
store (ODS) tables and transactional InfoCubes that were introduced in SAP BW,
Release 3.0.

Note: The SAP BW transactional ODS tables and transactional InfoCubes do not
support changed data capture (CDC) processing.

● The SAS/ACCESS Interface to SAP BW now provides a new method of extracting data
from the ODS tables and InfoCubes in your SAP BW system. When extracting data from
ODS tables and InfoCubes, you can either use full update processing, which extracts all
of the data in the selected ODS table or InfoCube, or you can use changed data capture
(CDC) processing. CDC processing enables you to extract only the data that has
changed since your last extraction.

● The Load Metadata wizard has improved performance when extracting metadata. Now,
the SAS/ACCESS Interface to SAP BW uses an ABAP function that issues a single call
to your SAP BW system rather than issuing multiple calls. This reduces the amount of
time required to extract large amounts of metadata from the ODS objects and InfoCubes
 in your SAP BW system.

● In previous versions of the SAS/ACCESS Interface to SAP BW, the logon profiles
required that CPI-C parameters be used when logging on to your SAP BW system. Now,
the CPI-C parameters are no longer used when you log on to your SAP BW system. The
logon utility enables you to access the following windows in which you will need to enter
your logon parameters:

❍ Logon to SAP BW window

❍ Advanced Parameters window

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/ASSIST 9.0 and 9.1

Overview

The new Table Passwords window and several new features for current product elements
enhance the usability and functionality of SAS/ASSIST.

Note:

● This section describes the features of SAS/ASSIST that are new or enhanced since
SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/ASSIST 9.1 is supported
on both OS/390 and z/OS operating systems and, throughout the SAS/ASSIST
documentation, any reference to z/OS also applies to OS/390, unless otherwise stated.

Details

Table Passwords Window

The new Table Passwords window lists all password-protected tables that are in currently
declared SAS data libraries. In this window, you can

● enter the password for each table

● save passwords in an encrypted file that SAS/ASSIST can refer to in future sessions

● keep one or more password-protected tables from being used in the current session

● keep all password-protected tables from being used in future SAS/ASSIST sessions.

Data Sources Window

The Data Sources window now includes a Deselect Libraries button that you can use to
deselect all libraries.
Maps Task and Create Data for Mapping Task

The Maps task and the Create Data for Mapping task now allow you to specify two area
identifier columns. This enhancement enables you to take advantage of map data sets that
require two columns (for example, STATE and COUNTY) to uniquely identify each area.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/CONNECT 9.0 and 9.1

Overview

New and enhanced features for SAS/CONNECT improve ease of use and SAS performance:

● MP CONNECT technology encompasses parallel processing on SMP (Symmetric Multi-

Processor) hardware as well as on machines across a network via the asynchronous
RSUBMIT statement or command. MP CONNECT now supports pipeline parallelism.

● SAS/CONNECT libref inheritance eliminates the need to duplicate data for use in
multiple SAS sessions.

● The same command that is used to start a client session can also be used to start a
server session by assigning the value !sascmd to the SASCMD= option in the SIGNON
and RSUBMIT statements and to the SASCMD= global system option.

● To ensure information privacy, SAS/CONNECT now supports the network security

protocol Secure Sockets Layer (SSL), which encrypts client/server data transfers.

● The %SYSLPUT macro statement now enables you to create a macro variable in a
specific server session.

● A new SASESOCK engine in the LIBNAME statement is available for SAS/CONNECT

applications that implement MP CONNECT with piping.

● Encoded passwords are supported in the RSUBMIT statement, the SIGNON statement,
and in script files that contain passwords.

● The SIGNON statement supports these new options: SIGNONWAIT=, TBUFSIZE=,

SERVER=, and SERVERV=.

● Compute Services (RSUBMIT statement) supports the new options SIGNONWAIT= and
CPERSIST=.

● New SAS global system options are SIGNONWAIT= and SYSRPUTSYNC=.

● SAS/CONNECT server initialization errors are written to the SAS console log.
Note:

● This section describes the features of SAS/CONNECT that are new or enhanced since
SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/CONNECT 9.1 is

supported under both OS/390 and z/OS operating systems and, throughout this
document, any reference to z/OS also applies to OS/390, unless otherwise stated.

Details

Signon

● SAS/CONNECT libref inheritance eliminates the need to duplicate data for use in
multiple SAS sessions. Server sessions can inherit client-defined librefs, allowing
multiple sessions to read from and write to a single SAS library. Libref inheritance is
implemented in the SIGNON and RSUBMIT statements.

● The same command that is used to start a client session can also be used to start a
server session by assigning the value !sascmd to the SASCMD= option in the SIGNON
and RSUBMIT statements and the SASCMD global system option.

● The SIGNONWAIT= option in the SIGNON statement and in the RSUBMIT statement
specifies whether implicit signons within an RSUBMIT are executed synchronously or
asynchronously during a SAS session. Synchronous processing means that an
RSUBMIT to a server session must be completed before control is returned to the client
session.

SIGNONWAIT= is now also a global SAS system option.

● The SAS 9.1 behavior of the filename value that is specified in the LOG= (and
OUTPUT=) options in the SIGNON statement is different than in previous releases of
SAS. The most recent RSUBMIT to filename overwrites the previous contents of
filename. Now, instead of overwriting the file, RSUBMIT appends to the file.

● The TBUFSIZE= global system option is now also an option in the SIGNON statement.
TBUFSIZE= option in the SIGNON statement specifies the size of the buffer that is used
by the SAS application layer for transferring data between a client and a server across a
network.
 ● The SERVER= option in the SIGNON statement is used to specify a CONNECT server
definition that has been defined in a SAS Metadata Repository.

● The SERVERV= option in the SIGNON statement is used to view the values that are
configured in the CONNECT server definition.

● In order to recover from initialization failures, you need to view the content of the SAS
console log. The location of the log varies according to the operating environment that
the server session runs under.

Compute Services

● MP CONNECT technology encompasses parallel processing on SMP (Symmetric Multi-

Processor) hardware as well as on machines across a network via the asynchronous
RSUBMIT statement or command.

● MP CONNECT now supports pipeline parallelism, which allows multiple SAS DATA
steps or procedures to overlap execution by piping the output from one process as the
input into the next process in a pipeline. Piping improves performance and reduces the
demand for disk space.

● SAS/CONNECT libref inheritance eliminates the need to duplicate data for use in
multiple SAS sessions. Server sessions can inherit client-defined librefs, allowing
multiple sessions to read from and write to a single SAS library. Libref inheritance is
implemented in the RSUBMIT and SIGNON statements.

● The same command that is used to start a client session can also be used to start a
server session by assigning the value !sascmd to the SASCMD= option in the
RSUBMIT and SIGNON statements and the SASCMD global system option.

● The %SYSLPUT statement is used to create a macro variable in a server session. Now
you can identify the specific server session in which a macro should be created, which is
necessary because multiple server sessions can result from executing asynchronous
remote submits. The /REMOTE= option that is specified in the %SYSLPUT macro
statement directs the macro definition to a specific server session.

● The SIGNONWAIT= option in the RSUBMIT statement and in the SIGNON statement
specifies whether implicit signons within an RSUBMIT are executed synchronously or
asynchronously during a SAS session. Synchronous processing means that an
RSUBMIT to a server session must be completed before control is returned to the client
 session.

SIGNONWAIT= is now also a global SAS system option.

● The SAS 9.1 behavior of the filename value that is specified in the LOG= (and
OUTPUT=) options in the RSUBMIT statement is different than in previous releases of
SAS. The most recent RSUBMIT to filename overwrites the previous contents of
filename. Now, instead of overwriting the file, RSUBMIT appends to the file.

● The CPERSIST option in the RSUBMIT statement is now also a global system option.
CPERSIST specifies whether a connection between a client and a server persists
(continues) after the RSUBMIT has completed.

● The SYSRPUTSYNC option in the RSUBMIT statement is now also a global system
option. SYSRPUTSYNC sets %SYSRPUT macro variables in the client session when
the %SYSRPUT statements are executed rather than when a synchronization point is
encountered.

Remote Library Services

● An explicit port number may now be specified in the SERVER= option in the LIBNAME
statement if you use the TCP/IP access method and sign on to a spawner by using an
explicit port specification instead of using the default port.

● SAS®9 Remote Library Services does not permit a SAS®9 client or server to connect to
a SAS 6 client or server. Use PROC UPLOAD and PROC DOWNLOAD to connect
clients and servers that run SAS®9 and SAS 6. For details, see information about cross-
version issues in the SAS/SHARE User's Guide.

● The LIBNAME statement for the SASESOCK engine associates a libref with a TCP/IP
pipe (instead of a physical disk device) for processing input and output. The
SASESOCK engine is required for SAS/CONNECT applications that implement MP
CONNECT with piping.

Data Transfer Services

Improvements to the file-compression algorithm have significantly reduced the time required
for large data transfers using SAS/CONNECT.
Security

● Secure Sockets Layer (SSL) is a protocol that provides network security and privacy for
SAS/CONNECT client/server transfers. To use SSL, you must first install and configure
SSL. To apply SSL, you must set SAS system options.

SSL is supported only under the UNIX and Windows operating environments.

● Encoded passwords are supported in the RSUBMIT statement , the SIGNON

statement , and in script files that contain passwords.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in Communications Access Methods for SAS/

CONNECT 9.1 and SAS/SHARE 9.1
Overview

SAS now supports

● the TCP/IP communications access method for network connections between these
operating environments: OpenVMS Alpha, UNIX, Windows, and z/OS. Also, the XMS
communications access method can be used between address spaces under z/OS.

● the network security protocol Secure Sockets Layer (SSL), which encrypts connections
between client and server.

● a new shell script for starting SAS is provided for the z/OS spawner.

● new instructions for configuring TCP/IP that runs under the OS/390 and z/OS operating
environments.

● the new Windows spawner option -NAME.

● new options for the OpenVMS spawner, UNIX spawner, Windows spawner, and z/OS
spawner are -OMRCONFIGFILE and -SASSPAWNERCN. The -
INSTALLDEPENDENCIES option is valid only in the Windows spawner.

Note:

● This section describes the features of the SAS communications access methods that
are new or enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. Throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

Details
Access Methods and Operating Environments

● SAS now supports the TCP/IP and XMS communications access methods.

● SAS now supports the OpenVMS Alpha, UNIX, Windows, and z/OS operating
environments.

● SAS no longer supports the APPC, DECnet, EHLLAPI, and NETBIOS communications
access methods or the CMS, OpenVMS VAX, OS/2, Windows 95, and Windows 98
operating environments.

SSL Protocol

SAS/CONNECT and SAS/SHARE support the Secure Sockets Layer (SSL) protocol, which
provides network security and protects the privacy of information by encrypting client/server
transfers under the UNIX and Windows operating environments.

OS/390 and z/OS Operating Environments

● A new Shell Script for Starting SAS is provided for the z/OS spawner.

● New instructions are provided to configure TCP/IP that runs under the OS/390 and z/OS
operating environments.

Spawners

● The new -NAME option for the Windows spawner is used to assign a name to the
spawner that is installed and started as a service. A specified name overrides the default
name that is automatically assigned when the -INSTALL option is used.

● New options for the OpenVMS spawner, UNIX spawner, Windows spawner, and z/OS
spawner are -OMRCONFIGFILE and -SASSPAWNERCN. The new -
INSTALLDEPENDENCIES option is valid only in the Windows spawner.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New for the SAS 9.0 and 9.1 Data Providers

Overview

New or enhanced features in the SAS Data Providers include the following:

● a new SAS OLAP Data Provider

● a new data source syntax for easier integration
● enhanced support for ADO
● improved error reporting
● support for larger tables and longer format and informat names.

Note: This section describes the features of the SAS Data Providers that are new or enhanced
since SAS 8.2.

Details

Version 6 of the SAS/SHARE Server is No Longer Supported

Version 6 of the SAS/SHARE Server is no longer supported by the SAS/SHARE Data

Provider. You can still connect to Version 7 or later SAS/SHARE servers.

SAS OLAP Data Provider

The new SAS OLAP Data Provider supports access to multidimensional data on a SAS OLAP
Server through the OLE DB for OLAP interfaces.

Data Source Syntax for Easier Integration

In addition to setting each property individually, the SAS IOM and SAS OLAP Data Providers
now enable you to specify all the necessary properties in the Data Source.

File Support across Operating Environments

The SAS Local Data Provider supports SAS data sets that were created under operating
environments other than Windows. Data sets created for operating environments such as
Solaris and HP-UX can be read directly by the SAS Local Data Provider.

In-Memory Data Set Caching

The SAS IOM Data Provider now supports in-memory data caching by means of the new
rowset property DBPROP_SAS_PAGESIZE, which controls how many rows the IOM server
retrieves each time it processes a request. Retrieved rows are held in memory and are
returned to the OLE DB consumer as needed. In-memory caching can significantly improve
performance.

ADO recordsets also have a caching facility for improving performance. You can set the
"CacheSize" property on the Recordset object to the number of rows that you want to retrieve
on each request. To ensure the best performance, you set the "Maximum Open
Rows" (DBPROP_MAXOPENROWS) property to a value that is at least twice the value of the
"CacheSize" property.

Optimized accessors are supported as described by the OLE DB specification, and they can
be used for application-specific performance tuning.

Positioning

For the SAS IOM Data Provider, positioning improvements are available only when caching is
enabled. If you have legacy applications that are dependent on the positioning model used in
SAS Data Provider releases prior to SAS 9.0, you can disable caching and return to the
previous model.

Larger Tables and Longer Names for Formats and Informats

The SAS Data Providers now support all rows and columns that are supported in SAS. For
OLE DB consumers, two interfaces have been added to SASExtensions.h:

● ISASDataSetInfo90
● SASDATASETINFO90

(ADO consumers do not have access to these interfaces.)

Because longer names for formats and informats are supported, all SAS Data Providers can
use SAS formats when reading data. The SAS IOM Data Provider can write data using SAS
informats and apply user-written formats and informats.
Version-Dependent and Version-Independent ProgIDs

All SAS Data Providers support both version-dependent and version-independent ProgIDs.
This enables you to install different versions of the SAS Data Providers on the same operating
environment and to write applications that use specific versions of the SAS Data Providers.

Error Reporting

If you encounter a problem while using the SAS Data Providers, improved error messages give
you more detailed information to help you diagnose and resolve problems more quickly.

Length-Setting Column Attributes and Additional ADO Column Types

The fixed-length column attribute is now set correctly by the SAS Data Providers. This attribute
affects the type of column that ADO reports. Also, the range of column types has been
expanded to include adVarChar and adVarWChar when the fixed-length column attribute is not
set.

Full Path Table IDs

When you open a recordset using ADO or open a rowset using OLE DB, the SAS Local Data
Provider supports the use of a full path, such as c:\sasuser\data.sas7bdat, as the table
ID. To use this form of table ID, you must set the value of the "Data Source" property on the
ADO Connection object and the OLE DB DBPROP_INIT_DATASOURCE property to
"_LOCAL_" (the default).

Local Update Access by the SAS/SHARE Data Provider

Single-user update access to a local installation of SAS is now provided by the SAS/SHARE
Data Provider and users can perform SQL processing on local data sets. The SAS Local Data
Provider no longer supports update access.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Data Quality Server 9.0, 9.1, and 9.1.2
Overview

New capabilities, functions, and options in SAS Data Quality Server (formerly called SAS Data
Quality - Cleanse) improve your ability to:

● analyze the quality of your data

● minimize defective data

● reduce redundancies

● transform and standardize data

● merge and recombine data.

Note: z/OS is the successor to the OS/390 operating system. SAS Data Quality Server 9.1 is
supported on both OS/390 and z/OS operating systems. Throughout this document, any
reference to z/OS also applies to OS/390.

General Enhancements

● SAS Data Quality Server is now available under the z/OS (formerly OS/390) operating
environment.

● The software is now closely integrated with:

❍ SAS ETL Studio for data cleansing as part of enterprise-wide extract, transform,
and load.

❍ dfPower Studio and Blue Fusion from DataFlux (a SAS company) for locale
editing and additional data cleansing functionality.

● The SAS Sample Library now contains samples for SAS Data Quality Server 9.1.
Locales

The following locales are provided:

● DEDEU, German language, for use with data from Germany

● ENAUS, English for Australia

● ENGBR, English for Great Britain

● ENUSA, English for the United States

● ENZSA, English for South Africa (new in SAS 9.1.2)

● FRFRA, French for France (new in SAS 9.1.2)

● ITITA, Italian for Italy

● NLNLD, Dutch for The Netherlands.

Functions

The following new functions interpret input character values that have been parsed (and
therefore contain delimiters):

● DQMATCHPARSED returns a match code from a parsed character value.

● DQGENDERPARSED returns a gender determination from the parsed name of an

individual.

The next set of new functions helps you prepare parsed character values:

● DQPARSETOKENPUT creates a new parsed value or adds a parsed value to an

existing parsed value.

● DQMATCHINFOGET returns the name of the parse definition that is associated with a
specified match definition.

● DQGENDERINFOGET returns the name of the parse definition that is associated with a
specified gender definition.
The new function DQLOCALEINFOGET returns a list of the locales that are currently loaded
into memory.

The new function DQPATTERN returns a pattern analysis of the words or characters in an
input character value.

The existing function DQSCHEMEAPPLY and the existing CALL routine CALL
DQSCHEMEAPPLY now accept the following new arguments: scheme-lookup-method, match-
definition, sensitivity, and locale. These arguments implement the new scheme-apply
capabilities that are also available in the DQSCHEME procedure for the APPLY statement.

System Options

The following system options are new or have changed:

● DQLOCALE= specifies the locales that are to be loaded into memory.

● DQSETUPLOC= specifies the location of the setup file for SAS Data Quality Server.

AUTOCALL Macros

The following AUTOCALL macros are new or have changed:

● %DQPUTLOC displays in the SAS log all the definitions and tokens in a specified locale.

● %DQLOAD loads specified locales. The new DQINFO parameter generates additional
information in the SAS log for debugging purposes.

● %DQUNLOAD unloads all locales.

DQSCHEME Procedure

In the PROC DQSCHEME statement, the BFD and NOBFD options enable you to generate
schemes in SAS format and in BFD format. BFD format schemes can be displayed and edited
using dfPower Customize from DataFlux (a SAS company).

The new CONVERT statement enables you to convert existing schemes between SAS and
BFD formats.

For the CREATE statement in the DQSCHEME procedure, the following options are new or
have been changed:

● INCLUDE_ALL enables you to fully populate the scheme. The scheme includes all
output values, including those that are not transformed.

● MODE= is stored in the scheme to specify that the scheme will, by default, be applied to
the entirety of each value of the input variable (when MODE=PHRASE), or to each
element in each value (when MODE=ELEMENT). The value of MODE= that is stored in
the scheme can be overridden by the value of the MODE= option in the APPLY
statement, or in the mode argument in the DQSCHEMEAPPLY function or CALL routine.

● SENSITIVITY= enables you to specify the degree of complexity in the match codes that
are generated internally when the scheme is built. Higher sensitivity values generate
match codes that are more complex. Complex match codes are useful when you want a
higher degree of similarity between the DATA values that map to a given STANDARD
value.

● MATCHDEF=, which was previously known as MATCHTYPE=, specifies the match

definition that is referenced during the creation of match codes.

● LOCALE= specifies a locale.

For the APPLY statement in the DQSCHEME procedure, MODE= specifies whether to apply
the scheme to the entire input value or to each element of the input value. The default value is
determined by the value of MODE= that was stored in the scheme when the scheme was
created.

DQMATCH Procedure

For the PROC DQMATCH statement, the options DELIMITER and NODELIMITER enable you
to generate concatenated match codes with or without a delimiter.

For the CRITERIA statement in the DQMATCH procedure, the following options are new or
have been changed:

● SENSITIVITY= now has a maximum value of 95, which equates with the maximum
sensitivity in dfPower Studio.
 ● MATCHCODE= enables you to generate more than one match code in a single pass
through the data.

● DELIMSTR= enables you to generate match codes for parsed input character variables.

● MATCHDEF=, which was previously known as MATCHTYPE=, specifies the match

definition that will be referenced during the creation of match codes.

● LOCALE= specifies a locale.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Data Surveyor 4.1 for SAP

Overview

SAS Data Surveyor 4.1 for SAP makes it much easier to perform the following tasks:

● search pre-extracted SAP BW metadata

● subset the extraction of SAP BW ODS objects and InfoCubes through WHERE
statements
● apply a WHERE statement to selected components of the InfoCube
● extract SAP ODS objects as SAS Views
● load external file data to SAP BW systems

For information about changes to the SAS/ACCESS Interface to R/3, see the What's New
section of the SAS/ACCESS Interface to R/3 User's Guide.

Note: SAS Data Surveyor for SAP is now called SAS Data Surveyor 4.1 for SAP. It adds new
features to the version of SAS Data Surveyor for SAP that originally shipped with SAS 9.1.

Details

Search Capabilities for SAP BW Metadata

A metadata search window in the SAP BW Source Designer wizard enables you to quickly find
SAP BW metadata that contains a specified search string. You can revise and refine your
metadata search criteria by searching within the returned search results. Select an InfoCube or
an ODS object to view the associated metadata. You can also view the actual data for an ODS
object. From the search window, you can select the ODS Object or InfoCube that you want to
identify as a data source in your SAS ETL Studio data warehouse.

Subsetting Capabilities

● In a create star schema view transformation, you can add a WHERE statement to apply
subset criteria within a Load InfoCube job. The subset information can include a
WHERE statement.
 ● In a Load ODS object job transformation, you can add a WHERE statement to apply
subset criteria within a Load ODS object job. The subset information can include a
WHERE statement.

Applying WHERE Statements to Selected Components of a Load

InfoCube Job

When you propagate a WHERE statement to the components of the InfoCube using the
Propagate Tab in the create star schema view transformation, the extraction steps of the
propagation targets and of the Create Star Schema view transformation are optimized.

Extracting SAP ODS Objects As SAS Views

Extraction options in the Extraction Options window (for ODS objects) of the SAP BW Source
Designer wizard enable you to specify whether you want to create a SAS View from the ODS
object that you specified.

Loading External File Data to SAP BW

A Target Designer wizard enables you to load external file data to an SAP BW warehouse by
creating a flat file based on InfoPackage metadata stored in SAP BW. The wizard registers a
process to create a flat file in a format that can be loaded by an existing InfoPackage into SAP
BW. The wizard generates a process flow diagram into which you can drop a SAS data set as
input. By mapping the data to the flat file, you can run a job in SAS ETL Studio that ultimately
returns the file with the new data to SAP BW. The exact process that is used to transfer the
data to SAP BW depends on the InfoPackage settings and the location of the external data
files.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.
What's New

What's New in SAS Enterprise Guide 3.0

Overview

SAS Enterprise Guide 3.0 includes the following major enhancements:

● resizable task windows that have a new navigation pane

● an integrated environment for creating stored processes

● use of the Process Flow window as an integral part of the SAS Enterprise Guide
interface

● a simplified user interface for the OLAP Analyzer

● context help throughout SAS Enterprise Guide.

Details

Task Updates

● Task windows are resizable and include a new navigation pane that enables you to see
the available option panes simultaneously and to access any of them with a single click.
● The new Sort Data task enables you to sort a data set in your project by any of its
columns. You can sort the data by one or more columns, and you can select ascending
or descending order for each column. The sorted data set is added as a new data item
in your project.

● The Import Data task now supports additional file types, including all the popular PC
database formats.

● For each task, you can specify the starting row and limit the number of rows of data that
the task processes.

Stored Processes
You can create stored processes that address the metadata and the code simultaneously. A
stored process is a SAS program that is designed to be stored on a central server and
accessed by numerous clients. Stored processes consist of two distinct parts: the SAS code
and a stored process definition that resides on a metadata server. Stored processes can be
used for Web reporting, building Web applications, delivering result packages to clients or the
mid-tier, and publishing results to channels or repositories.

Process Flow Window

The Process Flow window (formerly named the Process Flow Builder) is now an integral part
of the SAS Enterprise Guide interface. This window has been enhanced so that the
dependencies among the data, tasks, and final output are easier to understand. You can use
this window to build entire projects. Process flows can also be the basis for creating stored
processes.

OLAP Analyzer

● The OLAP Analyzer (formerly named the MDDB Viewer) has been simplified by the
development of a new user interface and wizards for common tasks.
● You can view the detailed data that makes up any tuple (that is, a pairing of items from
two dimensions) in your OLAP cube.
● You can add calculated members, or formulas, to a dimension in an OLAP cube. The
calculated members can be computed from other members or values and must return
either strings or numeric values.

Application Interface

● The application interface has been completely re-designed to improve usability,

streamline interaction with SAS servers, exploit the new features in SAS®9, and help
end-users be more productive.
● The main SAS Enterprise Guide interface, as well as task and options windows,
includes a context help area to provide targeted help information about the currently
selected option.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Enterprise Miner 4.3

Overview

Two parallel versions of Enterprise Miner, either 4.3 or 5.1, are available in SAS 9.1.
Enterprise Miner 4.3 is a continuation of the SAS client/SAS server system. Enterprise Miner
5.1 uses the production SAS 9.1 server and is a Web-deployable client application, which was
developed using Java technology.

Enterprise Miner 4.3 includes the following new features and enhancements since Enterprise
Miner 4.2:

● The Link Analysis, Time Series, and Memory-Based Reasoning nodes are production.

● Interactive training in the Tree node is supported through the Enterprise Miner Tree
Desktop Application.

● Enterprise Miner Tree Desktop Application uses the new procedure ARBORETUM. A
new view, Local Tree, is available.

● The Interactive Grouping node supports variables that have the model role of Group.

● You can register a report in the Enterprise Miner Model Repository and view the report
using the Web application Enterprise Miner Model Viewer.

A comparison of Enterprise Miner 4.3 and 5.1 is summarized at the end of this document.

Details

Link Analysis Node

The Link Analysis node is now production and includes the following new features and
enhancements:

● Weighted and unweighted centrality measures are computed by default.

● Any node data variable with the name TEXT, TXT, or LABEL is assigned as the variable
 label.

● The default number of nodes that are read from the Nodes table is increased from 32 to
100.

● The Results Browser now includes a Graphs tab. The Graphs tab displays multiple
plots, such as link and node distribution histograms, plots of link Chi-square values, and
plots of node centrality measures.

● The Output includes a brief summary of the nodes and links data sets.

● In the Detailed Results window, you can use any column to sort the Nodes and Links
tables.

● The network display controls are now contained in the Display Control window, which
enables you to modify the nodes, links, link graph layout, and cluster options from a
centralized window.

● You can create a custom display of your links based on the link value. You can set the
color and width of a link based on a cutoff value that you specify in the Link Value
window.

● You can define your own clusters or modify existing clusters in the Interactive Clustering
window.

● The MDS Options window contains a Grouping Bias option that you can use to specify
how to space nodes within groups.

Tree Node

In Enterprise Miner 4.2 and earlier releases, interactive training is performed in the local SAS
session. Beginning with Enterprise Miner 4.3, interactive training is supported through the
Enterprise Miner Tree Desktop Application.

Enterprise Miner Tree Desktop Application

The Enterprise Miner Tree Desktop Application in SAS mode is production in Enterprise Miner
4.3. New features and enhancements include the following:
 ● The Enterprise Miner Tree Desktop Application now uses the new procedure,
ARBORETUM. Eventually, the ARBORETUM procedure will replace the SPLIT
procedure. In general, PROC ARBORETUM runs faster than PROC SPLIT on larger
data sets. Also, PROC ARBORETUM provides more informative messages and enables
you to

❍ prune specific nodes and explicitly define splitting rules

❍ output data sets that describe the nodes and splitting rules

❍ generate PMML (Predictive Model Markup Language) output

❍ have more control over the performance.

● The Local Tree view enables you to view a portion of the whole tree, depending on the
primary selected node and the depth that you define.

Interactive Grouping Node

The groupings of a variable in your input data might have been defined by other methods
outside of the Interactive Grouping node. If you set the model role to Group and the status to
Use, the Interactive Grouping node places each level of the variable in a group, and calculates
the weight of evidence and other statistics without applying the node settings.

Model Repository

The Enterprise Miner Model Repository has been enhanced to include the following:

● Setting the model registration options and saving models to the model repository now
occurs through the Reporter node. In addition, you can set the model repository that you
want to use by submitting macro variables in the Program Editor.

● You can save models directly to the model repository by using the SAS Metadata
Server. You do not have to define the Open Metadata Architecture Java server to
communicate with the model repository.

● You can search for, browse, and delete models from a model repository by using the
Enterprise Miner Model Viewer.
Advantages of Using Enterprise Miner 5.1

The following list summarizes the advantages of using Enterprise Miner 5.1 instead of
Enterprise Miner 4.3:

● Model evaluation and reporting tools provide more information.

● Graphics and data visualization tools are more tightly integrated into the product.

● Data processing and model training executes entirely on the server.

● Multiple process flow diagrams can be run concurrently.

● A single process flow diagram can execute in multiple streams on multi-CPU systems.

● Training processes can be stopped.

● The client can be run under any system, not just a SAS System.

● The server definitions and meta services are administered by the SAS Management
Console.

Comparison of Enterprise Miner 4.3 and 5.1

The following table is a listing of the primary differences between Enterprise Miner 4.3 and
Enterprise Miner 5.1.

Configuration Enterprise Miner 4.3 Enterprise Miner 5.1

Server SAS 9.1 MVA SAS 9.1 MVA

Middleware N/A Java

It manages multiple users

and model training can be
disconnected.

Client SAS 9.1 Windows Java 1.4.1

Metadata Server Optional, but needed for Required
model registration.

Project Storage Client and Server Server

SAS Environment Enterprise Miner 4.3 Enterprise Miner 5.1

Program Editor, Log, Output Yes Yes

windows

Viewer for SAS/GRAPH Yes Yes

output

SAS/INSIGHT Yes No

SAS DMS-based solutions Yes No

Enterprise Miner Interfaces Enterprise Miner 4.3 Enterprise Miner 5.1

SAS System GUI Yes No

Java client GUI No Yes

Batch project execution No Yes

Web application results Yes Yes

viewer

Java API No Yes (experimental)

SAS Code node interface Yes Yes. It provides better

support for macro variables,
macros, code generation,
and results definition.

SAS Code node based No Yes. XML definitions for

custom nodes node properties.

DMTOOL custom nodes Yes No

Enterprise Miner Procedures Unsupported Unsupported

Usage

Metadata Enterprise Miner 4.3 Enterprise Miner 5.1

Table and Column analytical Yes Yes
metadata

Batch interface for creating No Yes

table and column metadata

Batch interface for creating No Yes

target decision profiles

Sample-based metadata Yes No

calculation statistics

Complete data-based No Yes

metadata calculation
statistics

Configurable data advisory No Yes. You can set thresholds

rules for missing percentages.

Extensible column attributes No Yes. You can add additional

column attributes to be
included in reports.

Report column attribute No Yes. You can include

variables that have the
report attribute in most
reports such as score
rankings and score
distributions.

Hidden variables No Yes. You can hide rejected

variables from the variable
usage user interfaces but
retain them in the data for
score applications.

Data Model for entire project No Yes. It facilitates batch and

GUI execution of common
projects.

GUI Functionality Enterprise Miner 4.3 Enterprise Miner 5.1

XML diagram exchange No Yes

Diagram copy/paste No Yes
between projects

Open multiple diagrams No Yes

Open multiple results No Yes

windows

Open multiple child windows No Yes

in node results

Common property sheet No Yes

Individual property dialogs Yes No

Group processing Yes (stratified, bagging, and No

boosting)

Job Execution Enterprise Miner 4.3 Enterprise Miner 5.1

Stop running diagram No Yes

Run multiple diagrams No Yes

Disconnect while diagram No Yes. Middleware

running configuration is required.

Continue work while No Yes

diagrams running

Share projects with multiple Yes Yes

users

Batch mode execution No Yes

Scheduling No No

Multi-threaded procedures Yes Yes

Multi-tasking projects No Yes

Reporting Enterprise Miner 4.3 Enterprise Miner 5.1

HTML Reports Yes No

SAS Publish Packages No Yes
(SPK)

Web application for viewing Yes Yes

stored models

Interactive Analysis Enterprise Miner 4.3 Enterprise Miner 5.1

Tree growing and pruning Yes Yes

Neural network model Yes No

Association rule: WHERE Yes No

clause

Transformation bin allocation Yes No

Filter outliers selection Yes No

Link analysis Yes No

Interactive grouping Yes No

Decision threshold charts Yes No

Decision Processing Enterprise Miner 4.3 Enterprise Miner 5.1

Class target profile matrix Yes Yes

Class target loss matrix Yes Yes

Cost values and cost Yes Yes

variables

Class target variable Yes No

number of decisions

Interval target decisions Yes No

Model Assessment Enterprise Miner 4.3 Enterprise Miner 5.1

Class probability score Yes Yes

rankings: gain, lift, etc.
Class probability score No Yes
distributions

Classification tables in node Sometimes Always

output listings

Decision tables in node No Yes

output listings

Type I and Type II error No Yes

table in node output listings

Interval target score rankings No Yes

Interval target score No Yes

distributions

Interval target prediction vs. Yes. It is sample based and Yes. It is user-generated
actual target available in Model Manager. plots of exported data.

Score rankings printed in No Yes

output listings

Score distributions printed in No Yes

output listings

Post-model decision matrix Yes No

what-if investigations

Decision threshold charts Yes No

Komogorov-Smirnov (KS), No Yes

Receiver Operating
Characteristic (ROC) index,
GINI statistics

Validation data assessment Yes Yes

Train and Test data Optional. You must enable it Yes

assessment through Model Manager,

ROC chart Yes Yes

Scoring Enterprise Miner 4.3 Enterprise Miner 5.1

SAS score code Yes Yes

C and Java score code Yes Yes

Separation of residual and No Yes

non-residual score code

PMML generation No Yes

Nodes Enterprise Miner 4.3 Enterprise Miner 5.1

Input Data Yes Yes

Sampling Yes Yes

Partitioning Yes Yes

Time Series Yes Yes

Variable Selection Yes Yes

Clustering Yes. The procedure Yes. The procedure DMVQ

FASTCLUS is used. is used to support class
variables, score code, and
PMML.

SOM Yes No

Link Analysis Yes No

Insight Yes No. Graphs can be

generated from the Results
window of any node.

Distribution Explorer Yes No. Graphs can be

generated from the Results
window of any node.

Multiplot Yes Yes

StatExplore No Yes. This node computes
univariate and bivariate
distribution statistics for
interval and class variables.
Target and segment
variables are used as by
variables and/or correlation
terms.

Merge No Yes. This node merges

training, test, and validation
data sets by row number or
by ID variable. It is useful for
combining predictions from
multiple models or for
matching ID in multiple
tables.

Association Yes Yes, but the Results window

does not support filtering
rules and scatter plot for
items. This node supports
network display of rules. It
generates a transposed data
set that has one row per
customer and variables for
rules. The transposed data
set can be used to cluster or
predict customer behavior
by rules.

Path Analysis No Yes. This node uses the

new PATH procedure that
includes a referrer variable
for Web log analysis.

Transform Yes Yes, but this node does not

support user-specified
equations. It supports the
creation of dummy and
interactive terms.
Interactive Grouping Yes. This node supports No
user-driven grouping of
variable levels and bins
based on GINI, Information
Gain, and Weight of
Evidence (WOE)scores.

Drop No Yes. This node drops

variables from temporary
tables for processing
efficiency.

Filter Yes Yes, but this node does not

support graphical selection
of filter ranges.

Impute Yes, this node is the Yes

Replacement node.

Principle Components Yes. It is in the Princomp/ Yes. This node does not
Dmneural node. support the selection of
number of components in
the Results window.

Regression (linear and Yes Yes

logistic)

Dmine Regression No. Dmine regression is Yes. This node uses the
available as an optional DMINE procedure to
output from the Variable produce models that directly
Selection node. include the Analysis of
Variance (AOV), group, and
interaction effects for
interval and binary targets.

Decision Tree Yes. Use the Tree Desktop Yes. Use the Tree Desktop
Application for interactive Application for interactive
training. training.

Neural Network Yes Yes. This node does not

support interactive training
or advanced user network
configuration.
Rule Induction No Yes. This node uses an
algorithm for building
models by recursively
identifying target events. It is
useful for modeling rare
events. This functionality
was formerly included in
DMTOOL.

Autoneural No Yes. This node uses an

algorithm for automated
MLP network building. It
selects the type and number
of activation functions from
four different architectures.
This functionality was
formerly included in
DMTOOL.

Dmneural Yes. This node is part of the Yes.

Princomp/Dmneural node.

Two Stage Model Yes Yes. You can specify the

options for the first and
second stage models, and
the neural network models
that have two targets.

Memory-Based Reasoning Yes. This node is not No

recommended for score
deployment, because it
requires training table
availability.

Ensemble Yes Yes. The node supports

simple averaging and voting
methods. It does not support
bagging and boosting
models.
Model Comparison Yes. It is the Assessment Yes. This node computes
node. ROC and KS and
automatically selects a
model based on your
selection.

Group Processing Yes No

Subdiagram Yes No

Control Point Yes Yes

SAS Code Yes Yes. This node provides

extended support through
better organized macros and
macro variables. It supports
building model and model
assessment functions, and
the creation of report tables
and plots.

Score Yes Yes. If score data is defined,

the node always scores data
to create output view and
table.

Score Converter Yes No. C and Java code are

included in the SPK results
package. PMML code for
decision trees is available
on a request basis.

User Defined Model Yes No

Reporter Yes No. Reports in the SPK

format can be generated
from any node.

Data Set Attributes Yes Yes. The Metadata node in

Enterprise Miner 5.1
replaces the Data Set
Attributes node in Enterprise
Miner 4.3.
 Data Mining Database Yes N/A

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Enterprise Miner 5.1

Overview

SAS Enterprise Miner 5.1 represents a new paradigm for distributing the power of SAS data mining. A three-tiered architecture
separates the data mining computational server from the user interface workstations. The new architecture provides unprecedented
flexibility that allows users to configure efficient installations that scale from single-user systems to very large enterprise computing
solutions. Powerful servers can be dedicated to computing while end users move from office to home to remote site without losing
access to projects or services. Mining processes can be run in parallel and scheduled in a batch environment. Data miners can also
distribute Web reports over the corporate intranet to product managers.

Customers should select the configuration that is appropriate in their operating environment. Together, the SAS System CDs and the
SAS Ancillary CD contain all components that are needed to install any configuration.

SAS Enterprise Miner 5.1 in SAS 9.1.3 contains the following new nodes:

● Segment Profile Node

● Credit Scoring Nodes (experimental)

Segment Profile Node

The Segment Profile node helps assess data sets by using a splitting algorithm to create segmented data. Segmented data is data
that is grouped by segment variable, based on common attributes or values among the specified input variables. Use the Segment
Profile Node to identify the variables that you want to segment the data set by, and to identify the input variables that you want to use
to discriminate between a segment and the entire data set. In addition, the Segment Profile node computes summary statistics for
designated report variables.

Credit Scoring Nodes (Experimental)

SAS Credit Scoring is a new experimental solution in SAS Enterprise Miner 5.1 in SAS 9.1.3. This solution offers the ability to rapidly
generate automated credit scoring models that rely mostly on statistical models.

If your site has licensed SAS Credit Scoring, the credit scoring nodes will appear on the Credit Scoring tab in your Enterprise Miner
session. SAS Enterprise Miner includes the following credit scoring nodes:

● Interactive Grouping

● Scorecard

● Reject Inference

● Credit Exchange

You can use these nodes to build scorecard models that assign score points to customer attributes; to group and select
characteristics, automatically or interactively, by using Weights of Evidence and Information Value measures; and to normalize score
points to conform with company or industry standards. The business value of statistical models can be assessed by using strategy
curves, profit charts, and a reject inference process in order to arrive at models for scoring through-the-door populations. A credit
exchange tool provides additional reporting of the credit scoring results and can exchange information with the SAS Credit Risk
solution.
For more information, see the documentation for SAS Credit Scoring.

Conversion from Previous Releases

There is no current process for converting SAS Enterprise Miner Version 4.x or 3.x projects to SAS Enterprise Miner 5.1.

Data Import and Export

SAS Enterprise Miner 4.3 and SAS Enterprise Miner 5.1 work directly on SAS tables and views. Neither product directly integrates
further data preparation or processing except for customized code that you write in the SAS Code node. SAS Enterprise Miner 5.1
includes a Merge node that enables users to merge input data sets.

SAS Enterprise Miner 4.3 and SAS Enterprise Miner 5.1 can register models to a SAS Metadata Repository. The information
registered by using SAS Enterprise Miner 5.1 is more complete.

Documentation

The online documentation explains many of the details about installing, configuring, and using SAS Enterprise Miner 5.1. This
document adds overview information about SAS Enterprise Miner 5.1, and a comparison of its features to the features in SAS
Enterprise Miner 4.3.

SAS Enterprise Miner 4.3 vs. SAS Enterprise Miner 5.1

The following table shows the primary differences between SAS Enterprise Miner 4.3 and SAS Enterprise Miner 5.1.

Configuration SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Server SAS 9.1 MVA SAS 9.1 MVA

Middleware N/A Java. The middleware manages multiple

users and model training can be
disconnected.

Client SAS 9.1 Windows Java 1.4.1

Metadata Server Optional, but is needed for model Required

registration.

Project Storage Client and Server Server

SAS Environment SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Program Editor, Log, Output windows Yes Yes

Viewer for SAS/GRAPH output Yes Yes

SAS/INSIGHT Yes No

SAS DMS-based solutions Yes No

Enterprise Miner Interfaces SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1
SAS System GUI Yes No

Java client GUI No Yes

Batch project execution No Yes

Web application results viewer Yes Yes

Java API No Yes (experimental)

SAS Code node interface Yes Yes. It provides better support for macro
variables, macros, code generation, and
results definition.

SAS Code node-based custom nodes No Yes. XML definitions for node properties.

DMTOOL custom nodes Yes No

SAS Enterprise Miner Procedures Unsupported Unsupported

Usage

Metadata SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Table and Column analytical metadata Yes Yes

Batch interface for creating table and No Yes

column metadata

Batch interface for creating target No Yes

decision profiles

Sample-based metadata calculation Yes No

statistics

Complete data-based metadata No Yes

calculation statistics

Configurable data advisory rules No Yes. You can set thresholds for missing
percentages.

Extensible column attributes No Yes. You can add additional column

attributes to be included in reports.

Report column attribute No Yes. You can include variables that have the
report attribute in most reports such as
score rankings and score distributions.

Hidden variables No Yes. You can hide rejected variables from

the variable usage user interfaces but retain
them in the data for score applications.

Data Model for entire project No Yes. It facilitates batch and GUI execution of
common projects.

GUI Functionality SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

XML diagram exchange No Yes

Diagram copy/paste between projects No Yes

Open multiple diagrams No Yes

Open multiple results windows No Yes

Open multiple child windows in node No Yes
results

Common property sheet No Yes

Individual property dialogs Yes No

Group processing Yes (stratified, bagging, and boosting) No

Job Execution SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Stop running diagram No Yes

Run multiple diagrams No Yes

Disconnect while diagram runs No Yes. Middleware configuration is required.

Continue work while diagrams run No Yes

Share projects with multiple users Yes Yes

Batch mode execution No Yes

Scheduling No No

Multi-threaded procedures Yes Yes

Multi-tasking projects No Yes

Reporting SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

HTML Reports Yes No

SAS Publish Packages (SPK) No Yes

Web application for viewing stored Yes Yes

models

Interactive Analysis SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Tree growing and pruning Yes Yes

Neural network model Yes No

Association rule: WHERE clause Yes No

Transformation bin allocation Yes No

Filter outliers selection Yes No

Link analysis Yes No

Interactive grouping Yes Yes, if your site licenses SAS Credit

Scoring. The SAS Enterprise Miner
Interactive Grouping Desktop Application
enables you to modify the groupings
interactively.

Decision threshold charts Yes No

Decision Processing SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Class target profile matrix Yes Yes

Class target loss matrix Yes Yes

Cost values and cost variables Yes Yes

Class target variable number of Yes No

decisions

Interval target decisions Yes No

Model Assessment SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Class probability score rankings: gain, Yes Yes

lift, etc.

Class probability score distributions No Yes

Classification tables in node output Sometimes Always

listings

Decision tables in node output listings No Yes

Type I and Type II error table in node No Yes

output listings

Interval target score rankings No Yes

Interval target score distributions No Yes

Interval target prediction vs. actual Yes. It is sample based and available in Yes. It is user-generated plots of exported
target Model Manager. data.

Score rankings printed in output No Yes

listings

Score distributions printed in output No Yes

listings

Post-model decision matrix what-if Yes No

investigations

Decision threshold charts Yes No

Kolmogorov-Smirnov (KS), Receiver No Yes

Operating Characteristic (ROC) index,
GINI statistics

Validation data assessment Yes Yes

Train and Test data assessment Optional. You must enable it through Yes
Model Manager,

ROC chart Yes Yes

Scoring SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

SAS score code Yes Yes

C and Java score code Yes Yes

Separation of residual and non- No Yes

residual score code

PMML generation No Yes

Node Tools SAS Enterprise Miner 4.3 SAS Enterprise Miner 5.1

Input Data Yes Yes

Sampling Yes Yes

Partitioning Yes Yes

Time Series Yes Yes

Variable Selection Yes Yes

Clustering Yes. The procedure FASTCLUS is used. Yes. The procedure DMVQ is used to
support class variables, score code, and
PMML.

SOM Yes No

Link Analysis Yes No

Insight Yes No. Graphs can be generated from the

Results window of any node.

Distribution Explorer Yes No. Graphs can be generated from the

Results window of any node.

Multiplot Yes Yes

StatExplore No Yes. This node computes univariate and

bivariate distribution statistics for interval
and class variables. Target and segment
variables are used as by variables and/or
correlation terms.

Merge No Yes. This node merges training, test, and

validation data sets by row number or by ID
variable. It is useful for combining
predictions from multiple models or for
matching ID in multiple tables.

Association Yes Yes, but the Results window does not

support filtering rules and scatter plot for
items. This node supports network display of
rules. It generates a transposed data set
that has one row per customer and variables
for rules. The transposed data set can be
used to cluster or predict customer behavior
by rules.

Path Analysis No Yes. This node uses the new PATH

procedure that includes a referrer variable
for Web log analysis.

Transform Yes Yes, but this node does not support user-
specified equations. It supports the creation
of dummy and interactive terms.

Drop No Yes. This node drops variables from

temporary tables for processing efficiency.

Filter Yes Yes, but this node does not support

graphical selection of filter ranges.

Impute Yes, this node is the Replacement node. Yes

Principal Components Yes. It is in the Princomp/Dmneural node. Yes. This node does not support the
selection of number of components in the
Results window.
Regression (linear and logistic) Yes Yes

Dmine Regression No. Dmine regression is available as an Yes. This node uses the DMINE procedure
optional output from the Variable Selection to produce models that directly include the
node. Analysis of Variance (AOV), group, and
interaction effects for interval and binary
targets.

Decision Tree Yes. Use the Tree Desktop Application for Yes. Use the Tree Desktop Application for
interactive training. interactive training.

Neural Network Yes Yes. This node does not support interactive
training or advanced user network
configuration.

Rule Induction No Yes. This node uses an algorithm for

building models by recursively identifying
target events. It is useful for modeling rare
events. This functionality was formerly
included in DMTOOL.

Autoneural No Yes. This node uses an algorithm for

automated MLP network building. It selects
the type and number of activation functions
from four different architectures. This
functionality was formerly included in
DMTOOL.

DMNeural Yes. This node is part of the Princomp/ Yes.

DMNeural node.

Two Stage Model Yes Yes. You can specify the options for the first
and second stage models, and the neural
network models that have two targets.

Memory-Based Reasoning Yes. This node is not recommended for Yes.

score deployment, because it requires
training table availability.

Ensemble Yes Yes. The node supports simple averaging

and voting methods. It does not support
bagging and boosting models.

Model Comparison Yes. It is the Assessment node. Yes. This node computes ROC and KS and
automatically selects a model based on your
selection.

Segment Profile No Yes. This node uses a designated segment

variable to segment the data set based on
input variables that discriminate between a
segment and the entire data set.
Additionally, the node generates graphics
and summary information to profile the
generated segments.

Group Processing Yes No

Subdiagram Yes No

Control Point Yes Yes

 SAS Code Yes Yes. This node provides extended support
through better organized macros and macro
variables. It supports building model and
model assessment functions, and the
creation of report tables and plots.

Score Yes Yes. If score data is defined, the node

always scores data to create output view
and table.

Score Converter Yes No. C and Java code are included in the
SPK results package. PMML code for
decision trees is available on a request
basis.

User Defined Model Yes No

Reporter Yes No. Reports in the SPK format can be

generated from any node.

Data Set Attributes Yes Yes. The Metadata node in SAS Enterprise
Miner 5.1 replaces the Data Set Attributes
node in SAS Enterprise Miner 4.3.

Data Mining Database Yes N/A

Interactive Grouping Yes. This node supports user-driven Yes, if your site licenses SAS Credit
grouping of variable levels and bins based Scoring.
on GINI, Information Gain, and Weight of
Evidence (WOE) scores.

Scorecard Yes, if your site licenses SAS Credit Yes, if your site licenses SAS Credit Scoring.
Scoring.

Reject Inference Yes, if your site licenses SAS Credit Yes, if your site licenses SAS Credit Scoring.
Scoring.

Credit Exchange Yes, if your site licenses SAS Credit Yes, if your site licenses SAS Credit Scoring.
Scoring.

Network Performance

All SAS computations are performed on the server and are unaffected by the client/server network performance. All project
information such as functional settings and intermediate data sets are stored on the SAS server. GUI operations (such as editing a
process flow diagram, property sheets, and variables tables) depend on transferring data from the SAS server to the client GUI, and
are affected by both the server's availability and client/server network performance. SAS Enterprise Miner 5.1 is designed to be
tolerant of network disconnections and will clean up resources that include SAS sessions, accordingly. A reliable 512Kbps or greater
network bandwidth is recommended for reasonable client/server performance.

Multi-Tasking

The SAS Enterprise Miner 5.1 client will start a SAS session for interacting with the server and submitting user-entered SAS code. In
the default configuration, SAS Enterprise Miner 5.1 starts a separate SAS session for each parallel branch in the process flow
diagram. Also, a user of SAS Enterprise Miner 5.1 can start several diagrams that run simultaneously. Each new diagram starts a new
SAS session.

Note: It is possible for a user on a single CPU desktop system to start so many SAS sessions that overall system performance is
seriously degraded.
Threading

Some tasks in SAS Enterprise Miner 5.1 (such as data sorting, variable selection, and regression modeling) have been rebuilt to
distribute their work over multiple CPUs on the same system.

Models and Computation

SAS Enterprise Miner 4.3 and 5.1 use the same SAS procedures for core modeling and summarization, therefore, you should get the
same regression results when you use either release of the software.

SAS Enterprise Miner 4.3 and 5.1 generate SAS code to manage the use of SAS procedures. Because the SAS code that is
generated by each of these releases of SAS Enterprise Miner is different, you will get different results in analytical metadata
management and derived functions.

Analytical Metadata

SAS Enterprise Miner 4.3 uses the following attributes to maintain analytical metadata for variables:

● Role — input, target, id, freq, rejected...

● Level — interval, nominal, ordinal, binary, and unary

● Order — sort order for a categorical variable

SAS Enterprise Miner 5.1 contains the following additional attributes:

● Report — Yes or No. It specifies whether to generate a report.

● Family — identifies the general source of a variable for record keeping such as demographic, financial, historic, which can be
useful for constructing the data.

● Drop — specifies whether a variable should be dropped from the analysis

● Upperlimit — specifies the upper bound for an interval variable

● Lowerlimit — specifies the lower bound for an interval variable

● Distribution — indicates the expected univariate distribution (not used currently)

● Creator — specifies the ID of the node that creates a derived variable

● Comment — describes text.

Use the %EMDS macro to create a data source definition that has additional attributes for variables that are not used by Enterprise
Miner but that are included in reports that Enterprise Miner creates.

Metadata Sample

SAS Enterprise Miner 4.3 creates a metadata sample (which has 2,000 observations or less, by default) for data summarization,
graphics, and interactive modeling. The metadata sample is downloaded and persists on the client system. SAS Enterprise Miner 5.1
is a completely server-based system that does not use a metadata sample.

SAS Servers

SAS Enterprise Miner 4.3 and 5.1 do not require different server installation. However, a SAS Enterprise Miner 4.3 server requires the
SAS connect spawner, and SAS Enterprise Miner 5.1 server requires the SAS object spawner.

The SAS Enterprise Miner 5.1 server is responsible for project storage and computations. Having more memory available improves
both computational and GUI performance. A minimum of 512MB memory and 1GB or more is recommended for optimal performance.

Note: SAS Enterprise Miner 5.1 was not tested on z/OS operating systems. Currently, SAS Enterprise Miner 5.1 requires the HFS or
UNIX environment under z/OS.

Java Requirement

SAS Enterprise Miner 5.1 requires Java release 1.4.1. The SAS base language and procedures are not being ported to Java and will
continue to run in a threaded SAS System.

Java Middleware

The Java middleware is a new feature in SAS Enterprise Miner 5.1, but it is not a required component. The middleware is useful when
you want to disconnect the client from a running diagram, or to facilitate multiple users who are sharing SAS servers and a SAS Open
Metadata Server.

Java Client

The Java client is based on Java Swing GUI libraries that are part of Java 1.4.1. Following is a list of performance considerations for
the SAS Enterprise Miner 5.1 Java client:

● Memory — The maximum Enterprise Miner Java client memory is set to 500MB. Client systems should have 512MB memory
for best performance.

● Property Sheets and Variables Tables — The data for property sheets and variables table editors is retrieved from the server.
If the server is running a resource-intensive diagram, the property sheet or the variables table might be slow to display.

● Program Editor — User-entered code submitted through the Program Editor runs in the same SAS session as other GUI
operations. This blocks other GUI operations, such as editing a process flow diagram or a property sheet, and is the same
effect as in a traditional SAS Editor session.

● Graphics and Table Views — Data for interactive graphics and table views is transferred on demand from the server to the
client. A maximum of 10,000 rows of data can be transferred from the server to the client. For interactive graphics, you can
select a sampling method and size. SAS variable formats are not currently supported in interactive graphics and table views.

Enterprise Miner Model Repository

SAS Enterprise Miner 4.3 and SAS Enterprise Miner 5.1 can register models to the Enterprise Miner model repository. The repository
is a member of the SAS Metadata Server (SMS). When you register a SAS Enterprise Miner model, details of the model are stored in
the SMS. Additional details can be stored in a WEBDAV server, if that is available, and then configured.
The Model Repository Viewer is a Web application that queries and presents models that are found in the Enterprise Miner model
repository. This function is useful in archiving models over long periods of time and in distributing models to people who are not users
of Enterprise Miner such as business managers and database administrators. The components of the Model Repository Viewer can
be used to build custom applications for Web delivery of data mining models.

Batch Processing

SAS Enterprise Miner 5.1 supports SAS language-based batch processing by using macros. You can use all these macros together in
one or in many SAS jobs that conduct complete data-mining model building without using the GUI in SAS Enterprise Miner 5.1, or you
can use the macros with the GUI in a complementary cycle.

● %EMDS — supports the creation of SAS Enterprise Miner 5.1 data source definitions and management of table and column
metadata. This capability is useful in automating routine data source registration from batch data preparation jobs. For example,
you might have a SAS code job that extracts data from relational tables in a data warehouse and creates a table that is ready
for predictive modeling. You can add %EMDS to that job to create the data source definition that is needed for use in the SAS
Enterprise Miner 5.1 user interface or batch computing jobs.

● %EMTP — supports the creation of SAS Enterprise Miner 5.1 target profile definitions that are properties of a data source
definition. These target profile definitions contain information about the decision matrix, cost values, and prior probabilities,
which are used by Enterprise Miner modeling functions.

● %EM5BATCH — supports the building, running, and reporting of SAS Enterprise Miner 5.1 process flow diagrams. An exact
diagram can be run from either the SAS Enterprise Miner 5.1 user interface or from a batch job. The results can be viewed in
the SAS Enterprise Miner 5.1 user interface or included in a reporting SAS program. The SAS Enterprise Miner 5.1 user
interface includes a function to build batch code. This is useful when you want to automate creation and execution of a data
mining analysis.

Java API

SAS Enterprise Miner 5.1 supports a Java language API. See the SAS Enterprise Miner 5.1 documentation for usage information.
Java API is useful when you are building a Java language application and want to include data mining functionality. For example, if
you build a Web portal to neural networks, your Java servlet code can use the SAS Enterprise Miner 5.1 Java API to run the SAS
neural network. The Enterprise Miner Java API is experimental in SAS 9.1.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS 9.1 Text Miner

Overview

SAS Text Miner (AF version) software in SAS 9.1 contains the following new and enhanced
features:

● additional language support

● enhanced %tmfilter macro for reading textual data in various formats and for Web
crawling

● additional options for text parsing

● text parsing for more than one text variable

● new functionalities in Text Miner Results Browser to view original documents, to view an
HTML version of the documents, to perform nested "find similar" or "filter" requests, and
to create concept links

● macro variables to change the default settings

● improved performance

● specific error messages.

The data set SAMPSIO.REUTER3 is no longer available.

Details

Language Support

In addition to English, French, and German, SAS Text Miner enables you to analyze
documents in Danish, Dutch, Finnish, Italian, Portuguese, Spanish, and Swedish. If you have a
set of documents in various languages, the %tmfilter macro uses language detection
technology to identify the language of each document.
Input Data Pre-processing

In addition to reading documents that have various formats, the %tmfilter macro enables you to
create textual input data by crawling and retrieving Web pages that start from a specified
universal resource locator (URL).

When you use the %tmfilter macro to crawl Web pages, it creates two variables in the SAS
data set. The TEXT variable contains the text summary and the URI variable contains the
universal resource indicator (URI). The URI is a way of specifying the file so that the text can
be read across different operating environments.

Documents that are longer than 32k can be analyzed if the files are stored in the file system
and referenced by the URI variable.

The user-defined synonym list is applied regardless of whether the Stemmed words as root
form check box is selected.

When the same term is identified twice, one time as a standard term and the second time as
an entity, only the entity version is maintained.

Text Miner Node Settings

The Text Miner node enables you to specify the TEXT and URI variables. Also, you can
specify a set of parts-of-speech that can be ignored when the text is parsed.

The Role variable, of the synonym list, is now taken into account when the Same word as
different part of speech check box is selected. This means that the same term can have a
different synonym when it is used in different ways. In addition, it is no longer necessary to
have separate entries in the synonym data set to recognize words that are written in various
cases.

Processing Multiple Text Variables

You can process more than one text variable by sequentially adding an additional Text Miner
node for each variable that you want to parse. In this case, the output variables such as the
singular value decomposition (SVD) dimensions from the different Text Miner nodes will not be
overwritten.
Text Miner Results Browser

In the Results Browser, the number of documents and the number of parsed terms are
displayed at the top of the Documents and Terms tables.

The Text Miner Results Browser provides new icons for the most common tasks.

If you take advantage of the capability to use the URI variable, the Results Browser enables
you to view documents in their original formats (if any) such as WORD or PDF.

The Text Miner Results Browser enables you to perform nested "find similar" or "filter"
requests. In addition, when you close the results viewer, it will now retain any filter that is
currently applied and will export the files that have that filter. This enables you to copy the
results tool several times and have different aspects of your data feeding into other nodes from
each set of results.

The Text Miner Results Browser enables you to display the results of hierarchical clustering in
a hyperbolic tree applet.

Concept linking enables you to discover the relationship between two terms based on the
occurrences of the terms in the document collection. You can publish the results at a specified
location. Concept linking also uses a hyperbolic tree applet for display.

Macro Variables

SAS Text Miner provides a set of macro variables that enables you to change some of the
default settings. See the SAS Text Miner Appendixes for more information.

Performance

Many of the common tasks that are performed in the Results Browser (such as "Filter" and
"Find Similar") have been sped up dramatically by implementing the actions in compiled C
code. Performance of the singular value decomposition (SVD) calculations and parsing is also
improved.

Error Messages
SAS Text Miner provides improved error handling. You will get specific error messages when
the node run fails.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS ETL Studio

Overview of SAS ETL Studio

SAS ETL Studio 3.2 makes it much easier to perform the following tasks:

● extract the data in external files

● run and manage multiple jobs
● view data and statistics for tables and external files
● create custom transformations that help ETL specialists specify the correct parameters

Note: SAS ETL Studio 3.2 adds new features to the version of SAS ETL Studio that originally
shipped with SAS 9.1.3.

Details about SAS ETL Studio

What's New in SAS ETL Studio 3.2

The following features are new to SAS ETL Studio 3.2:

● Enhanced support for external files. Three new source designer wizards enable you to
create metadata for external files. The wizards enable you to manually specify metadata
such as the delimiters between values in the file. They enable you to import or
automatically generate other metadata, such as column definitions. The metadata for an
external file can then be used in a SAS ETL Studio job that reads data from the file or
writes data to the file.

● Enhanced support for SAS code transformation templates. The Transformation

Generator wizard enables you to create user-written SAS code transformation templates
and make them available in the Process Library tree. The wizard now enables you to
define options that will help users enter the correct values in the property window for
your SAS code transformation. Other new features include the ability to copy, paste,
import, and export SAS code transformations; the ability to specify multiple inputs or
outputs—or no inputs or outputs—for your transformation; the ability to define user-
defined variables for each input and output in your transformation; the ability to update
the source code and other properties of a SAS code transformation by using the
property window for that transformation.
● Multiple jobs can be executed in parallel. You can open multiple jobs in multiple Process
Designer windows and submit each job for execution. The jobs will execute in the
background, so that you can perform other tasks in SAS ETL Studio while a job is
executing. Each job has its own connection to the SAS application server, so the jobs
can execute in parallel.

● New Job Status Manager window. The Job Status Manager window enables you to view
the current status of a job, the time it started executing, the time it finished executing,
and other properties of a submitted job. The Job Status Manager window also enables
you to open a job in the Process Designer window, cancel and kill a job that is currently
running, and resubmit a job.

● Copy and paste support for metadata objects. In the Inventory tree, the Custom tree,
and the Project tree, you can copy and paste the metadata objects for jobs, tables,
external files, notes, and documents. In the Process Library tree, you can copy and
paste SAS code transformation templates.

● Enhanced validation for generated code. SAS ETL Studio can generate code for jobs.
The validation of generated code has been significantly enhanced for the current
release, especially for column mapping.

● Enhanced support for database management system (DBMS) tables. Source designers
can now generate metadata for tables in the following formats: OLEDB, MySQL,
Informix, Excel, and SQL Server. Source designers can register primary keys, foreign
keys, and indexes for those DBMSs that support access to the metadata about keys and
indexes.

● The View Data window is more robust. The View File and View Statistics windows have
been added. The View Data window now enables you to view SAS data sets of any size,
with paging; displays data in external files; supports threaded execution; supports table
options such as passwords; can display tables on computers that are remote from the
default SAS application server for SAS ETL Studio.

● Enhanced support for impact analysis. Impact analysis can now trace the impact of
changes to OLAP cubes, external files, SAS code transformations, and information
maps. Column use in Data Validation transformations can also be traced.

● New transformation template for forecasting. Use the new Forecasting transformation
template to run the SAS High-Performance Forecasting (HPF) procedure against a
warehouse data store. The HPF procedure provides a quick and automatic way to
generate forecasts for many sets of time-series or transactional data.

● New Calculated Members wizard for updating OLAP cubes. The Calculated Members
wizard enables you to add, edit, or delete calculated members in a selected cube.
● Enhanced support for the SCD Type 2 Loader transformation template. The generated
code for the SCD Type 2 Loader executes significantly faster in this release. Also, an
entry now can be closed out without writing a new current row in the target. The Use
SQL Pass-Thru option on the Options tab in the property window for the SCD Type 2
Loader now enables you to specify explicit pass-through for Oracle, DB2, Teradata, and
ODBC. On that same tab, the new Libref to save insert and update temporary tables
option enables you to specify a libref (the name of a pre-defined SAS library) that
permanently stores the insert and update tables that are generated by the SCD Type 2
Loader. These tables can then be used to generate statistics about records that have
been inserted versus records that have been updated. The insert and update tables can
also be used to restart target table loads without rerunning the entire job.

● Process Designer window enhancements:

❍ Derived mappings are column mappings in which the value of a target column is a
function of a source column. The Mapping tabs of the following transformations
have been updated to support derived mappings: the File Reader and File Writer
transformations for external files; the Loader transformation for tables; SAS code
transformations, and the Fact Table Lookup transformation.

❍ It is now easier to add and remove objects in SAS ETL Studio process flow
diagrams. For example, multi-node transformations, such as the SAS Splitter,
have pop-up menu options that enable you to add drop zones to the
transformation. Also, you can now add transformations to the drop zones of multi-
node transformations.

❍ You can turn off automatic column mapping for a transformation that is selected in
the current job. You must disable automatic mapping for a transformation if you
want to delete automatic mappings that are inappropriate in the current job.

❍ You can now select a job in the Custom tree or the Inventory tree and view the
job in the Process Designer window, submit the job, or view the code for the job.

● General user interface enhancements:

❍ Most wizards enable you to add new metadata objects to a user-defined group in
the Custom tree. This enables you to organize your metadata on the SAS ETL
Studio desktop.

❍ The SAS ETL Studio desktop displays the name of the current metadata profile,
the default SAS application server, the login ID and metadata identity of the
current user or group, and the current metadata server.

❍ Unique default names are provided when you create or copy the metadata for
 tables, jobs, and other objects.

For more information, see latest version of the SAS ETL Studio: User's Guide at support.
sas.com.

What's New in SAS ETL Studio in SAS 9.1.3

The following features are new to SAS ETL Studio in SAS 9.1.3:

● Support for the SAS Scalable Performance Data Server (SPD Server). The SPD Server
is a high performance, multi-user, parallel-processing data server that has a
comprehensive security infrastructure, backup and restore utilities, and sophisticated
administrative and tuning options. The SPD Server can be faster and more flexible than
other storage options, including the Scalable Performance Data Engine (SPD Engine).

● Two new transformation templates provide additional support for slowly changing
dimensions (SCD).

❍ Unlike the SCD Type 2 transformation (which tracks changes to a table's

descriptive attributes), the Key Effective Date transformation tracks changes in a
table’s keys. The Key Effective Date transformation tracks changes in a table that
does not have descriptive attributes, such as an intersection table—a table that
describes the relationships between two or more tables.

For example, suppose that you have a table of users that is named USERS, and
a table of groups that is named GROUPS. An intersection table that is named
USERS_X_GROUPS could describe the many-to-many relationships between
USERS and GROUPS. The Key Effective Date transformation would use date
ranges (beginning and ending dates) to detect when a new key combination has
been entered in USERS_X_GROUPS.

❍ The Surrogate Key Generator transformation enables you to create a unique

identifier for records—a surrogate key. You can use the surrogate key in
operations that would be difficult or impossible to perform with the original key.
For example, to make sorting easier, a numeric surrogate key could be generated
for an alphanumeric original key.

● The "Redeploy Jobs to Stored Process" feature rebuilds all stored processes that are
associated with SAS ETL Studio jobs. Use this feature whenever you need to update
stored processes to match their associated SAS ETL Studio jobs. You can use this
feature after you have updated a set of jobs for which stored processes have been
generated. You can also use this feature after a metadata repository has been promoted
from a test environment to a production environment.
 ● The property window for the Mining Results transformation was updated to make it
easier to select inputs and outputs.

If you are running SAS 9.1.3 at your site, you do not have to upgrade your metadata
for SAS ETL Studio 3.2.

For details about upgrading metadata for SAS 9.1.3, as well as installing and
configuring servers, libraries, users, and other resources that are required by SAS
ETL Studio, see the SAS Intelligence Platform: Planning and Administration Guide.

What's New in SAS ETL Studio in SAS 9.1.2

The following features are new to SAS ETL Studio in SAS 9.1.2:

● Support for slowly changing dimensions (SCD), which enables you to track changes to
data that occur over time. You can analyze those changes and forecast the impact on
future business decisions. For example, a company that provides long-distance
telephone service can learn which group of customers are most likely to move to a
different company. Those customers can be targeted in a marketing campaign and
offered an incentive to retain their current provider.

SAS ETL Studio provides two new transformations, SCD Type 2 Loader and Fact Table
Lookup, that enable you to track changes and retain historical records. Using the SCD
Type 2 Loader, you can load dimension tables and detect changes in source data, add
change tracking information, and generate primary key values. Using Fact Table
Lookup, you can map source columns into fact tables, use translation tables, and
specify responses when missing values are detected.

● Improved status messaging for ETL process flows. The status of a SAS ETL Studio job
or a transformation within a job can be automatically e-mailed, written to a file, or sent to
an event broker that will pass the status code to another application. You can also use
status code handling to capture job statistics, such as the number of records before and
after the append of the last table loaded in a job.

● Easier data validation for ETL process flows. The new Data Validation transformation
enables you to identify and act on duplicate values, invalid values, and missing values.
You can also develop your own validation process that translates source values by
using expressions or translation tables.

● Export and import SAS ETL Studio jobs. You can export jobs from SAS ETL Studio to
an XML file. You can then use SAS ETL Studio to import these jobs into the same
 metadata repository or a different repository.

● Support for stored processes. SAS ETL Studio jobs can be saved to a file and executed
later by a SAS Stored Process Server.

● Impact analysis and reverse impact analysis (data lineage). SAS ETL Studio enables
you to identify the tables, columns, and transformations that would be affected by, or
which have an impact on, a selected table or column. You can view a diagram and a
report that show the affected jobs, transformations, tables, and columns.

● Support for SAS Enterprise Miner scoring models. The new Mining Results
transformation enables you to read the metadata from a SAS Enterprise Miner scoring
model and create an output table that applies the model to the source data.

● Support for table concatenation and N-to-1 column mapping. The new Append
transformation enables you to create a single target by appending (concatenating) two
or more sources. The Append transformation supports N-to-1 column mapping.

● Support for using a physical table to update that table's metadata. If a change is made
directly to a physical table, you can use the Update Table Metadata feature to update
the table's metadata so that it matches the physical table.

● Support for optional macro variables in the code that SAS ETL Studio generates for a
job. The variables enable SAS ETL Studio jobs to access the metadata server and
retrieve relevant metadata. For example, the code that is generated for a job might
access the metadata server in order to retrieve an event code that is defined in a
repository.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.
What's New

What's New in SAS/ETS 9.0 and 9.1

Overview

New procedures in SAS/ETS include the following:

● The experimental ENTROPY procedure provides Generalized Maximum Entropy

estimation for linear systems of equations.
● The QLIM procedure analyzes univariate and multivariate models where dependent
variables take discrete values or values in a limited range.
● The TIMESERIES procedure analyzes time-stamped transactional data with respect to
time and accumulates the data into a time series format.
● The UCM procedure provides estimation for Unobserved Component Models, also
referred to as Structural Models.

Several new financial and date, time, and datetime functions have been added.

The new experimental SASEHAVR interface engine is now available to SAS/ETS for Windows
users for accessing economic and financial data residing in a HAVER ANALYTICS Data Link
Express (DLX) database.

New features have been added to the following SAS/ETS components:

● PROC ARIMA
● PROC EXPAND
● PROC MDC
● PROC MODEL
● PROC VARMAX
● PROC X12
● Time Series Forecasting System

Financial Functions

SAS/ETS now provides new financial functions. They are described in detail in Chapter 4,
"SAS Macros and Functions."

CUMIPMT
 Returns the cumulative interest paid on a loan between the start period and the end
period.

CUMPRINC
Returns the cumulative principal paid on a loan between the start period and the end
period.

IPMT
Returns the interest payment for a given period for an investment based on periodic,
constant payments and a constant interest rate.

PMT
Returns the periodic payment for a constant payment loan or the periodic saving for a
future balance.

PPMT
Returns the payment on the principal for an investment for a given period.

Date, Time, and Datetime Functions

SAS/ETS now provides the following new date, time, and datetime functions. See Chapter 3,
"Date Intervals, Formats, and Functions," for more details.

INTFMT
Returns a recommended format given a date, time, or datetime interval.

INTCINDEX
Returns the cycle index given a date, time, or datetime interval and value.

INTCYCLE
Returns the date, time, or datetime interval at the next higher seasonal cycle given a
date, time, or datetime interval.

INTINDEX
Returns the seasonal index given a date, time, or datetime interval and value.

INTSEA
Returns the length of the seasonal cycle given a date, time, or datetime interval.
SASEHAVR Engine

The experimental SASEHAVR interface engine gives Windows users random access to
economic and financial data residing in a HAVER ANALYTICS Data Link Express (DLX)
database. You can limit the range of data that is read from the time series and specify a
desired conversion frequency. Start dates are recommended on the libname statement to help
you save resources when processing large databases or when processing a large number of
observations. You can further the subsetting of your data by using the WHERE, KEEP, or
DROP statements in your DATA step. You can use the SQL procedure to create a view of your
resulting SAS data set.

ARIMA Procedure

The OUTLIER statement of the ARIMA procedure has become production in SAS System 9. A
new ID option that provides date labels to the discovered outliers has been added.

In the presence of embedded missing values, the new default White Noise test of residuals
uses the one proposed by Stoffer and Toloi (1992), which is more appropriate.

The default forecasting algorithm when the data have embedded missing values and the
model has multiple orders of differencing for the dependent series has been slightly modified.
This modification usually improves the statistical properties of the forecasts.

ENTROPY Procedure

The new experimental ENTROPY procedure implements a parametric method of linear

estimation based on Generalized Maximum Entropy.

Often the statistical-economic model of interest is ill-posed or underdetermined for the

observed data, for example when limited data is available or acquiring data is costly. For the
general linear model this can imply that high degrees of collinearity exist among explanatory
variables or that there are more parameters to estimate than observations to estimate them
with. These conditions lead to high variances or non-estimability for traditional GLS estimates.
The principle of maximum entropy, at the base of the ENTROPY procedure, is the foundation
for an estimation methodology that is characterized by its robustness to ill-conditioned designs
and its ability to fit overparameterized models.

Generalized Maximum Entropy, GME, is a means of selecting among probability distributions

so as to choose the distribution that maximizes uncertainty or uniformity remaining in the
distribution, subject to information already known about the distribution itself. Information takes
the form of data or moment constraints in the estimation procedure. PROC ENTROPY creates
a GME distribution for each parameter in the linear model, based upon support points supplied
by the user. The mean of each distribution is used as the estimate of the parameter. Estimates
tend to be biased, as they are a type of shrinkage estimate, but will typically portray smaller
variances than OLS counterparts, making them more desirable from a mean squared error
viewpoint.

PROC ENTROPY can be used to fit simultaneous systems of linear regression models,
Markov models, and seemingly unrelated regression models as well as to solve pure inverse
problems and unordered, multinomial choice problems. Bounds and restrictions on
parameters can be specified and Wald, Likelihood ratio, and Lagrange multiplier tests can be
computed. Prior information can also be supplied to enhance estimates and data.

EXPAND Procedure

The EXPAND procedure has several new transformation operators: moving product, moving
rank, moving geometric mean, sequence operators, fractional differencing, Hodrick-Prescott
filtering, and scaling.

The EXPAND procedure has a new option for creating time series graphics. The PLOT=
option enables you to graph the input, output, and transformed time series.

MDC Procedure

The RESTRICT statement now has a new syntax and supports linear restrictions.

The new BOUNDS statement enables you to specify simple boundary constraints on the
parameter estimates. You can use both the BOUNDS statement and the RESTRICT statement
to impose boundary constraints; however, the BOUNDS statement provides a simpler syntax
for specifying these kinds of constraints.

MODEL Procedure

The SMM (Simulated Method of Moments) estimation is now available as an option in the FIT
statement. This method of estimation is appropriate for estimating models in which integrals
appear in the objective function and these integrals can be approximated by simulation. There
may be various reasons for that to happen, for example, transformation of a latent model into
an observable model, missing data, random coefficients, heterogeneity, etc. A typical use of
SMM is in estimating stochastic volatility models in finance, where only the stock return is
observable, while the volatility process is not, and needs to be integrated out of the likelihood
function. The simulation method can be used with all the estimation methods except Full
Information Maximum Likelihood (FIML) in PROC MODEL. Simulated Generalized Method of
Moments (SGMM) is the default estimation method.

Heteroscedastic Corrected Covariance Matrix Estimators (HCCME) have been

implemented. The HCCME= option selects which correction is applied to the covariance
matrix.

Instrumental variables can now be specified for specific equations rather than for all
equations. This is done with expanded syntax on the INSTRUMENT statement.

QLIM Procedure

The new QLIM procedure analyzes univariate and multivariate limited dependent variable
models where dependent variables take discrete values or dependent variables are observed
only in a limited range of values. This procedure includes logit, probit, tobit, selection, and
multivariate models. The multivariate model can contain discrete choice and limited
endogenous variables as well as continuous endogenous variables.

The QLIM procedure supports the following models:

● linear regression model with heteroscedasticity

● probit with heteroscedasticity
● logit with heteroscedasticity
 ● tobit (censored and truncated) with heteroscedasticity
● Box-Cox regression with heteroscedasticity
● bivariate probit
● bivariate tobit
● sample selection and switching regression models
● multivariate limited dependent variables

TIMESERIES Procedure

The new TIMESERIES procedure analyzes time-stamped transactional data with respect to
time and accumulates the data into a time series format. The procedure can perform trend and
seasonal analysis on the transactions. Once the transactional data are accumulated, time
domain and frequency domain analysis can be performed on the resulting time series. The
procedure produces numerous graphical results related to time series analysis.

UCM Procedure

The new UCM procedure, experimental in SAS System 9, is production in SAS 9.1. You
can use this procedure to analyze and forecast equally spaced univariate time series data
using Unobserved Components Models (UCM).

The UCMs can be regarded as regression models where, apart from the usual regression
variables, the model consists of components such as trend, seasonals, and cycles. In time
series literature UCMs are also referred to as Structural Models. The different components in a
UCM can be modeled separately and are customized to represent salient features of a given
time series. The analysis provides separate in-sample and out of sample estimates (forecasts)
of these component series. In particular, model-based seasonal decomposition and seasonal
adjustment of the dependent series is easily available. The distribution of errors in the model is
assumed to be Gaussian and the model parameters are estimated by maximizing the
Gaussian likelihood. The UCM procedure can handle missing values in the dependent series.

The domains of applicability of PROC UCM and PROC ARIMA are virtually identical; however,
decomposition of a series in features such as trend, seasonals, and cycles is more convenient
in PROC UCM. A seasonal decomposition of a time series can also be obtained using other
procedures, for example, PROC X12. However, these seasonal decompositions generally do
not take into account regression and other effects and are not model based. The seasonal
decomposition in PROC UCM is based on a comprehensive model, providing all the
advantages of model diagnostics.

VARMAX Procedure

The VARMAX procedure now provides the following features:

● The ECTREND option is available in the ECM=( ) option of the MODEL statement to fit
the VECM(p) with a restriction on the drift. The ECTREND option is ignored when either
the NSEASON or NOINT option is specified.
● You can now use the DFTEST option at multiple lags. For example, DFTEST=(DLAG=
(1)(12)) provides the Dickey-Fuller regular unit root test and seasonal unit root test. If the
TREND= option is specified, the seasonal unit root test is not available.
● The DYNAMIC option is added to the PRINT=( ) option. This representation displays the
contemporaneous relationships among the components of the vector time series.
● The CORRX, CORRY, COVPE, COVX, COVY, DECOMPOSE, IARR, IMPULSE,
IMPULSX, PARCOEF, PCANCORR, and PCORR options can be used with the number
in parentheses in the PRINT=( ) option. For example, you can use CORRX or CORRX
(number). The options print the number of lags specified by number. The default is the
number of lags specified by the LAGMAX=number.
● The subset BVAR model is now available.
● The statistics for the one lagged coefficient matrix are removed in the ECM.
● The last columns of the BETA and ALPHA are removed in the COINTTEST option when
the NOINT option is not specified.
● The long variable names are available in the model parameter estimation table.
● The schematic representation of the estimates that shows the significance of the
parameters is now available.
● Two new ODS Tables, ParameterGraph and GARCHParameterGraph, are added.

Many ODS table names have been changed.

X12 Procedure

The X12 procedure default behavior has changed with regard to missing leading and trailing
values. Previously the default was not to trim leading/trailing missing values from the series.
This made it difficult to process multiple series within a data set when the series had differing
spans. Now the default is to trim leading and trailing missing values. The new NOTRIMMISS
option provides the old default behavior; when NOTRIMMISS is specified, PROC X12 will
automatically generate missing value regressors for any missing value within the span of the
series, including leading and trailing missing values.

The following statements and options are new:

● The AUTOMDL statement uses the TRAMO method based on the work of Gomez and
Maravall (1997a and 1997b) to automatically select the ARIMA part of a regARIMA
model for the time series.
● The OUTLIER statement automatically detects additive, level shift, and temporary
change outliers in the time series. After the outliers are identified, the appropriate
regression variables are incorporated into the model.
● The MAXITER and TOL options of the ESTIMATE statement provide additional control
over the convergence of the nonlinear estimation.
● The ITPRINT and PRINTERR options of the ESTIMATE statement enable you to
examine the iterations history of the nonlinear estimation.
● The FINAL and FORCE options of the X11 statement enable you to control the final
seasonally adjusted series. The FINAL option specifies whether outlier, level shift, and
temporary change effects should be removed from the final seasonally adjusted series.
The FORCE option specifies whether or not the yearly totals of final seasonally adjusted
series match the totals of the original series.

Time Series Forecasting System

Enhancements to this graphical point-and-click system provide new kinds of forecasting

models, better ways to customize lists of models, greater flexibility in sharing projects over a
network, and support for graphical and tabular Web reports:

● The Factored ARIMA Model Specification window provides a general purpose interface
for specifying ARIMA models. You can specify any number of factors and select the AR
and MA lags to include in each factor. This makes it easy to model series with unusual
and/or multiple seasonal cycles.
● Improvements to the Model Selection List Editor window enable you to open
alternate model lists included with the software as well as user defined model lists. You
can create a new model list, open an existing model list, modify it, use it to replace the
current list, append it to the current list, save it in a catalog, assign it to a project, or
assign it as a user default list for newly created projects. Several new ARIMA and
dynamic regression model lists are provided. You can combine these into large sets for
 automatic model selection and select from them to create the best set of candidate
models for your data.
● Project options are no longer stored exclusively in the SASUSER library. You can
use any path to which you have write access by assigning the libname TSFSUSER. The
system prompts you for this path if you do not have write access to the SASUSER
library.
● The Series Viewer and Model Viewer support saving graphs and tables via the
Output Delivery System (ODS). Select the "Use Output Delivery System" option in the
Save As dialog to create html pages and corresponding gif files. You can access and
organize these using the ODS Results window, display them automatically in your
browser (depending on your results preferences settings), or publish them via the
Internet or an intranet. You can also create other forms of output by providing your own
ODS statements.
● The Time Series Viewer and Time Series Forecasting System can now be started from
a macro submitted from the Program Editor or the Enhanced Editor. The FORECAST
and TSVIEW macros accept the same arguments as the FORECAST and TSVIEW
commands. You can use the FORECAST macro to generate and submit any number of
independent unattended forecasting runs from a data step program.

References

Gomez, V. and A. Maravall (1997a), "Program TRAMO and SEATS: Instructions for the User,
Beta Version," Banco de Espana.

Gomez, V. and A. Maravall (1997b), "Guide for Using the Programs TRAMO and SEATS, Beta
Version," Banco de Espana.

Stoffer, D. and Toloi, C. (1992), "A Note on the Ljung-Box-Pierce Portmanteau Statistic with
Missing Data," Statistics & Probability Letters 13, 391-396.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/Genetics 9.0 and 9.1

Overview

SAS/Genetics includes several new procedures:

● the experimental HTSNP procedure for selecting a subset of SNPs that identify
groups of haplotypes that minimize within-group diversity
● the INBREED procedure for estimating covariance and/or inbreeding coefficients for
pedigrees

New features have been added to the SAS/Genetics procedures:

● ALLELE
● CASECONTROL
● FAMILY
● HAPLOTYPE
● PSMOOTH

including options that accommodate new data formats.

Accommodating New Data Formats

There are several new options available for analyzing data in different formats. The
GENOCOL and DELIMITER= options have been added to four procedures: ALLELE,
CASECONTROL, FAMILY, and HAPLOTYPE. The GENOCOL option enables you to use
columns containing marker genotypes instead of a pair of columns containing the two alleles
that comprise the genotype. You can specify the delimiter that is used to separate the two
alleles with the DELIMITER= option. In addition, the experimental options TALL, MARKER=,
and INDIV= can be used collectively for data in a "tall-skinny" format in the ALLELE,
CASECONTROL, and HAPLOTYPE procedures. Data sets in this format contain a marker
identifier and individual identifier, along with one variable containing the marker genotypes or
two columns containing marker alleles. See the individual procedures' Syntax sections for
more details about these new options.
ALLELE Procedure

The new options ALLELEMIN=, GENOMIN=, and HAPLOMIN= enable you to specify the
minimum estimated frequency for an allele, genotype, or haplotype, respectively, to be
included in its corresponding ODS table. By default, any allele, genotype, or haplotype that
occurs at least once in the sample is included in the respective table. These options can be
used to reduce the size of the ODS tables, or alternatively, the GENOMIN= or HAPLOMIN=
options can be set to 0 to view all possible genotypes or haplotypes, not just those that are
observed.

CASECONTROL Procedure

The new NULLSNPS= option enables you to specify SNPs to be used in calculating the
variance inflation factor for genomic control. By default, if VIF is specified, the variables in the
VAR statement are used, but this new option provides a way of using particular SNPs,
separate from those being tested for association and which are assumed to have no
association with the TRAIT variable, for genomic control (Bacanu, Devlin, and Roeder 2000).

You can request that approximations of exact p-values for the case-control tests be
reported in place of the asymptotic chi-square p-values (Westfall and Young 1993). The new
PERMS= option indicates the number of permutations to be used for a Monte Carlo estimate of
each exact p-value, and the random seed can be provided in the new SEED= option.

The OUTSTAT= data set includes two new columns: NumTrait1 and NumTrait2, where the
values 1 and 2 are replaced by the two values of the TRAIT variable. These columns contain
the number of genotyped individuals with each trait value for each marker.

FAMILY Procedure

The new "Family Summary" ODS table displays information about each family in the data
set at each of the markers. This includes the number of parents genotyped, the number of
affected children, the number of unaffected children, as well as an error code indicating what
type of, if any, Mendelian inconsistencies occur in a nuclear family's genotypes at each
marker. The new SHOWALL option can be used to display this information for all families at
each marker. By default, only those families with a genotype error are included in the table for
the marker(s) where the error occurs.

The new "Description of Error Codes" ODS table provides descriptions of the numerical
error codes used in the "Family Summary" table.

Approximations of exact p-values can now be requested in place of the asymptotic chi-
square p-values for the TDT, S-TDT, SDT, and combined S-TDT and SDT using the PERMS=
option. The number specified indicates the number of permutations to be used in the Monte
Carlo procedure for estimating exact p-values. You can provide the random seed used for the
permutations in the new SEED= option.

The multiallelic SDT and multiallelic combined SDT/TDT are now implemented as
described by Czika and Berry (2002).

HAPLOTYPE Procedure

The EST=EM | STEPEM option enables you to specify whether you would like haplotype
frequencies to be estimated using the original EM algorithm or the new stepwise EM algorithm
(Clayton 2002). When EST=STEPEM is specified, a cutoff to be used for trimming the set of
haplotypes before adding an additional locus can be given in the new STEPTRIM= option.

The ID statement enables variables from the input data set to be included in the OUT=
data set created by PROC HAPLOTYPE in addition to or instead of the _ID_ variable, a unique
numeric identifier assigned to each individual by the procedure.

HTSNP Procedure

The experimental HTSNP procedure implements search algorithms for identifying a subset
of SNPs called haplotype tag SNPs (htSNPs) (Johnson et al. 2001) that capture much of the
linkage disequilibrium and haplotype diversity among common haplotypes.

INBREED Procedure
 The INBREED procedure is now included in SAS/Genetics in addition to SAS/STAT where
it originated. This procedure calculates the covariance or inbreeding coefficients for pedigrees
either by treating the population as a single generation or by performing separate analyses on
each generation. You can also opt to have inbreeding and covariance coefficients averaged
within each gender category.

PSMOOTH Procedure

The new option TPM implements the truncated product method (Zaykin et al. 2002) for
smoothing p-values over windows of markers. The TAU= option, also new, can be used in
conjunction with the TPM option to specify the value of at which p-values are truncated.

References

Bacanu, S-A., Devlin, B., and Roeder, K. (2000), "The Power of Genomic Control," American
Journal of Human Genetics, 66, 1933 -1944.

Clayton, D. (2002), "Choosing a Set of Haplotype Tagging SNPs from a Larger Set of Diallelic
Loci," [http://www-gene.cimr.cam.ac.uk/clayton/software/stata/htSNP/htsnp.pdf].

Czika, W. and Berry, J.J. (2002), "Using All Alleles in the Multiallelic Versions of the SDT and
Combined SDT/TDT," American Journal of Human Genetics, 71, 1235 -1236.

Johnson, G.C.L. et al. (2001), "Haplotype Tagging for the Identification of Common Disease
Genes," Nature Genetics, 29, 233 -237.

Westfall, P.H. and Young, S.S. (1993), Resampling-based Multiple Testing, New York: John
Wiley & Sons, Inc.

Zaykin, D.V., Zhivotovsky, L.A., Westfall, P.H., and Weir, B.S. (2002), "Truncated Product
Method for Combining P-values," Genetic Epidemiology, 22, 170 -185.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/GRAPH 9.0 and 9.1

Overview

It's easier than ever to produce enhanced and detailed, informative graphics for your Web
presentations. New features in SAS/GRAPH include:

● three new procedures: GAREABAR, GBARLINE, and MAPIMPORT

● new options in the GCHART procedure for producing standard pie or donut charts with a
detailed, inner pie overlay

● new options in the GRADAR procedure for adjusting how a chart looks and for
specifying annotation

● support for the new DOCUMENT procedure for the Output Delivery System (ODS)

● the new SAS Maps Online application

● server-side rendering using the ACTXIMG and JAVAIMG devices

● client support for annotation

● client support for ODS styles

● ActiveX support for creating graphs interactively

● ActiveX support for radar charts produced with the GRADAR procedure

● the new Java Constellation Applet

● user interface enhancements for the client graphs, such as redesigned dialogs.

Note:

● This section describes the features of SAS/GRAPH that are new or enhanced since
SAS 8.2.
 ● z/OS is the successor to the OS/390 operating system. SAS/GRAPH 9.1 is supported
on both OS/390 and z/OS operating systems and, throughout this document, any
reference to z/OS also applies to OS/390, unless otherwise stated.

Details

Procedures

The following procedures are new or enhanced:

● The GAREABAR procedure generates bar graphs in which the width of the bars are
proportional to a characteristic of the data element that is represented by the bars. Area
bar charts are supported only when you specify device=activex or
device=actximg .

● The new GBARLINE procedure enables you to create vertical bar charts that have line
plot overlays.

Note: The GBARLINE procedure is not supported for Java.

● The new MAPIMPORT procedure enables you to import ESRI Shapefiles into SAS/
GRAPH map data sets.

● The new DOCUMENT procedure for ODS enables you to re-arrange or to duplicate
reports--including graphs--without having to rerun your analysis. You can display output
to any ODS output format without executing your SAS programs again. For more
information, see the DOCUMENT procedure in SAS Output Delivery System: User's
Guide.

● New options in the PIE statement in the GCHART procedure enable you to create detail
pie charts that have an inner pie overlay. The slices in the overlay align with the slices in
the outer pie and show detailed information about the major components that comprise
the outer slice. The new options are DETAIL=, DETAIL_PERCENT=,
DETAIL_RADIUS=, DETAIL_SLICE=, DETAIL_THRESHOLD=, and DETAIL_VALUE=.

● The GRADAR procedure has the following new options:

❍ ANNOTATE= specifies an annotate data set.

 ❍ INBORDER requests a border around plots.

❍ INHEIGHT= specifies the height in percent screen units of text used inside the
frame of the chart.

❍ LAST= specifies that the spoke that corresponds to the category is displayed to
the left of the start angle.

❍ MAXNVERT= specifies the maximum number of vertices.

❍ MISSING accepts a missing value as a valid midpoint for the chart variable.

❍ NOFRAME suppresses the frame that is drawn around the chart by default.

❍ NOZEROREF turns off the zero reference line when negative values are plotted.

❍ OTHER= specifies a new category that merges all categories that are not
selected because of the MAXNVERT= option.

❍ ORDERACROSS= specifies the display order for the values of the ACROSS=
variable.

❍ SPIDER draws lines on a radar chart that connect the spokes instead of the
default tick marks. The resulting lines look similar to a "spider web."

❍ STARINRADIUS= and STAROUTRADIUS= determine the diameter of the stars.

● The LEVELS=ALL option in the GMAP procedure uses a color ramp to assign a
continuous color scheme to each response value.

SYMBOL Statement

The SINGULAR= option tunes the algorithm that is used to check for singularities.

Graphics Options

The following graphics options are new:

USERINPUT
 determines whether user input is enabled for the device.

SWFONTRENDER

specifies the method used to render software fonts.

The Annotate Facility

The following macros are new:

%CENTROID

retrieves the centroids of polygons.

%MAPLABEL

creates an output data set that can be used with the ANNO= option in PROC GMAP.

SAS Maps Online Application

The new SAS Maps Online application enables you to download: data updates, sample SAS/
GRAPH programs that use the map data sets delivered with SAS/GRAPH, and GIF images of
maps. SAS Maps Online is located at support.sas.com/rnd/datavisualization/
mapsonline/html

Pop-up Data Tips for Web Graphics

Web graphics now support pop-up data tips. A pop-up data tip is text that is displayed when a
user moves the cursor over a portion of a Web graphic. You can add custom data tips to the
output of any SAS/GRAPH procedure that supports the HTML= option.

Server-Side Rendering

The ACTXIMG and JAVAIMG devices generate images on the server that match the look of
the client graphs. These devices are especially useful when you do not need the interactivity
that is provided by the client graphs. ACTXIMG is only available for Windows.
Client Support for Annotation

The Java and ActiveX clients now support annotation through the Output Delivery System
(ODS) for the G3D, GBARLINE, GCHART, GCONTOUR, GMAP, GPLOT, and GRADAR
procedures. You can specify the ANNOTATE= option in these procedures when you are using
the JAVA, JAVAIMG, ACTIVEX, and ACTXIMG device drivers. All annotate functions are
available with each device driver (except the FRAME and IMAGE functions, which are
available only with ACTIVEX and ACTXIMG).

Client Support for ODS Styles

ODS styles now affect both table and client graph output. Sixteen new graph styles provide a
consistent look for your entire ODS output, which enhances readability and usability.

ActiveX Control

The following are enhancements for the ActiveX Control:

● The ActiveX control now supports creating graphs interactively. You can import data
from SAS data sets, Microsoft Excel files, or Microsoft Access files.

Note: To create graphs interactively, you must have Enterprise Guide 2.0 HotFix 11 or
higher installed.

● The ActiveX control now supports radar charts that are produced by using the GRADAR
procedure.

● The ActiveX control menus now enable the following additional languages: Chinese,
Japanese, Korean, and Russian. (The following languages were also available in SAS
8.2: French, German, Hebrew, Hungarian, Italian, Polish, and Spanish.

Java Constellation Applet and DS2CONST Macro

The new Java Constellation Applet, which you can generate by using the DS2CONST macro,
enables you to see the relationships among node link data, such as Web click data, network
flow data, and simple affinity data. You can interactively select a set of nodes to see the
relationships among the nodes. You can see all of the links coming to the set of nodes or going
out of a set of nodes.

Java Treeview Applet and DS2TREE Macro

The new Java Treeview applet, which you can generate by using the DS2TREE macro, shows
the parent-child relationships of elements in a hierarchical structure. It provides an optional
"fish-eye" distortion that highlights the central area of interest, and enables you to search for,
hide, and display element subtrees. A Treeview diagram is ideal for displaying data such as
organizational charts or the hierarchical relationships of the pages of a Web site.

Java Contour Applet

The following are enhancements for the Java Contour Applet:

● a new plot style, Smooth, enables you to display flat (linearly interpolated) planes with
no outlines.

● several new parameters.

Java Graph Applet

The following are enhancements in the Java Graph Applet:

● For bar charts, error bars and the CERROR= option (which sets their color) are now
enabled. Bars can be labeled by statistics by using the OUTSIDE= and INSIDE=
options. Patterns are enabled for 2-D bars, and improved support for the VALUE= option
in the AXIS statement is provided.

● For pie charts with group variables, the OTHER=, HTML=, INVISIBLE, and EXPLODE
options are available. Data tips can now be displayed for groups. The V=EMPTY option
in a PATTERN statement creates hollow pie slices. The LABEL= option enables you to
specify font height and color for donut charts.

● Scatter plots now enable the BOX, STD, and HILOC interpolations. For these
interpolations, you can use the SYMBOL statement to specify colors, font height and
width, line type, point labels, and box width.

● The Graph applet menus now enable the following additional languages: Chinese,
 Japanese, Korean, and Russian. (The following languages were also available in SAS
8.2: French, German, Hebrew, Hungarian, Italian, Polish, and Spanish.)

● The MENUREMOVE parameter can be used to disable menus and menu options in the
applet's user interface.

User-Defined Formats

The Java and ActiveX devices now support user-defined formats, except for nested user-
defined formats. For information about defining formats, see the documentation for the
FORMAT procedure in the Base SAS Procedures Guide.

Colors

Color names can now be a maximum of 64 characters in length.

Fonts

The following fonts have been added:

● Davidb (Hebraic)

● Fsong (Chinese)

● Hebrewb

● Hei (Chinese)

● Mincho (Japanese)

PAGEFIT Attribute for PostScript

The new PAGEFIT image attribute enables you to adjust how a PostScript image fits on the
page. The PAGEFIT attribute replaces the NOFIT attribute.

GTITLE and GFOOTNOTE Options for the ODS Statement

The behavior of the GTITLE and GFOOTNOTE options has been changed--when you specify
NOGTITLE or NOGFOOTNOTE, the space in the graphic that would have been used for the
title or footnote is allocated to the procedure output rather than being left empty. You need to
be aware of this change if you are using annotation or mapping coordinates. For more
information, see Controlling Where Titles and Footnotes are Rendered.

Enhancements in SAS/GRAPH Documentation

In addition to information about new features, the SAS/GRAPH documentation now includes
information about the following:

● COLORMAC and HLPCLR macros and expanded information about choosing color
schemes

● DSGI routine GASK ('PATREP') and the functions GSET('PATREP') and GRAPH
('PLAY')

● map formats that are available with the GMAP procedure

● HTML generators, which are macros that generate HTML files that run one of the SAS/
GRAPH applets: DS2CONST (Constellation Applet), DS2TREE (Treeview Applet), and
DS2CSF (Rangeview Applet).

● attributes and parameters for Java and ActiveX, which were formerly documented in the
SAS Output Delivery System: User's Guide.

Also, additional examples of Web-output programs have been added to the documentation and
the SAS/GRAPH sample library. Documentation for the JAVA2 device driver has been
removed, because JAVA and JAVA2 are now functionally equivalent.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New in SAS 9, 9.1, 9.1.2, and 9.1.3 High-
Performance Forecasting

Overview

New features, procedures, and functions have been added to SAS High-Performance
Forecasting as follows:

New features have been added to PROC HPF.

New procedures have been added for creating model specifications and model selection lists:

● PROC HPFARIMASPEC
● PROC HPFESMSPEC
● PROC HPFEXMSPEC
● PROC HPFIDMSPEC
● PROC HPFUCMSPEC
● PROC HPFSELECT

A new procedure has been added for creating calendar events:

● PROC HPFEVENTS

New procedures have been added for computations:

● PROC HPFDIAGNOSE
● PROC HPFENGINE

New experimental functions have been added for forecast scoring:

● HPFSCSUB Function
● HPFSCSIG Function

SAS High-Performance Forecasting has a new version numbering scheme. SAS High-
Performance Forecasting 2.1 provides the same features and functionality as SAS 9.1.3 High-
Performance Forecasting software, but adds new scalability features that improve processing
performance.
Details

HPF New Version Number

SAS High-Performance Forecasting has a new version numbering scheme. SAS High-
Performance Forecasting 2.1 provides the same features and functionality as SAS 9.1.3 High-
Performance Forecasting software, but adds new scalability features that improve processing
performance.

HPF Procedure

The HPF procedure has the following new features.

New options related to forecast model selection:

● HOLDOUTPCT= option
● SEASONTEST= option
● SELECT= option

A new option related to forecast model initialization:

● NBACKCAST= option

A new statement related to intermittent demand models:

● IDM statement

New options related to out-of-sample forecast performance statistics:

● BACK= option
● PRINT=PERFORMANCE option
● PRINT=PERFORMANCESUMMARY option
● PRINT=PERFORMANCEOVERALL option

New options related to the processing of the data:

● NOTSORTED option
● REPLACEBACK option
● SORTNAMES option
New options related to printed and graphical output:

● PLOT= option
● PRINT=STATES option

A new option related to the message log:

● MAXERROR= option

HPFARIMASPEC Procedure

The new HPFARIMASPEC procedure is used to create an Autoregessive Integrated Moving

Average (ARIMA) model specification file. The output of the procedure is an XML file that
stores the intended ARIMA model specification. This XML specification file can be used to
populate the model repository used by the HPFENGINE procedure. (Likewise, the XML files
generated by the other model specification procedures in this section can also be used to
populate the model repository used by PROC HPFENGINE.)

HPFESMSPEC Procedure

The new HPFESMSPEC procedure is used to create an Exponential Smoothing Model (ESM)
specification file. The output of the procedure is an XML file that stores the intended ESM
model specification.

HPFEXMSPEC Procedure

The new HPFEXMSPEC procedure is used to create an External Model (EXM) specification
file. The output of the procedure is an XML file that stores the intended EXM model
specification.

HPFIDMSPEC Procedure

The HPFIDMSPEC procedure is used to create an Intermittent Demand Model (IDM)

specification file. The output of the procedure is an XML file that stores the intended IDM
model specification.

HPFUCMSPEC Procedure

The new HPFUCMSPEC procedure is used to create an Unobserved Component Model

(UCM) specification file. The output of the procedure is an XML file that stores the intended
UCM model specification.

HPFSELECT Procedure

The new HPFSELECT procedure is used to create model selections lists. A model selection
list contains references to candidate model specifications stored in the model repository. The
output of the procedure is an XML file that stores the intended model selection list.

HPFEVENTS Procedure

The HPFEVENTS procedure provides a way to create and manage events associated with
time series. The procedure can create events, read events from an events data set, write
events to an events data set, and create dummies based on those events, if date information is
provided.

A SAS event is used to model any incident that disrupts the normal flow of the process that
generated the time series. Examples of commonly used events include natural disasters, retail
promotions, strikes, advertising campaigns, policy changes, and data recording errors.

An event has a reference name, a date or dates associated with the event, and a set of
qualifiers. The event exists separately from any time series; however, the event may be
applied to one or more time series. When the event is applied to a time series, a dummy
variable is generated that may be used to analyze the impact of the event on the time series.

HPFDIAGNOSE Procedure

The new HPFDIAGNOSE procedure is an automatic modeling procedure to find the best
model among ARIMA Models, Exponential Smoothing Models, and Unobserved Component
Models.

The HPFDIAGNOSE procedure has the following functionality:

● intermittency test
● functional transformation test
● simple differencing and seasonal differencing test
● tentative simple ARMA order identification
● tentative seasonal ARMA order identification
● outlier detection
● significance test of events
● transfer functions identification
● intermittent demand model
 ● exponential smoothing model
● unobserved component model

HPFENGINE Procedure

The new HPFENGINE procedure provides large-scale automatic forecasting of transactional or

time series data. The HPFENGINE procedure extends the foundation built by PROC HPF,
enabling the user to determine the list of models over which automatic selection is performed.

The use of many forecast model families is supported when HPFENGINE is used in
conjunction with new procedures that generate generic model specifications. Among these
models are:

● ARIMA
● Unobserved Component Models (UCM)
● Exponential Smoothing Models (ESM)
● Intermittent Demand Models (IDM)
● External Models (EXM)

Furthermore, users may completely customize the operation by defining their own code to
generate forecasts.

For models with inputs, the STOCHASTIC statement is especially helpful for automatically
forecasting those inputs that have no future values.

Also supported is the generation of a portable forecast score. The output of the SCORE
statement is a file or catalog entry that, when used with the new function HPFSCSUB, can be
used to efficiently generate forecasts outside of the HPFENGINE procedure.

The new HPFDIAGNOSE procedure produces output that is compatible with HPFENGINE. As
a result, the task of candidate model specification can be entirely automated.

HPFSCSUB Function

The experimental HPFSCSUB function uses score files to produce forecasts outside of the
HPFENGINE procedure. Being a function, it is particularly well suited for use within other SAS
programming contexts, such as the DATA step, or procedures that permit the specification of
functions, such as the NLP procedure. The only input required is a reference to the score
function, the horizon, and future values of any inputs.

HPFSCSIG Function
The experimental HPFSCSIG function generates a sample signature for subsequent use by
the HPFSCSUB function.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/IML 9.0 and 9.1

Overview

New to SAS/IML are the following:

● A set of new iterative methods for large sparse systems of linear equations
● A set of new direct algorithms utilizing Cholesky factorization for large sparse systems of
linear equations
● A new chapter on Genetic Algorithms
● A set of new functions and calls for grouping and sorting
● A set of new calls for random number generation
● A new programming feature that extends the matrix subscripting functionality

Iterative Methods for Large Sparse Systems of Linear Equations

Iterative methods create a new direction in IML: the capability to handle large, sparse
matrices and systems. With sparsity exploitation and iterative approximation algorithms, IML
can solve linear systems containing as many as 106 variables on a regular PC. The new
methods that are used are Conjugate Gradient, Minimum Residual, and Biconjugate Gradient.
The collection of preconditioners include fast incomplete Cholesky factorization and Jacobi.

Direct Algorithms for Large Sparse Systems of Linear Equations:

Cholesky Factorization

The Cholesky algorithm comprises a minimum degree ordering heuristic and symbolic
factorization. The implementation is based on a quotient graph model.

Genetic Algorithms

Genetic algorithms are a family of search algorithms that seek optimal solutions to problems
using an approach that parallels the principles of natural selection and evolution in nature.
There are several new experimental subroutines and functions that enable you to formulate
and implement genetic algorithm optimizations. You have the flexibility either to write your own
modules to specify the objective function and genetic operators or to use standard functions
and operators provided by IML.

New Functions and Calls

BY Group Processing for Matrices

A new function, UNIQUEBY, has been added to IML that makes it easier to retrieve and
process BY groups in a sorted matrix. You can use the SORT and SORTNDX calls to sort a
matrix, and then call the UNIQUEBY function to get a vector of indices of the first row of each
unique BY group in the input matrix. See the Language Reference section for full details.

SORT and SORTNDX Calls

Two new subroutines have been added to make sorting of matrices easier. The SORT call
sorts a matrix in place, sorting the rows by specified columns. The SORTNDX function creates
an index matrix, without rearranging the input matrix, which enables you to access the rows of
the input matrix in sorted order. The SORTNDX call will normally be faster than the SORT call,
and you can use it to create multiple indexes into the same input matrix. See the Language
Reference section for full details.

RANDSEED and RANDGEN Calls

Two new subroutines have been added to improve the efficiency of random number
generation. RANDSEED and RANDGEN use the same algorithm as the data functions
STREAMINIT and RAND, with changes to maximize performance in IML. See the Language
Reference section for full details.

New Programming Feature

Subscripting by Row or Column Names

Matrix subscripting functionality has been extended, so that you can specify a set of rows or
columns by the names given in a MATTRIB statement or assigned by a data set statement.
This is done by using a character matrix as one or both of the subscripts. IML will attempt to
match character string elements to column or row names assigned to the matrix. See the
Language Reference section for full details and examples.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Information Delivery Portal 2.0

Overview

The SAS Information Delivery Portal 2.0 includes the following new features:

● enhanced user interface

● integration with the new SAS solutions and Business Intelligence tools

● new metadata architecture

● development of new portlets

● enhancements to the information map viewer

● enhancements to the SAS Web Infrastructure Kit

● improved management of content items

● more robust management of pages and portlets

Enhancements to the User Interface

The SAS Information Delivery Portal's user interface is completely redesigned. It provides
increased usability, improved quality of presentation, and consistency with other products in
the SAS solutions and Business Intelligence suites.

From a single point in the portal, you can enter your preferences for locale, theme, e-mail,
notifications, and date and time formats. These selected preferences apply to all SAS solutions
that run in the portal.

Integration with the New SAS Solutions and Business Intelligence Tools

The SAS Information Delivery Portal can now be installed as part of a larger interoperable
suite of SAS solutions and Business Intelligence tools that are designed to meet the needs of
different audiences, with the portal serving as a single access point. A single sign-on
mechanism enables user authentication and session information to be shared among
applications. You need to log on only once in order to access all of the information that you are
authorized to see.

New Metadata Architecture

The new SAS Metadata Server provides a central point for administering portal users,
configuring system resources, and controlling access to portal content.

Development of New Portlets

The portal was developed using a new Web application architecture that eases customization
and enables new portlets to be developed and deployed quickly.

The following new portlets have been added:

● In SAS 9.1.3 Service Pack 2, you can create your own WebDAV content portlets. A
WebDAV content portlet displays the contents of an HTML fragment that is stored in the
portal's WebDAV repository.

● In SAS 9.1.3 Service Pack 3, you can create two new types of portlets: WebDAV graph
portlets and information map viewer portlets. A WebDAV graph portlet displays a graph
that uses data from the portal's WebDAV repository. An information map viewer portlet
displays data by using bookmarks that you create in the Visual Data Explorer
component.

Enhancements to the Information Map Viewer

The following enhancements were made to the information map viewer:

● The new information map viewer enables relational and OLAP data to be viewed using
graphics and tables.

● In SAS 9.1.3 Service Pack 2, extensive enhancements were made to the information
map viewing functions.
Enhancements to the SAS Web Infrastructure Kit

The following enhancements have been made to the SAS Web Infrastructure Kit, which serves
as the infrastructure for the SAS Information Delivery Portal Web application:

● In SAS 9.1.3, the SAS Web Infrastructure Kit includes the capability to run the remote
SAS Services application as a Windows service. This capability is enabled through the
use of the Java Service Wrapper from Tanuki Software, which is provided with SAS
Foundation Services.

● In SAS 9.1.3, the IBM WebSphere servlet container is now a supported platform for the
SAS Web Infrastructure Kit.

● In SAS 9.1.3 Service Pack 2, the SAS Web Infrastructure Kit includes new tools that
content administrators can use to delete shared pages and page templates from the
metadata repository.

● In SAS 9.1.3 Service Pack 2, the SAS Web Infrastructure Kit includes a new theme
called SAS Winter, which administrators can use as a basis for creating new themes. In
addition, the style sheets that are included in the themes have been modified.

Logging Off from a Portal Session

In SAS 9.1.3 Service Pack 2, if you log on to a Web server in order to access the portal, you
now have the ability to log off from a portal session.

Managing Content Items

In SAS Information Delivery Portal 2.0, you can perform the following tasks:

● e-mail links to portal content

● share content with other users in a group

● publish content to SAS publication channels

● bookmark content for future reference

● receive alert notifications for some types of content

In SAS 9.1.3 Service Pack 3, you can create, edit, and delete applications and syndication
channels. In addition, you can create new content items (including pages, portlets,
applications, syndication channels, and links) without adding them to the portal.

In SAS 9.1.3 Service Pack 3, you can delete and edit content items from the search results
page.

In SAS 9.1.3 Service Pack 3, content administrators can perform the following tasks:

● create, share, and delete page templates

● share pages, portlets, links, applications, and syndication channels

● edit and delete shared portlets, links, applications, and syndication channels

Managing Pages and Portlets

In SAS 9.1.3 Service Pack 3, the following enhancements have been added for laying out and
deleting pages:

● Pages can be laid out either in columns or in a grid (with rows and columns). In a grid
layout, individual portlets can span columns and rows. For both types of layouts, you
can specify the percentage width for each column.

● When deleting a page, you can now specify whether to also delete the portlets that are
on the page. When deleting a collection portlet, you can now specify whether to also
delete the items that are displayed in the portlet.

In SAS 9.1.3 Service Pack 3, the properties of a page now include a page rank, which
indicates the importance of the page as compared to other pages. This value can be used to
determine the order in which pages are listed in the navigation bar.

In SAS 9.1.3 Service Pack 3, the workflow for adding, creating, and editing pages and portlets
has changed:

● The Options menu now includes two entries for editing pages, one for editing page
content and one for editing page properties.

● Editable portlets now include two edit icons, one for editing portlet content and one for
 editing portlet properties.

● When editing the contents of a collection portlet, you can specify whether the portlet is to
display each item's location and description. This option is also available for the
Bookmarks portlet.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Information Map Studio 2.1

Overview of SAS Information Map Studio

SAS Information Map Studio has been updated with new functionality and usability
enhancements that make the application more flexible and easier to use.

● General user interface enhancements help not only with ease of use, but they also
enable you to perform tasks more quickly and efficiently.

● Relationship information can now be imported from the ETL process directly into your
information maps.

● Newly added information map administration features enable you to perform such tasks
as resource analysis and access control management from within SAS Information Map
Studio.
● The new Options window enables you to set preferences and select user options for
SAS Information Map Studio.
● The data item, filter, prompt, and stored process interfaces all include new or improved
functionality, including a completely redesigned prompt window interface.

Details about SAS Information Map Studio

General User Interface Enhancements

The SAS Information Map Studio 2.1 user interface includes the following new and enhanced
features that help you to work more efficiently within the application:

● new cut, copy, and paste functionality for information map items
● new find facility
● new expand and collapse functionality for tree views
● enhanced ability to move and reorder items within an information map
● new and improved icons, including icons that distinguish between relational and OLAP
information maps and icons that indicate primary and foreign keys
● new functionality to enable you to switch metadata profiles from within the application

Security
From within SAS Information Map Studio, you can now modify the access controls for an
information map and view the access controls for a stored process.

Administration Tools

A set of administration tools has been added, which enables you to perform the following tasks:

● generate a report that lists the information maps and their associated metadata
resources
● generate a report that lists the information maps that have unresolved resources, that
are unavailable for impact analysis, and that are unreadable

● make information maps available to SAS ETL Studio for impact analysis and generate a
report that lists the information maps that were successfully made available

User Options

The Options window has been added, which enables you to set the following user preferences
for your SAS Information Map Studio sessions:

● display options that enable you to specify where you want to display the SAS
Information Map Studio window and what you want to see displayed in it
● naming rules for data items
● initial relationship creation options for automatically creating relationships based on
metadata definitions
● custom properties options for displaying custom properties and for specifying a custom
properties template

Data Items

The following enhancements have been added to simplify the process of creating a data item:

● pre-populated lists of user-defined formats. You can now select one or more user-
defined formats from a list of available formats.
● default classification determination. When you insert a relational data item, the data type
of the table column now determines the default classification (category or measure) that
is assigned to the data item.

Filters
The filter definition windows have been updated to provide you with the following
enhancements:

● improved display of compound filter expressions, including the real-time rendering of

Boolean precedence groupings in the Filter expression area
● new functionality that enables you to choose from lists of date, time, and timestamp
values
● support for prompts that can accept multiple values

Prompts

The completely redesigned Prompt Properties window provides you with the following new
features:

● the ability to create a list of prompt values by running a query on one or more data items

● support for prompts whose values are dynamically generated at run time
● display of both unformatted and formatted prompt values
● support for prompts that can accept multiple values

Stored Processes

The updated Stored Processes window enables you to view the properties and parameters of
a stored process. You can also view the properties of the parameters.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.
What's New

What's New in SAS Integration Technologies 9.0, 9.1, and

9.1.2
Overview

SAS Integration Technologies includes the following enhancements.

● Performance and scalability improvements

● Use of the SAS Metadata Server to store configuration information

● Support for creating Web services

● Enhanced SAS Stored Processes

● New SAS Foundation Services

● The new SAS Web Infrastructure Kit

● Event publishing capabilities

● Messaging interface updates

● The new SAS Integration Technologies Server Administrator's Guide.

Note:

● This section describes the features of SAS Integration Technologies that are new or
enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS Integration Technologies is
supported on both OS/390 and z/OS operating systems and, throughout this document,
any reference to z/OS also applies to OS/390, unless otherwise stated.

Details
SAS Metadata Server

The SAS Metadata Server stores configuration information for servers and other SAS
Integration Technologies resources, and SAS Management Console is used to administer this
information.

Web Services

Support is provided for creating Web services that implement the XML for Analysis Version 1.1
interface to call SAS Stored Processes.

SAS Stored Processes

SAS Stored Processes can operate on a SAS Stored Process Server to produce streaming
output for use in Web applications. You can use SAS Stored Processes in the following ways.

● Use the SAS Stored Process Web Application to execute a stored process and return
the results to a browser.

● Use the StoredProcessService application programming interface (API) to invoke stored

processes from Java applications, JavaServer Pages, servlets, and custom tag sets.

● A SAS Stored Process can be invoked from the SAS Information Delivery Portal.

SAS Foundation Services

SAS Foundation Services is a new set of core infrastructure services that Java programmers
can use to write applications that are integrated with the SAS platform. The services provide
dynamic service discovery, user authentication, profile management, session context
management, metadata and content repository access, and activity logging. Extension
services for event management, information publishing, stored process execution, and
enhanced IOM client connection are also provided.

You can use the Foundation Services Manager plug-in to SAS Management Console to
configure service deployments and services, and you can use the Application Monitor plug-in
to monitor the activities and performance of applications that are enabled by SAS Foundation
Services.
Integrated Object Model (IOM) Server

The Integrated Object Model (IOM) server includes the following enhancements.

● The IOM server has been re-engineered to take advantage of the new Threaded Kernel
(TK) technology in SAS®9. This enhancement reduces response time for IOM client
applications that access Component Object Model (COM) servers and IOM Bridge
servers. The enhancement is transparent and does not require changes to server
configurations or to client programs.

● New load-balancing options in the IOM server configuration model enable more efficient
deployment of server processes across machines.

● A new Windows Object Manager enables clients to interact with multiple types of IOM
servers. The new service creates and manages objects for four "flavors" of IOM servers:
SAS Workspace Servers, SAS Metadata Servers, SAS Stored Process Servers, and
SAS OLAP Servers.

● A new Java Connection Service (part of SAS Foundation Services) enables clients to
interact with multiple types of IOM servers.

❍ This new service creates and manages objects for four "flavors" of IOM servers:
SAS Workspace Servers, SAS Metadata Servers, SAS Stored Process Servers,
and SAS OLAP Servers.

❍ This service also provides pooling and server failover scalability features and
support for load-balancing spawners.

● At this time, SAS Integration Technologies 9.0 and later does not support the use of
Object Request Brokers (ORBs) under the Common Object Request Broker Architecture
(CORBA) on server platforms, nor does it support communication with client ORBs
using the Internet Inter-ORB Protocol (IIOP).

● For COM and DCOM launched servers, all file access verifications are now performed
only with the user ID under which the server was launched. The additional level of
security checking, which was based on the client user ID, has been removed. Before
upgrading to SAS Integration Technologies 9.0 or later, the security policies at the
following sites should be reviewed.

❍ Sites that launch COM workspace servers by using the "this user" identity setting
in the DCOM configuration utility
 ❍ Sites that use COM+ pooling.

For more details, see the Windows Security section in the SAS Integration Technologies
Developer's Guide at support.sas.com/rnd/itech/doc9/dev_guide/index.
html .

Security

SAS Integration Technologies now uses the following new security features that are provided
with SAS Open Metadata Architecture.

● SAS Management Console User Manager plug-in and SAS Personal Login Manager for
registering SAS users, groups, and login information in a SAS Metadata Repository.

● SAS Management Console Authorization Manager plug-in for setting access controls in
a SAS Metadata Repository.

● The host operating environment's authentication provider to authenticate users of IOM

servers. As an alternative, you can authenticate users of SAS Metadata Servers and
OLAP servers by using an LDAP directory server or a Microsoft Active Directory server.

SAS Web Infrastructure Kit

The new SAS Web Infrastructure Kit provides an infrastructure for creating Web applications
that use portal technology by including the following items.

● SAS Java components, Web infrastructure components, and a services infrastructure

● A portal Web application shell that provides page navigation, portlet rendering, log-on
and log-off capability, metadata searching, bookmarking, personalization, and content
administration features

● Predefined portlets for content viewing and file structure navigation

● A portlet development kit, which includes an API and a set of best practices, for
developing custom portlets

● Administrative tools for deploying services, portlets, themes, global preferences, and
 additional Web applications.

The SAS Web Infrastructure Kit provides the infrastructure for the SAS Information Delivery
Portal product.

Publishing Framework

The Publishing Framework includes the following enhancements.

● Publication of packages to a channel supports subscribers who specify the webDAV

transport (in addition to queue and e-mail), and a default webDAV server can be
specified in the channel definition.

● The Publishing Framework plug-in to SAS Management Console enables channel and
subscription information to be administered on a SAS Metadata Server.

● New CALL routines use the new Event Services API to enable the publication of an
event, which provides support for dynamic event-driven processes.

● The SAS Package Reader application provides improved viewing of large tables.

● The SAS Subscription Manager application contains the following enhancements.

❍ The My Subscriptions and My Groups windows provide pop-up menus that are
activated by right-clicking a window item.

❍ You can specify name and value exclusion filters in addition to inclusion filters.

❍ Name and value pairs are listed in ascending alphabetical order.

❍ The application now recognizes the groups to which a subscriber is associated.

Messaging Interfaces

The Messaging interfaces include the following enhancements.

● The Common Messaging Interface supports the certified message delivery features of
the TIBCO Rendezvous software and does not require a field identifier for messages
from TIBCO Rendezvous. In addition, the Common Messaging Interface provides
 support for headers and libraries that are included in TIBCO Rendezvous Version 7.1 for
Windows NT, Windows 2000, Windows XP, AIX 5.1, HP Tru64 UNIX, HP-UX 11.0,
Linux, and Solaris 8.

● The WebSphere MQ (formerly named MQSeries) Messaging Interface provides support

for the following software versions.

❍ IBM WebSphere MQ Version 5.3 under Windows NT, Windows 2000, Windows
XP, and z/OS

❍ IBM WebSphere MQ Client Version 5.2 under HP-UX 11.0, Solaris 8, and AIX 5.1

❍ IBM WebSphere MQ Version 5.2 under Linux.

● Beginning with SAS Integration Technologies 9.0, the Geneva Message Queuing (GMQ)
Interface is not provided.

Documentation

Documentation for administering servers has been moved from the SAS Integration
Technologies Administrator's Guide to the new SAS Integration Technologies Server
Administrator's Guide.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New in SAS Inventory Replenishment Planning 1.2

What's New in SAS Inventory Replenishment Planning 1.2

Overview

SAS Inventory Replenishment Planning has a new version numbering scheme. SAS Inventory
Replenishment Planning 1.2 provides more features and greater functionality than SAS 9.1.2
SAS Inventory Replenishment Planning.

SAS Inventory Replenishment Planning enables you to calculate periodic-review inventory

replenishment policies using information about demand, lead time, costs, and desired service
measures.

For SAS Inventory Replenishment Planning 9, IRP existed as a collection of macros; in

Release 9.1, these have been extended to the IRP procedure, which can be used to calculate
inventory replenishment policies for both single-location and two-echelon distribution inventory
systems.

SAS Inventory Replenishment Planning 9.1.2 includes the experimental MIRP procedure for
calculating inventory control parameters in multiechelon supply chains. The MIRP procedure is
designed to help users better understand how network topologies, cost structures, and service
level requirements, among other factors, impact the inventory investment and allocation across
a supply chain.

SAS Inventory Replenishment Planning 1.2 includes

● new options for the IRP procedure to give the user more control over calculating policies
● improvements in the IRP algorithms
● production-level MIRP procedure, which replaces the experimental MIRP procedure
● the new SAS Inventory Policy Studio solution, which provides a user-friendly interface to
the IRP procedure

PROC IRP

PROC IRP can calculate four types of replenishment policies. These policies are determined
through a number of algorithms that are controlled by user-specified options. PROC IRP can
accommodate both single-location and two-echelon distribution inventory systems.

The input data set to PROC IRP specifies information about lead time, demand, and costs, as
well as options to control the policy. The output data set produced by PROC IRP gives the
policy parameters for each item. In addition, estimates of measures such as fill rate, ready
rate, and average inventory, among others, are included in the output data set.

With SAS Inventory Replenishment Planning 1.2, PROC IRP includes new and improved
algorithms. In addition, new options give the user more control over optimization of policies:

● ALGORITHM= option
● QGRID= option
● DIST= option

PROC MIRP

SAS Inventory Replenishment Planning 9.1.2 and higher includes the MIRP procedure. PROC
MIRP can calculate inventory control parameters for all stock-keeping locations in general
supply chain networks, which may consist of any combination of serial, assembly, and
distribution subnetworks. These parameters ensure that service requirements are satisfied at
minimum inventory cost for every supply chain. PROC MIRP gives users flexibility in modeling
their supply chain networks. These functionalities include:

● two replenishment policies: base-stock policy and min-max policy

● four service-level measures: ready rate, fill rate, backorder ratio, and waiting time
probability
● order constraints: minimum size, maximum size, and fixed lot size
● multiple-period replenishment planning
● backlog and lostsales options

The input data sets to PROC MIRP specify information about lead times, holding costs, service
levels, and demand of stock-keeping location in the networks, as well as information about the
structure of the networks. The output data set produced by PROC MIRP gives the inventory
control parameters, along with estimates of measures such as order quantities, backlogs, and
service levels, for each stock-keeping location and each period in a planning horizon. PROC
MIRP can also be used to evaluate the performance of users' own inventory policies.

SAS Inventory Policy Studio (Preproduction)

SAS Inventory Replenishment Planning 1.2 includes SAS Inventory Policy Studio, a new
graphical user interface designed to support the use of PROC IRP for users new to SAS or
unfamiliar with the SAS language. In addition to supporting the optimization of inventory
policies, Inventory Policy Studio:

● enables users to create "what if" scenarios using different parameters or forecasts, and
determine the impact on policies, customer service levels, and costs
● provides a graphical sensitivity analysis to assist users in quickly gauging the impact
that changes in specific parameters will have on policies, customer service levels, and
costs

After creating scenarios, and calculating, evaluating, and promoting policies, the user can
export the project table to a Microsoft Excel spreadsheet for use in other operational systems.

In Release 1.2, SAS Inventory Policy Studio does not support all of the capabilities of PROC
IRP. For example, SAS Inventory Policy Studio:

● does not support the use of backorder penalty costs as input to policy calculations
● does not support policy calculation for multiechelon systems

For information about SAS Inventory Policy Studio, see the SAS Inventory Replenishment
Planning 1.2: Inventory Policy Studio User's Guide.

Copyright © 2005 by SAS Institute Inc.,Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/IntrNet 9.0 and 9.1

Application Dispatcher
Overview

Application Dispatcher provides Application Broker and Load Manager enhancements,

additional server encodings for z/OS, a new logging feature, new options for the PROC
APPSRV statement, file upload capability, and enhanced documentation.

Note:

● This section describes the features of SAS/IntrNet: Application Dispatcher that are new
or enhanced since SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/IntrNet 9.1: Application
Dispatcher is supported in both the OS/390 and z/OS operating environments and,
throughout this document, any reference to z/OS also applies to OS/390, unless
otherwise stated.

Details

SAS/IntrNet: Application Dispatcher includes the following enhancements:

● You can now use Application Dispatcher to upload one or more files to your Application
Server.
● The Application Broker default welcome page can be replaced by a customized
welcome page.

● SAS Enterprise Guide 3.0 includes experimental support for building SAS/IntrNet:
Application Dispatcher applications. You can use SAS Enterprise Guide to generate or
modify SAS programs and to generate input HTML forms for your SAS/IntrNet
applications. See the Working with SAS/IntrNet Applications section in the SAS
Enterprise Guide product Help for more information.

● The _NOLOG_ feature enables you to create special macro symbols that can be sent to
the Application Server without publishing the macro values in the APPSRV log.
● SAS/IntrNet: Application Dispatcher now supports the following additional parameters
for starting the Load Manager:
 -maxreq=minutes
specifies the maximum time it should take for the Application Server to send a
BUSY state after the Application Server is allocated to the Application Broker.

-maxrun=minutes
specifies the expected maximum job run-time in minutes before an Application
Server is declared as hung.

-maxstart=minutes
specifies the maximum time that it should take an Application Server to start.

-nokill
specifies not to kill a pool server that is marked as hung.

-workdir=directory
enables you to specify the current working directory as a start parameter for the
Load Manager.

● You can obtain an Application Server activity report by using the Application Broker and
running the LOADCURRENT program.

● The documentation now includes a sample Web application that demonstrates some of
the features of Application Dispatcher sessions. The sample application is an online
library. Users can login, select one or more items to check out of the library, and request
by e-mail that the selected items be delivered. The sample code shows how to create a
session and then create, modify, and view macro variables and data sets in that session.
● Two additional versions of the Application Broker have been developed for heavily
loaded systems where performance is critical. The two new modules are broker.dll
(ISAPI Windows) and broker.so (GWAPI z/OS).
● For z/OS, the SAS 9 Application Broker requires that the IBM Web maintenance patch,
PQ47248, be installed if you intend to use a Web server codepage (FSCP) other than
ibm-1047.
● SAS/IntrNet: Application Broker on z/OS now supports Windows server encodings in
addition to the previously supported ISO-8859 encodings. New encodings include

❍ wlatin1 (Western Europe): This value is the default in all cases except when the
Web server is using IBM-870 or IBM-1025 encoding.
❍ wlatin2 (Eastern Europe): This value is the default when the Web server is
using IBM-870 encoding.
❍ wcyrillic (Cyrillic): This value is the default when the Web server is using IBM-
1025 encoding.
 The z/OS Application Broker also supports a new ISO-8859 encoding:

❍ ISO-8859-15 (Latin9): This encoding is recommended only if your Web server

and SAS System are using any of the IBM-114x encodings.

SAS/IntrNet: Application Broker on z/OS now supports the following additional Web
server fscp encodings:

❍ EBCDIC1140 (North America)

❍ EBCDIC1141 (Austria/Germany)
❍ EBCDIC1142 (Denmark/Norway)
❍ EBCDIC1143 (Finland/Sweden)
❍ EBCDIC1144 (Italy)
❍ EBCDIC1145 (Spain)
❍ EBCDIC1146 (United Kingdom)
❍ EBCDIC1147 (France)
❍ EBCDIC1148 (International)

● The _DEBUG option now supports a list of case-insensitive keywords that can be
entered to indicate which debug values to enable.
● The ConnectionError directive enables users to specify the message to be displayed
when there is an Application Server connection error.
● The SHAREPOLL= and NOSHAREPOLL options enable the PROC APPSRV statement
to control the period of SAS/SHARE libref polling and to disable polling of the SAS/
SHARE server librefs, respectively.
● Load Manager log filename directives have been added to enable the rollover of Load
Manager log files. Special codes inserted into the log filename specify the format and
frequency for creating log files.
● Documentation for the BrokerPassword directive was added. The directive enables
users to specify a password in order to protect the Application Broker administration
interface.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/IntrNet 9.0 and 9.1

htmSQL
Overview

htmSQL for SAS/IntrNet 9.0 and 9.1 includes a new administration option and more flexibility
for coding directives.

Note:

This section describes the features of SAS/IntrNet: htmSQL that are new or enhanced since
SAS 8.2.

Details

● The new SET configuration option enables administrators to set default values for name
and value pairs.

● Parameter values for htmSQL directives can now be delimited with either double or
single quotation marks.

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Management Console 9.1.2 and 9.1.3

Overview

SAS Management Console is a Java application that provides a single point of control for
managing resources that are used throughout the SAS Intelligence Platform. Instead of using a
separate administrative interface for each application in your computing environment, you can
use the single interface in SAS Management Console to perform the administrative tasks that
are required for creating and maintaining an integrated environment across multiple platforms.
SAS Management Console enables you to manage the following resources:

● server definitions

● library definitions

● user definitions

● resource access controls

● metadata repositories

● SAS licenses

● job schedules

● XML maps

SAS Management Console works by creating and maintaining metadata definitions for each
computing resource or control. These metadata definitions are stored in a repository on a SAS
Metadata Server, which makes them available for use by other applications. For more
information, see the SAS 9.1.2 Management Console: User's Guide.

The 9.1.3 release of SAS Management Console provides support for the SAS Scalable
Performance Data (SPD) Server, enables you to import data tables into a library, and updates
resource templates.

Details
SAS Management Console now contains the following enhancements:

● Support is added for the SAS Scalable Performance Data Server by allowing you to
define SAS SPD Server libraries, servers, and schemas. You must run the Upgrade
Metadata function to add support for the SAS SPD Server.
● You can import data tables into SAS Management Console libraries by using the Import
Tables wizard. The wizard lets you register existing SAS data sets in the metadata
repository.
● Resource templates for server, library, and schema definitions have been changed. Use
the Upgrade Metadata function to apply the new resource templates to your metadata
server. If you are upgrading a metadata server from SAS 9.1 to SAS 9.1.3, the resource
template changes in SAS 9.1.2 are applied before the SAS 9.1.3 changes are applied.
● Flows can be scheduled using operating system scheduling services. You define an
operating system scheduling server in SAS Management Console, then use the
Schedule Manager plug-in to submit flows to the server. The server uses operating
system commands to schedule and run the flows.
● Resource templates have been added for the SAS Grid Server and the Grid Monitoring
Server. These servers support a grid computing configuration.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS 9.0 and 9.1 National Language Support

(NLS)
Overview

● All information that is related to NLS has been consolidated into a single document for
your convenience.

● The LOCALE= option supports a new set of locale values in the form of Portable
Operating System Interface (POSIX) names.

● The LOCALE= option supports new values that identify unique language and country
combinations.

● The LIBNAME statement for Base SAS supports three new options for NLS:
CVPBYTES=, CVPENGINE=, and CVPMULTIPLIER=.

● The LIBNAME statement for the XML engine supports three new options for NLS:
ODSCHARSET=, ODSTRANTAB=, and XMLENCODING=.

● The LIBNAME statement in SAS/SHARE supports the RENCODING= option for NLS.

● Numerous NLS formats, informats, and functions are new. These new language
elements are in the following categories: Bi-directional text handling, Date/Time,
Monetary, and Unicode.

Note: z/OS is the successor to the OS/390 operating system. SAS 9.1 is supported on both
OS/390 and z/OS operating systems and, throughout this document, any reference to z/OS
also applies to OS/390, unless otherwise stated.

Details

New Document Consolidates Information about NLS

SAS 9.1 introduces the SAS National Language Support (NLS): User's Guide, which
consolidates all information about NLS that was previously contained in multiple SAS
documents. The SAS National Language Support (NLS): User's Guide provides
comprehensive conceptual information and detailed syntax for all SAS language elements that
contain NLS properties.

Expanded Values for the LOCALE= System Option

● Locale can be specified by using Portable Operating System Interface (POSIX) naming
standards. For example, the en_US value is the POSIX equivalent for the SAS value
English_UnitedStates.

● Previous releases of SAS software specified some LOCALE= values in the form of
language. The LOCALE= option supports new values that identify unique language and
country combinations that are specified in the form language_country. Some single
LOCALE= values have been replaced by more granular values. Some new values have
been added, and some values have been deleted. Here is a summary of the changes to
LOCALE= values:

Arabic

The single LOCALE= value for Arabic has been deleted. The following new
values have been added: Arabic_Algeria, Arabic_Bahrain, Arabic_Egypt,
Arabic_Jordan, Arabic_Kuwait, Arabic_Lebanon, Arabic_Morocco, Arabic_Oman,
Arabic_Qatar, Arabic_SaudiArabia, Arabic_Tunisia, and
Arabic_UnitedArabEmirates.

Chinese

The single LOCALE= value for Chinese has been deleted. The values
Chinese_Simplified and Chinese_Traditional have also been deleted.

Dutch

The single LOCALE= value for Dutch has been deleted. The following new values
have been added: Dutch_Belgium and Dutch_Netherlands.

English

The single LOCALE= value for English has been deleted. The following new
values have been added: English_HongKong, English_India, and
English_Singapore. The English_Britain value has been changed to
English_UnitedKingdom.
 Estonian_Estonia

The LOCALE= value for Estonian_Estonia is new.

French

The single LOCALE= value for French has been deleted. A new value,
French_Luxembourg, has been added.

German

The single LOCALE= value for German has been deleted. The following new
values have been added: German_Liechtenstein and German_Luxembourg.

Spanish

The LOCALE= values for Spain and Spanish_LatinAmerica have been deleted.
The single LOCALE= value for Spanish_LatinAmerica has been replaced by the
following new values: Spanish_Argentina, Spanish_Bolivia, Spanish_Chile,
Spanish_Columbia, Spanish_CostaRica, Spanish_DominicanRepublic,
Spanish_Ecuador, Spanish_ElSalvador, Spanish_Guatemala,
Spanish_Honduras, Spanish_Mexico, Spanish_Nicaragua, Spanish_Panama,
Spanish_Paraguay, Spanish_Peru, Spanish_PuertoRico, Spanish_UnitedStates,
Spanish_Uruguay, and Spanish_Venezuela.

For a comprehensive list, see Values for the LOCALE= System Option.

New Options in LIBNAME Statements for NLS

● The LIBNAME statement in Base SAS supports the following new options for NLS:

CVPBYTES=, CVPENGINE=, and CVPMULTIPLIER= Options

specify the attributes for character variables that are needed in order to process
(or transcode) a SAS file.

● The LIBNAME statement for the XML engine supports the following new options for NLS:

ODSCHARSET= Option
 specifies the character set to be generated in the META declaration for the output.

ODSTRANTAB = Option

specifies the translation table to use when transcoding an XML document for an
output file.

XMLENCODING= Option

specifies the encoding to use when reading, writing, copying, or saving an

external file.

● The LIBNAME statement in SAS/SHARE supports the following new option for NLS:

RENCODING= Option

specifies that the ASCII-based or EBCDIC-based encoding be used when

transcoding data for a SAS/SHARE server session that is using an ASCIIANY or
an EBCDICANY session encoding.

Formats for NLS

The following formats for NLS are new:

$CPTDWw. Format

writes a character string in Hebrew text that is encoded in IBM-PC (cp862) to

Windows Hebrew encoding (cp1255).

$CPTWDw. Format

writes a character string that is encoded in Windows (cp1255) to Hebrew DOS

(cp862) encoding.

HDATEw. Format

writes date values in the form yyyy mmmmm dd where yyyy is the year, mmmmm
represents the month's name in Hebrew, and dd is the day of month.

HEBDATEw. Format
 writes date values according to the Jewish calendar.

$LOGVSw. Format

writes a character string that is in left-to-right logical order to visual order.

$LOGVSRw. Format

writes a character string that is in right-to-left logical order to visual order.

NLDATEw. Format

converts a SAS date value to the date value of the specified locale, and then writes
the value in the format of the date value.

NLDATEMNw. Format

converts a SAS date value to the date value of the specified locale, and then writes
the date value in the format of the name of the month.

NLDATEWw. Format

converts a SAS date value to the date value of the specified locale, and then writes
the date value in the format of the date and the day of the week.

NLDATEWNw. Format

converts the SAS date value to the date value of the specified locale, and then
writes the date value in the format of the name of the day of the week.

NLDATMw. Format

converts a SAS datetime value to the datetime value of the specified locale, and
then writes the value in the format of the datetime.

NLDATMAPw. Format

converts a SAS datetime value to the datetime value of the specified locale, and
then writes the value in the format of the datetime with a.m. or p.m.
NLDATMTMw. Format

converts the time portion of a SAS datetime value to the time-of-day value of the
specified locale, and then writes the value in the format of the time of the day.

NLDATMWw. Format

converts a SAS date value to a datetime value of the specified locale, and then
writes the value in the format of day of the week and the datetime.

NLMNYw.d Format

writes the monetary format of the local expression in the specified locale using local
currency.

NLMNYIw.d Format

writes the monetary format of the international expression in the specified locale.

NLNUMw.d Format

writes the numeric format of the local expression in the specified locale.

NLNUMIw.d Format

writes the numeric format of the international expression in the specified locale.

NLPCTw.d Format

writes percentage data of the local expression in the specified locale.

NLPCTIw.d Format

writes percentage data of the international expression in the specified locale.

NLTIMAPw. Format

converts a SAS time value to the time value of a specified locale, and then writes
the value in the format of the time with a.m. or p.m.

NLTIMEw. Format
 converts a SAS time value to the time value of the specified locale, and then writes
the value in the format of the time.

$UCS2Bw. Format

writes a character string in big-endian, 16-bit, universal character set code in 2

octets (UCS2), Unicode encoding.

$UCS2BEw. Format

writes a big-endian, 16-bit, universal character set code in 2 octets (UCS2),

character string in the encoding of the current SAS session.

$UCS2Lw. Format

writes data in little-endian, 16-bit, universal character set code in 2 octets (UCS2),
Unicode encoding.

$UCS2LEw. Format

writes a character string that is encoded in little-endian, 16-bit, universal character

set code in 2 octets (UCS2), in the encoding of the current SAS session.

$UCS2Xw. Format

writes a character string in native-endian, 16-bit, universal character set code in 2

octets (UCS2), Unicode encoding.

$UCS2XEw. Format

writes a native-endian, universal character set code in 2 octets (UCS2), character

string in the encoding of the current SAS session.

$UCS4Bw. Format

writes a character string in big-endian, 32-bit, universal character set code in 4

octets (UCS4), Unicode encoding.

$UCS4BEw. Format
 writes a big-endian, 32-bit, universal character set code in 4 octets (UCS4),
character string in the encoding of the current SAS session.

$UCS4Lw. Format

writes a character string in little-endian, 32-bit, universal character set code in 4

octets (UCS4), Unicode encoding.

$UCS4LEw. Format

writes a little-endian, 32-bit, universal character set code in 4 octets (UCS4),

character string in the encoding of the current SAS session.

$UCS4Xw. Format

writes a character string in native-endian, 32-bit, universal character set code in 4

octets (UCS4), Unicode encoding.

$UCS4XEw. Format

writes a native-endian, 32-bit, universal character set code in 4 octets (UCS4),

character string in the encoding of the current SAS session.

$UESCw. Format

writes a character string that is encoded in the current SAS session in Unicode
escape (UESC) representation.

$UESCEw. Format

writes a Unicode escape (UESC) representation character string in the encoding of

the current SAS session.

$UNCRw. Format

writes a character string that is encoded in the current SAS session in numeric
character representation (NCR).

$UNCREw. Format

writes the numeric character representation (NCR) character string in the encoding
 of the current SAS session.

$UPARENw. Format

writes a character string that is encoded in the current SAS session in Unicode
parenthesis (UPAREN) representation.

$UPARENEw. Format

writes a Unicode parenthesis (UPAREN) character string in the encoding of the

current SAS session.

$UTF8Xw. Format

writes a character string in universal transformation format (UTF-8) encoding.

$VSLOGw. Format

writes a character string that is in visual order to left-to-right logical order.

$VSLOGRw. Format

writes a character string that is in visual order to right-to-left logical order.

WEEKUw. Format

writes a week number in decimal format by using the U algorithm.

WEEKVw. Format

writes a week number in decimal format by using the V algorithm.

WEEKWw. Format

writes a week number in decimal format by using the W algorithm.

Informats for NLS

The following informats for NLS are new:

$CPTDWw. Informat

reads a character string that is encoded in Hebrew DOS (cp862) and then converts
the character string to Windows (cp1255) encoding.

$CPTWDw. Informat

reads a character string that is encoded in Windows (cp1255) and then converts
the character string to Hebrew DOS (cp862) encoding.

$LOGVSw. Informat

reads a character string that is in left-to-right logical order and then converts the
character string to visual order.

$LOGVSRw. Informat

reads a character string that is in right-to-left logical order and then converts the
character string to visual order.

NLMNYw.d Informat

reads monetary data in the specified locale for the local expression, and then
converts the data to a numeric value.

NLMNYIw.d Informat

reads monetary data in the specified locale for the international expression, and
then converts the data to a numeric value.

NLNUMw.d Informat

reads numeric data in the specified locale for local expressions, and then converts
the data to a numeric value.

NLNUMIw.d Informat

reads numeric data in the specified locale for international expressions, and then
converts the data to a numeric value.
NLPCTw.d Informat

reads percentage data in the specified locale for local expressions, and then
converts the data to a numeric value.

NLPCTIw.d Informat

reads percentage data in the specified locale for international expressions, and
then converts the data to a numeric value.

$UCS2Bw. Informat

reads a character string that is encoded in big-endian, 16-bit, universal character

set code in 2 octets (UCS2), Unicode encoding, and then converts the character
string to the encoding of the current SAS session.

$UCS2BEw. Informat

reads a character string that is in the encoding of the current SAS session and then
converts the character string to big-endian, 16-bit, universal character set code in 2
octets (UCS2), Unicode encoding.

$UCS2Lw. Informat

reads a character string that is encoded in little-endian, 16-bit, universal character

set code in 2 octets (UCS2), Unicode encoding, and then converts the character
string to the encoding of the current SAS session.

$UCS2LEw. Informat

reads a character string that is in the encoding of the current SAS session and then
converts the character string to little-endian, 16-bit, universal character set code in
2 octets (UCS2), Unicode encoding.

$UCS2Xw. Informat

reads a character string that is encoded in 16-bit, universal character set code in 2
octets (UCS2), Unicode encoding, and then converts the character string to the
encoding of the current SAS session.
$UCS2XEw. Informat

reads a character string that is in the encoding of the current SAS session and then
converts the character string to 16-bit, universal character set code in 2 octets
(UCS2), Unicode encoding.

$UCS4Bw. Informat

reads a character string that is encoded in big-endian, 32-bit, universal character

set code in 4 octets (UCS4), Unicode encoding, and then converts the character
string to the encoding of the current SAS session.

$UCS4Lw. Informat

reads a character string that is encoded in little-endian, 32-bit, universal character

set code in 4 octets (UCS4), Unicode encoding, and then converts the character
string to the encoding of the current SAS session.

$UCS4Xw. Informat

reads a character string that is encoded in 32-bit, universal character set code in 4
octets (UCS4), Unicode encoding, and then converts the character string to the
encoding of the current SAS session.

$UCS4XEw. Informat

reads a character string that is in the encoding of the current SAS session and then
converts the character string to 32-bit, universal character set code in 4 octets
(UCS4), Unicode encoding.

$UESCw. Informat

reads a character string that is encoded in Unicode escape (UESC) representation,

and then converts the character string to the encoding of the current SAS session.

$UESCEw. Informat

reads a character string that is encoded in the current SAS session, and then
converts the character string to Unicode escape (UESC) representation.

$UNCRw. Informat
 reads the numeric character representation (NCR) character string, and then
converts the character string to the encoding of the current SAS session.

$UNCREw. Informat

reads a character string in the encoding of the current SAS session, and then
converts the character string to session-encoded numeric character representation
(NCR).

$UPARENw. Informat

reads a character string that is encoded in Unicode parenthesis (UPAREN)

representation, and then converts the character string to the encoding of the
current SAS session.

$UPARENEw. Informat

reads a character string that is encoded in the current SAS session, and then
converts the character string to the encoding of the Unicode parenthesis
(UPAREN) representation.

$UPARENPw. Informat

reads a character string that is encoded in Unicode parenthesis (UPAREN)

representation, and then converts the character string to the encoding of the
current SAS session with national characters remaining in the encoding of the
UPAREN representation.

$UTF8Xw. Informat

reads a character string that is encoded in Unicode transformation format (UTF-8),

and then converts the character string to the encoding of the current SAS session.

$VSLOGw. Informat

reads a character string that is in visual order and then converts the character
string to left-to-right logical order.

$VSLOGRw. Informat

reads a character string that is in visual order and then converts the character
 string to right-to-left logical order.

WEEKUw. Informat

reads the format of the number-of-week value within the year and returns a SAS
date value by using the U algorithm.

WEEKVw. Informat

reads the format of the number-of-week value within the year and returns a SAS
date value using the V algorithm.

WEEKWw. Informat

reads the format of the number-of-week value within the year and returns a SAS
date value using the W algorithm.

Functions for NLS

The following functions for NLS are new:

NLDATE Function

converts the SAS date value to the date value of the specified locale by using the
date-format modifiers.

NLDATM Function

converts the SAS datetime values to the time value of the specified locale using the
datetime-format modifiers.

NLTIME Function

converts the SAS time or datetime value to the time value of the specified locale
using the time-format modifiers.

TRANTAB Function

transcodes a data string by using a translation table.

 VARTRANSCODE Function

returns the transcode attribute of a SAS data set variable.

VTRANSCODE Function

returns a value that indicates whether transcoding is enabled for the specified
character variable.

VTRANSCODEX Function

returns a value that indicates whether transcoding is enabled for the specified
argument.

WEEK Function

returns the week-number value.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in the SAS OLAP Server 9.1 and 9.1.3

Overview

The SAS OLAP Server enables users to develop and deploy scalable Online Analytical
Processing (OLAP) applications. In addition, automated data loading and cube building are
available through the use of a new administration interface called SAS OLAP Cube Studio,
which was developed using Java technology.

OLAP queries are performed using the Multidimensional Expressions (MDX) query language in
client applications that are connected to the SAS OLAP Server by using the following:

● the SQL Pass-Through Facility for OLAP, which is designed to process MDX queries
within the PROC SQL environment

● open access technologies such as OLE DB for OLAP, ADO MD, and Java

Note: This section describes the features of the SAS OLAP Server that are new or enhanced
since SAS 8.2.

Details

SAS OLAP Server includes the following enhancements:

● The start-up file generator has been removed from the SAS OLAP Server Monitor plug-
in for SAS Management Console. SAS OLAP Servers are now automatically installed as
Windows services; server start-up options are set by a .ini file that is installed by the
SAS Deployment wizard.

● The Define Distinct Count function enables you to store NUNIQUE (Distinct Count)
statistics as measures with a SAS OLAP cube. You can add or delete a distinct count
measure either with PROC OLAP or in the Cube Designer wizard, within SAS OLAP
Cube Studio. You can add or delete a Distinct Count measure. You can also modify the
name, caption, format, units, and description of the measure.

● The Export Cube and Import Cube functions enable you to copy cube metadata from a
source repository to a target repository, and if needed, to another server. The Export
Cube function enables you to extract a cube's metadata from the source repository and
 save it in a file that you specify. All information about a cube, including its dimensions,
hierarchies, levels, measures, notes, properties, calculated measures, aggregations,
and security settings, will be extracted. The Import Cube function then enables you to
save the cube metadata to another metadata repository on another metadata server.

● The Synchronize Levels function enables you to synchronize a cube when the input
table for an existing cube has encountered a column name change. This function finds
the name differences between the cube and its input table and changes the hierarchy
level names to match the input table column names.

● When creating a cube dimension in SAS OLAP Cube Studio's Cube Designer wizard, a
hierarchy for a dimension will automatically be created when no hierarchy has been
explicitly defined and you click the Finish button in this window. This default hierarchy
includes all levels that were specified for the current dimension and the order they were
listed in for the dimension.

● The documentation for SAS OLAP Server has been expanded into three titles: SAS
OLAP Server User's Guide, SAS OLAP Server Administrator's Guide, and SAS
OLAP Server MDX Guide.

● There are two new tools for data loading and cube building:

❍ The OLAP procedure, in addition to cube building, includes options for handling
ragged hierarchies, defining global calculated members and named sets,
assigning properties to levels, and optimizing cube creation and query
performance. It also supports multiple hierarchies and drill-through tables.

❍ SAS OLAP Cube Studio is an alternative Java interface to the OLAP procedure.
This interface is also integrated with SAS ETL Studio.

● Server performance is recorded and analyzed by using the Application Response

Measurement (ARM) system.

● The new multi-threaded data storage and server functionality provide faster cube
performance. The data can be stored in a multidimensional form (MOLAP) or in a form
that includes existing aggregations from presummarized data sources.

● The metadata structure is improved, and metadata is stored with the cube.

● Caching and logging can be enabled or disabled.

● Support for ad hoc calculations and time dimensions is improved.

 ● An SQL Pass-Through Facility for OLAP is available in SAS for use in querying cubes.

● The Calculated Members Plugin provides a point-and-click interface that enables you to
add new measures or modify existing measures for the selected cube.

● Aggregations can be added to or deleted from existing cubes. In addition, further

enhancements for aggregation tuning have been made.

The AGGREGATION statement and SAS OLAP Cube Studio's Manual tuning
function have been enhanced for use with cubes that employ aggregated data from
other tables or for use with cubes that have no NWAY aggregation.

The Advanced Aggregation Tuning Plugin provides a point-and-click interface that

enables you to create and add aggregations to the list of existing aggregations that
might already be defined for the cube.
● New options have been added to the PROC OLAP statement:

COMPACT_NWAY

when building a cube from a star schema, this option enables additional
summarizations during the cube build that can decrease the size of the NWAY
aggregation.

IGNORE_MISSING_DIMKEYS=TERSE | VERBOSE

when building a cube from a star schema, this option enables the continuation of
the build when the fact table is found to contain keys that are not present in any of
the dimension tables. The log receives information about the number and location
of the missing keys.

For further information about these new options, see the SAS OLAP Server User's
Guide.

Note: Version 8 of the SAS OLAP Server can be used with SAS 9. For help, see "Using V8
SAS OLAP Server" in SAS Help and Documentation. See also Overview of Transition Issues.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Open Metadata Architecture 9.0, 9.1,

9.1.2, and 9.1.3

Overview

SAS®9 enhances your ability to store, manage, and use metadata by implementing SAS Open
Metadata Architecture. SAS Open Metadata Architecture 9.0 (and later) provides a framework
for creating and managing metadata and applications that use metadata. This enables
separate applications to share metadata. The metadata architecture also saves development
effort because applications do not have to implement their own metadata facilities.

Note:

● This section describes the features of SAS Open Metadata Architecture that are new or
enhanced since 9.0.

● z/OS is the successor to the OS/390 operating system. SAS Open Metadata
Architecture 9.0 (and later) is supported on both OS/390 and z/OS operating systems
and, throughout this document, any reference to z/OS also applies to OS/390, unless
otherwise stated.

Details

Components of SAS®9 Open Metadata Architecture

SAS®9 Open Metadata Architecture enables you to set up a metadata server, create metadata
repositories, and write applications (clients) that store, use, or manage the metadata. The
following components are part of the framework:

● SAS Metadata Repository is a collection of related metadata objects that describe

enterprise data resources.

● SAS Metadata Server is a multi-user server that makes metadata available from one or
more SAS metadata repositories. The metadata server is supported by SAS Integration
Technologies, which is required in order to use SAS Open Metadata Architecture.
Documentation for the SAS Metadata Server and repositories is available from the
 online SAS Customer Support Center at support.sas.com/rnd/eai/openmeta.

● The SAS Open Metadata Interface and SAS Java Metadata Interface are application
programming interfaces (APIs) for interacting with the SAS Metadata Server. SAS 9.0
(and later) clients use these APIs to deliver metadata services. Documentation for the
SAS Open Metadata Interface and the SAS Java Metadata Interface is available in SAS
Help and Documentation and SAS OnlineDoc.

● The SAS Metadata Model comprises many metadata types that define the information
that you store in metadata repositories for a variety of enterprise needs, such as storing
LIBNAME statements, DBMS schemas, data mining, OLAP information,
transformations, servers, and much more. Documentation for the SAS Metadata Model
is available in SAS Help and Documentation and SAS OnlineDoc.

● The SAS Open Metadata Architecture Authorization Facility is a subsystem of the

metadata server that returns authorization decisions based on access controls that are
in the metadata. The facility is used to control access to metadata objects on the
metadata server. It can also be used to control access and the actions that can be
performed on resources that the metadata objects describe. Documentation for the
authorization facility is included with the SAS Metadata Server documentation at
support.sas.com/rnd/eai/openmeta.

Clients of SAS®9 Open Metadata Architecture

SAS®9 ships multiple SAS Open Metadata Architecture clients that use the metadata model
and API. These clients facilitate managing and using metadata repositories and accessing
metadata by using the metadata server. The following software components are clients of the
SAS Open Metadata Architecture:

● SAS Management Console, which is a new standardized interface for managing various
SAS resources, including metadata. SAS Management Console also uses metadata to
manage those resources. The Metadata Manager plug-in facilitates tasks such
as creating and managing repositories and controlling the metadata server. The User
Manager plug-in enables you to register users and groups on the metadata server and
manage their registrations. The Authorization Manager plug-in enables you to define
access controls to SAS metadata repositories and to individual metadata within a
repository.

● A SAS language metadata interface that enables you to manage metadata from within
SAS. This interface includes the following elements:

❍ the METAOPERATE and METADATA procedures, which enable you to control

 the metadata server and issue SAS Open Metadata Interface method calls from
within SAS

❍ the METABROWSE and METAFIND commands (new in SAS 9.1), which enable
you to browse and search for specific metadata in SAS metadata repositories

❍ the METACON command (new in SAS 9.1), which enables you to manage server
connections

❍ portable SAS system options, which enable you to specify default server
connection parameters and repository settings for your SAS session

❍ a family of SAS metadata DATA step functions (new in SAS 9.1), which enable
you to get, set, and update the properties of SAS metadata objects in a DATA
step program

❍ the metadata LIBNAME engine that, along with your SAS engine, stores and
builds LIBNAME statements using information in SAS metadata repositories.

Other SAS products and solutions that are clients of the SAS Open Metadata Architecture
include SAS ETL Studio, SAS Information Delivery Portal, SAS Information Map Studio, SAS
OLAP Cube Studio, SAS Web Report Studio, and SAS Marketing Automation.

Documentation for SAS Open Metadata Architecture clients is available in SAS Help and
Documentation and SAS OnlineDoc.

Enhanced User Support

Beginning with SAS 9.1, the SAS Metadata Server supports an unrestricted user,
administrative users, and trusted users. These special users can perform tasks that cannot be
performed by other users. For more information, see the SAS Metadata Server documentation
at support.sas.com/rnd/eai/openmeta.

Support for ARM Logging

Beginning with SAS 9.1, the SAS Metadata Server supports ARM logging. Application
Response Measurement (ARM) is a standard for managing distributed application
performance. The ARM_OMA subsystem records transaction start-and-stop times that can be
used to develop timing statistics for server performance testing. ARM_OMA logging (which is
optional) is invoked by passing ARM-related system options in the command that starts the
metadata server. For more information, see the SAS Metadata Server documentation at
support.sas.com/rnd/eai/openmeta.

Repository Auditing

Beginning with SAS 9.1, the SAS Metadata Server gives you the option to save information
about changes to a repository in a set of audit files. The information in the audit files can be
used to restore the metadata in a repository to a previous state. Auditing is performed on
individual repositories and is invoked in SAS Management Console after a repository is
created. For more information, see the SAS Metadata Server documentation at support.sas.
com/rnd/eai/openmeta.

Importing and Exporting Metadata

Beginning with SAS 9.1, wizards were added to SAS Management Console that enable
metadata administrators to import and export metadata to and from other metadata models. By
default, the wizards use the Common Warehouse Metamodel (CWM) format. In addition, you
can add import and export formats by installing the Model Bridge software from Meta
Integration. For more information, see SAS Help and Documentation and SAS OnlineDoc.

Repositories Created for External DBMS

Beginning with SAS 9.1, when the appropriate SAS/ACCESS software is installed,
administrators can create repositories in Oracle or in DB2 from IBM by specifying an engine
and library and engine connection options when a repository is created. For more information,
see the SAS Metadata Server documentation at support.sas.com/rnd/eai/openmeta.

New Macros

The following macros for use by metadata administrators are new in SAS 9.1 or 9.1.2:

%OMABAKUP autocall macro (9.1)

automates the metadata server backup process.

%OMAOPTMZ autocall macro (9.1)

optimizes the memory footprint of a metadata repository by eliminating unnecessary
indexes, storing long character variables as varying length strings, and removing
duplicate copies of strings in repository data sets.

%MDUIMPC and %MDUIMPL autocall macros (9.1)

import user and group information from enterprise data sources to the metadata server.
Before you can use these macros, you must extract the necessary user and group
 information from existing stores.
%OMAPORT autocall macro (9.1.2)
ports a SAS Metadata Repository that is created in one host environment to another
host environment.

These macros are described in more detail in the SAS Metadata Server documentation at
support.sas.com/rnd/eai/openmeta.

New Documentation

The SAS 9.1 Open Metadata Architecture: Best Practices Guide provides information to
assist you in planning your metadata environment and optimize server performance. This
guide is available from the online SAS Customer Support Center at support.sas.com/rnd/eai/
openmeta.

Increased Security for SASUSERS and PUBLIC Groups

Beginning with SAS 9.1.2, the SAS Open Metadata Architecture Authorization Facility no
longer allows anyone, including the unrestricted user, to modify or delete the SASUSERS and
PUBLIC groups. For more information, see the SAS Metadata Server documentation at
support.sas.com/rnd/eai/openmeta.

Sample User Import Applications

Beginning with SAS 9.1.2, two sample applications are provided that metadata administrators
can modify to extract user and group information from enterprise data sources and create
identity metadata in a SAS Metadata Repository. The application importad.sas extracts user
information from Microsoft Active Directory domain controller files. The application importpw.
sas extracts user information from UNIX /etc/passwd files. After the information is extracted,
the applications use the %MDUIMPC and %MDUIMPL macros to read the information into the
appropriate format and load it into a SAS Metadata Repository. These applications are
available in the SAS Sample Library. For more information, see the SAS Metadata Server
documentation at support.sas.com/rnd/eai/openmeta.

Workunit Journaling
Beginning with SAS 9.1.3, the SAS Metadata Server supports new omaconfig.xml options that
enable administrators to configure the metadata server to write metadata updates to a high-
speed workunit journal file prior to updating repositories on disk. Workunit journaling improves
performance on multiprocessor metadata servers and also improves the metadata server's
recovery ability by maintaining a copy of all uncommitted updates. For information about the
workunit journaling options, see "Understanding Server Configuration Options" in the SAS
Open Metadata Architecture: Best Practices Guide at support.sas.com/rnd/eai/openmeta.

Expanded Search Capability

Beginning with SAS 9.1.3, the <XMLSelect> search element in the SAS Open Metadata
Interface supports the comparison operator =: (an equal sign with a colon modifier). This
operator compares only the specified prefix in a character string. For more information, see the
section "Filtering a GetMetadataObjects Request" under "Querying All Metadata of a Specified
Type" in the SAS Open Metadata Interface: User's Guide.

Ability to Reclaim Unused Disk Space

Beginning with SAS 9.1.3 Service Pack 2, the metadata server backup macro, %OMABAKUP,
supports a REORG option that reclaims unused disk space from SAS metadata repositories.
For more information, see "Using %OMABAKUP to Reclaim Unused Disk Space" in "Backing
Up the Metadata Server" in the SAS 9.1.3 Metadata Server: Setup and Administration Guide.
The %OMABAKUP macro also converts special characters that are not supported in directory
names by the host environment to underscores. For more information, see "How %
OMABAKUP Works" in "Backing Up the Metadata Server" in the SAS 9.1.3 Metadata Server:
Setup and Administration Guide.

Additional Server Startup Options and New Best Practices

Recommendation for MAXACTIVETHREADS
Beginning with SAS 9.1.3 Service Pack 3, two additional objectserverparms options can be set
in the SAS Metadata Server start command to improve server performance. The options,
THREADSMIN (TMIN) and THREADSMAX (TMAX), control the minimum and maximum
number of threads that are allowed in the SAS Metadata Server's thread pool. A thread is a
channel that is available for handling user requests. A thread pool defines the number of
threads that are available to a server, regardless of the number of user requests that are
made. When these options are set, the number of available threads is not allowed to fall below
TMIN or to exceed TMAX.

The optimum values for TMIN and TMAX are dependent on the setting of the
MAXACTIVETHREADS metadata server configuration option. MAXACTIVETHREADS, which
is set in the metadata server's omaconfig.xml file, specifies the maximum number of threads
that are allowed to run concurrently on the metadata server. There are new best-practices
recommendations for MAXACTIVETHREADS with SAS 9.1.3 Service Pack 3 as well. For
information about the new recommendations, and to better understand how the metadata
server uses threads, see "Setting System Configuration Options" in the SAS Open Metadata
Architecture: Best Practices Guide.

The SAS Configuration Wizard does not set TMIN and TMAX for you. To take advantage of
the performance gains that are available with these options, edit the metadata server start
command file and add the options manually. If you performed a planned SAS installation, this
file is located in a MetadataServer .bat or script file in C:\SAS\name_of_plan.xml\Lev1
\SASMain\MetadataServer. For information about the content of the metadata server start
command and where TMIN and TMAX should be specified, see "Starting the Metadata Server"
in the SAS Metadata Server: Setup and Administration Guide. The SAS Open Metadata
Architecture: Best Practices Guide and the SAS Metadata Server: Setup and Administration
Guide are available at support.sas.com/rnd/eai/openmeta/.

PHYSICAL_DELETE Server Configuration Option Deprecated

Beginning with SAS 9.1.3 Service Pack 3, the reserved omaconfig.xml option,
PHYSICAL_DELETE, is deprecated. For more information, see "PHYSICAL_DELETE Option"
in "Understanding Server Configuration Options" in the SAS 9.1.3 Open Metadata
Architecture: Best Practices Guide at support.sas.com/rnd/eai/openmeta/.

SAS Open Metadata Interface Enhancements

Beginning with SAS 9.1.3 Service Pack 3, the SAS Open Metadata Interface Status method
supports <PlatformVersion/> and <ModelVersion/> parameters. These parameters enable
clients to retrieve the SAS Metadata Server and SAS Metadata Model version numbers,
respectively. For more information, see the Status method in the IServer class in SAS 9.1.3
Open Metadata Interface: Reference.

The CheckinMetadata method is also modified. The method no longer restricts the number of
characters that can be entered in the changeDesc parameter. The changeDesc parameter
enables clients to include a description of object modifications with the Change metadata that
is automatically generated by the check-in process. Information that is entered in changeDesc
used to be stored as a Change object attribute but now is stored in a TextStore object. For
more information, see the CheckinMetadata method in the IOMI class in SAS 9.1.3 Open
Metadata Interface: Reference.

SAS Java Metadata Interface Enhancement

Beginning with SAS 9.1.3 Service Pack 3, a getPlatformVersion() method has been added to
the SAS Java Metadata Interface. For more information, see the SAS Java Metadata Interface
API specification at support.sas.com/rnd/gendoc/bi/api/. The getPlatformVersion() method
is in the MetadataWorkspace class.

New SAS Language Interface for Metadata

Beginning with SAS 9.1.3 Service Pack 3, the METALIB procedure is available to automate the
creation and maintenance of the table metadata defined for a SAS library. For more
information, see the METALIB procedure in SAS 9.1.3 Open Metadata Interface: Reference.

Copyright © 2005 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/OR 9.0 and 9.1

Overview

SAS/OR software contains several new and enhanced features since SAS 8.2. Brief
descriptions of the new features appear in the following sections. For more information, refer to
the SAS/OR documentation, which is now available in the following six volumes:

● SAS/OR User's Guide: Bills of Material Processing

● SAS/OR User's Guide: Constraint Programming
● SAS/OR User's Guide: Local Search Optimization
● SAS/OR User's Guide: Mathematical Programming
● SAS/OR User's Guide: Project Management
● SAS/OR User's Guide: The QSIM Application

The online help can also be found under the corresponding classification.

The BOM Procedure

The BOM procedure in SAS/OR User's Guide: Bills of Material Processing was introduced in
Version 8.2 of the SAS System to perform bill of material processing. Several new features
have been added to the procedure, enabling it to read all product structure records from a
product structure data file and all part "master" records from a part master file, and compose
the combined information into indented bills of material. This data structure mirrors the most
common method for storing bill-of-material data in enterprise settings; the part master file
contains data on each part while the product structure file holds data describing the various
part-component relationships represented in bills of material.

The PMDATA= option on the PROC BOM statement enables you to specify the name of the
Part Master data set. If you do not specify this option, PROC BOM uses the Product Structure
data set (as specified in the DATA= option) as the Part Master data set. The BOM procedure
now looks up the Part, LeadTime, Requirement, QtyOnHand, and ID variables in the Part
Master data set. On the other hand, the Component and Quantity variables remain in the
Product Structure data set.
You can use the NRELATIONSHIPS= (or NRELTS=) option to specify the number of parent-
component relationships in the Product Structure data set. You have greater control over the
handling of redundant relationships in the Product Structure data set using the DUPLICATE=
option.

Several options have been added to the STRUCTURE statement enabling you to specify
information related to the parent-component relationships. In particular, the variable specified
with the PARENT= option identifies the parent item, while the variables listed in the
LTOFFSET= option specify lead-time offset information. You can also specify variables
identifying scrap factor information for all parent-component relationships using the
SFACTOR= option. The RID= option identifies all variables in the Product Structure data set
that are to be included in the Indented BOM output data set.

The CLP Procedure - Experimental

The new CLP procedure in SAS/OR User's Guide: Constraint Programming is an

experimental finite domain constraint programming solver for solving constraint satisfaction
problems (CSPs) with linear, logical, global, and scheduling constraints. In addition to having
an expressive syntax for representing CSPs, the solver features powerful built-in consistency
routines and constraint propagation algorithms, a choice of nondeterministic search strategies,
and controls for guiding the search mechanism that enable you to solve a diverse array of
combinatorial problems.

The CPM Procedure

The CPM procedure in SAS/OR User's Guide: Project Management adds more options for
describing resource consumption by activities, enhancing its applicability to production
scheduling models.

A new keyword, RESUSAGE, has been added to the list of values for the OBSTYPE variable
in the Resource data set. This keyword enables you to specify whether a resource is
consumed at the beginning or at the end of a given activity.

The MILESTONERESOURCE option enables you to specify a nonzero usage of consumable

resources for milestone activities. For example, this option is useful if you wish to designate
specific milestones to be the points of payment for a subcontractor. The
MILESTONENORESOURCE option is the current default behavior of the CPM procedure,
which indicates that all resource requirements are to be ignored for milestone activities.

The GA Procedure - Experimental

The new GA procedure in SAS/OR User's Guide: Local Search Optimization facilitates the
application of genetic algorithms to general optimization. Genetic algorithms adapt the
biological processes of natural selection and evolution to search for optimal solutions. The
procedure can be applied to optimize problems involving integer, continuous, binary, or
combinatorial variables. The GA procedure is especially useful for finding optima for problems
where the objective function may have discontinuities or may not otherwise be suitable for
optimization by traditional calculus-based methods.

The GANTT Procedure

The GANTT procedure in SAS/OR User's Guide: Project Management includes a new option
for controlling the width of the Gantt chart. The CHARTWIDTH= option specifies the width of
the axis area as a percentage of the total Gantt chart width. This option enables you to
generate Gantt charts that are consistent in appearance, independent of the total time
spanned by the project.

The LP Procedure

The performances of primal and dual simplex algorithms in the LP procedure (SAS/OR User's
Guide: Mathematical Programming) have been significantly improved on large scale linear or
mixed integer programming problems.

The PM Procedure
The new options added to the CPM procedure are also available with PROC PM.

The QP Procedure - Experimental

The new QP procedure in SAS/OR User's Guide: Mathematical Programming implements

a primal-dual predictor-corrector interior-point algorithm for large sparse quadratic programs.
Depending on the distribution of the eigenvalues of the Hessian matrix, H, two main classes of
quadratic programs are distinguished (assuming minimization):

● convex: H is positive semi-definite

● nonconvex: H has at least one negative eigenvalue

Diagonal and nonseparable Hessian matrices are recognized and handled automatically.

Bill of Material Post Processing Macros

Several macros enable users to generate miscellaneous reports using the Indented BOM
output data set from the BOM procedure in SAS/OR User's Guide: Bills of Material Processing.
Other transactional macros perform specialized transactions for maintaining and updating the
bills of material for a product, product line, plant, or company.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/QC 9.0 and 9.1

Overview

SAS/QC now includes the ANOM procedure for analysis of means, a graphical and statistical
method for comparing a set of means to determine whether any of them are significantly
different from the overall mean. There are also a number of enhancements to the existing
CAPABILITY, OPTEX, RELIABILITY, and SHEWHART procedures.

The ADX Interface for Design of Experiments is a guided point-and-click solution for engineers,
scientists, statisticians, and other researchers who collaboratively design, analyze, and
interpret experiments to improve industrial processes and products. The ADX Interface
supports a variety of designs, including two-level, mixed level, response surface, mixture,
optimal, and split-plot.

The ADX Interface now enables you to

● create general factorial designs with factors having up to nine levels

● create two-level full factorial and minimum aberration fractional factorial generalized split-
plot designs
● delete inactive factors and project a fractional-factorial design to a higher-resolution
design
● join the means in a box plot
● show clear and aliased effects in the alias structure
● display confidence intervals in the response calculator and experiment report
● honor block structure in a blocked design during design randomization

The ADX Interface is documented in the book Getting Started with the SAS 9 ADX Interface for
Design of Experiments.

ANOM Procedure

The ANOM procedure produces analysis of means (ANOM) charts for identifying group
means that differ significantly from the overall mean. An ANOM chart is similar to a control
chart, with a process variable statistic (such as a mean) plotted versus a classification or group
variable. Decision limits on the chart are used to determine which of the group means are
significantly different.

ANOM can be used as an alternative to analysis of variance (ANOVA) in the fixed effects
situation. ANOM differs from ANOVA in that it identifies the groups that are different; ANOVA
only determines whether a significant difference exists. ANOM has the additional advantage of
a convenient graphical representation and lends itself to quality improvement applications in
which the end user has limited background in statistics.

PROC ANOM can be applied to both variables and attribute data, and to equal and unequal
sample sizes.

CAPABILITY Procedure

You can now juxtapose displays, including box-and-whisker plots, dot plots, and carpet plots,
with histograms as aids for visualizing the distribution of process data. The following options
are new in the HISTOGRAM statement:

● The BMCBOXFILL= option specifies the fill color for a box-and-whisker plot in the
bottom margin. By default, the box-and-whisker plot is not filled.
● The BMCFRAME= option specifies the color for filling the frame of a bottom margin plot.
By default, this area is not filled.
● The BMCOLOR= option specifies the color of the dot plot, carpet plot, or the outline of a
box-and-whisker plot in the bottom margin.
● The BMMARGIN= option specifies the height of a bottom margin plot.
● The BMPLOT= option produces a box-and-whisker plot, dot plot, or carpet plot along the
bottom margin of a histogram. A box-and-whisker plot gives a summary of the data
distribution that a histogram alone does not provide. A dot plot or carpet plot shows the
distribution of individual observations.

The following options are new in the COMPHIST and HISTOGRAM statements:

● The FRONTREF option causes reference lines to be drawn in front of histogram bars.
● The LOWER= suboption in the KERNEL option specifies lower bounds for fitted kernel
density estimates.
● The UPPER= suboption in the KERNEL option specifies upper bounds for fitted kernel
density estimates.

CLASS= variables specified in the COMPHIST statement can now have values longer
than 16 characters.
OPTEX Procedure

The OPTEX procedure now enables you to control how CLASS variables are modeled, by
specifying options for the ordering of levels and the parameterization of design matrix columns
associated with the levels. In addition, the default parameterization has been changed to be
orthogonal, providing efficiency values and parameter variances that are easier to interpret and
to compare.

The following options are new in the CLASS statement:

● The DESCENDING option reverses the sorting order of the classification levels.
● The ORDER= option specifies how the classification levels are sorted.
● The PARAM= option specifies the parameterization method for the design matrix
columns associated with classification levels.
● The REF= option specifies the reference level for effect or reference parameterization.

RELIABILITY Procedure

● The MCFPLOT statement has been enhanced to allow recurrence and censoring ages
to be grouped into intervals.
● The INTERPOLATE= option, in the MCFPLOT statement, enables plotted points to be
connected with either a step function or a straight line.
● The PPOS=NELSONAALEN option, in the PROBPLOT statement, enables the use of
Nelson-Aalen plotting positions.
● You can create probability plots when all failure modes act and plot CDF estimates
for individual modes on the same plot.
● You can compute cumulative distribution function estimates and confidence limits
when all modes act.

SHEWHART Procedure

In previous releases of the SHEWHART procedure, the data associated with a subgroup in an
input summary data set had to be complete for that subgroup to be plotted. For example, if the
variable _LCLX_ in a TABLE= data set contained a missing value for a given subgroup, that
subgroup would not be plotted. The SHEWHART procedure now processes data and control
limit values independently, so that the missing value for _LCLX_ produces a gap in the lower
control limit line for that subgroup. The data, central line, and upper control limit for the
subgroup are all plotted, assuming the values of the associated variables are not missing.

Phase and block variable values can now be up to 48 characters long.

The following options are new or enhanced:

● The BOX= option in the PROC SHEWHART statement specifies an input data set
containing subgroup summary data for producing schematic box charts.
● The CGRID= option specifies the color of horizontal grid lines positioned at labeled
major tick marks.
● The CLABEL= option specifies the text color for labels produced by the ALLLABEL=,
ALLLABEL2=, OUTLABEL=, and OUTLABEL2= options.
● The CTESTLABBOX= option specifies the text color for non-overlapping labels for
positive tests for special causes.
● The CTESTSYM= option specifies the color of the symbol used to plot subgroups with
positive tests for special causes.
● The HTML2= option enables you to associate URLs with subgroup points on a
secondary chart when graphics output is directed to HTML.
● The LABELANGLE= option specifies the angle at which labels produced by the
ALLLABEL=, ALLLABEL2=, OUTLABEL=, and OUTLABEL2= options are drawn.
● The OUTBOX= option in the BOXCHART statement produces an output data set
containing complete subgroup summary data for schematic box charts.
● The PHASEVARLABEL option displays the phase variable label above the phase
values.
● The PHASEVALSEP option draws a vertical line separating phase values.
● The SMETHOD=MVGRANGE option in the XRCHART statement causes the process
standard deviation to be estimated using a moving range of subgroup averages. You
can use this to construct control charts for means when the jth measurement in the ith
subgroup can be modeled as , where is the between-
subgroup variance, is the within-subgroup variance, the are independent with
zero mean and unit variance, and the are independent of the . This method can
also be used to construct the three-way control chart, which is advocated for this
situation by Wheeler (1995). A three-way control chart is useful when sampling, or within-
group, variation is not the only source of variation, as discussed in "Multiple
Components of Variation" . A three-way control chart comprises a chart of subgroup
means, a moving range chart of the subgroup means, and a chart of subgroup ranges.
When you specify the SMETHOD=MVGRANGE option, the XRCHART statement
produces the appropriate charts of subgroup means and subgroup ranges.
● The TESTLABBOX option produces labels for subgroups with positive tests for special
causes that are positioned so they do not overlap, if possible. The labels are enclosed in
boxes which are connected to the associated subgroup points with line segments.
● The TESTSYM= option specifies a symbol for plotting subgroups with positive tests for
special causes.
● The TESTSYMHT= option specifies the height of the symbol used to plot subgroups
with positive tests for special causes.
 ● The WNEEDLES= option specifies the width, in pixels, of needles that connect plotted
points to the central line.
● The ZEROSTD=NOLIMITS option suppresses the degenerate control limits on a
control chart produced when the estimated process standard deviation is zero.

References

Wheeler, D. J. (1995), Advanced Topics in Statistical Process Control, Knoxville, TN: SPC
Press, Inc.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS 9.0 and 9.1 ADX Interface for Design of
Experiments

Overview

The SAS ADX Interface for Design of Experiments includes enhancements related to response
surface designs, mixture designs, general factorial designs, and split-plot designs.
Furthermore, ADX can now import data from SAS data sets or external file formats, and it can
export design information to SAS data sets or external file formats.

The SAS ADX Interface now enables you to

● create general factorial designs with factors having up to nine levels

● create two-level full factorial and fractional factorial split-plot designs
● delete inactive factors and project a fractional-factorial design to a higher-resolution
design
● join the means in a box plot
● show clear and aliased effects in the alias structure
● display confidence intervals in the response calculator and experiment report
● honor block structure in a blocked design during design randomization

Details

Response Surface Designs

ADX can now create designs based on Hartley's (1959) small response surface designs.

Variance dispersion graphs are generated in the design details so you can compare designs
and choose the best number of center points. This option requires SAS/IML software.

Mixture Designs

Process variables can now be included in the creation and analysis of mixture designs. Mixture
designs with process variables are created using the optimal design interface. The analysis will
determine whether process variables are significant, but all such variables will be included in
the optimization process. In the optimization tools, process variables are treated as fixed-level
factors.

General Factorial Designs

General factorial designs are designs that run all combinations of factor levels. In ADX, you
can create general factorials with factors having any number of levels.

Split-Plot Designs

ADX can now create full factorial and two-level minimum aberration fractional factorial
generalized split-plot designs as described in Huang, Chen, and Voelkel (1998).

Data Import and Export

ADX can import factor and response values from SAS data sets or external files. You can
create the design in ADX and import solely the response information, or you can import both
the factor levels and the response.

ADX can export design information to SAS data sets and external files for inclusion in a data
warehouse. You can export variable information, experiment details, and values for the factors
and response.

Access to external file formats requires SAS/ACCESS software.

References

Hartley, H. O. (1959), "Smallest Composite Designs for Quadratic Response Surfaces,"

Biometrics, 15, 611--624.

Huang, P., Chen, D., and Voelkel, J. O. (1998), "Minimum-Aberration Two-Level Split-Plot
Designs," Technometrics, 40, 314--326.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/SHARE 9.0 and 9.1

Overview

The following new and enhanced features for SAS/SHARE ensure information privacy and
improve ease of use:

● The network security protocol Secure Sockets Layer (SSL) encrypts connections
between client and server.

● TCP/IP users can specify a port number explicitly, instead of specifying an already
defined server ID.

● Any form of a password option in a SAS/SHARE statement can be specified as an

encoded password.

● The SERVER= option in the LIBNAME statement specifies a CONNECT server

definition that has been defined in a SAS Metadata Repository.

● The HOSTNAME= option in the LIBNAME statement specifies the name of the node on
which the SAS/SHARE server runs.

● The CLIENTID= option in the PROC SERVER statement enables you to select whether
the log identifies clients by their session names or their secured names.

● The THREADEDTCP option in the PROC SERVER statement invokes the threaded
version of the TCP/IP access method and associated threaded infrastructure when the
TCP/IP access method is specified. (This option is experimental.)

● Specifying an automatic log rollover by using the LOGPARM option is a preferred log
management strategy for a SAS/SHARE server.

● Revised procedures are available for creating the SAS/SHARE server environment
under the UNIX and Windows operating environments.

● If the SAS/SHARE server log is not available, error messages are written to the SAS
console log.

● The documentation includes new information about server log messages and SAS
 system options that are used with SAS/SHARE. For details, see Interpreting Server Log
Messages; SAS/SHARE General SAS System Options; SAS/SECURE and SAS
Proprietary System Options; and Secure Sockets Layer (SSL) Options.

Note:

● This section describes the features of SAS/SHARE 9.1 that are new or enhanced since
SAS 8.2.

● z/OS is the successor to the OS/390 operating system. SAS/SHARE is supported on

both OS/390 and z/OS operating systems and, throughout this document, any reference
to z/OS also applies to OS/390, unless otherwise stated.

Details

Security

● Secure Sockets Layer (SSL) is a protocol that provides network security and protects
the privacy of information by encrypting SAS/SHARE client/server transfers under the
UNIX and Windows operating environments. SSL is implemented by means of Secure
Sockets Layer (SSL) Options.

● Using encoded passwords promotes security and enables you to store SAS programs
that do not contain clear-text passwords. The syntax for each of the following statements
in SAS/SHARE enables you to specify encoded passwords.

❍ PROC SERVER

■ OAPW=password;

■ UAPW=password;

■ PT2DBPW=password;

❍ LIBNAME

■ PASSWORD=password;
 ■ SAPW=password;

❍ PROC OPERATE

■ SAPW=password;

■ PASSWORD=password;

■ DISPLAY SERVER (SAPW=password);

■ QUIESCE SERVER (SAPW=password);

■ START SERVER (SAPW=password);

■ STOP SERVER (SAPW=password);

❍ PROC SQL;

■ CONNECT TO REMOTE (SAPW=password);

■ SELECT...FROM CONNECTION TO (PASSWORD=password);

■ SELECT...FROM CONNECTION TO (PT2DBPW=password);

Compatibility

SAS 9.1 does not permit a client or a server to connect to a Version 6 server or client. For
details, see SAS/SHARE Cross-Version Issues, SAS 9.1.

Explicit Port Specification

If a SAS/SHARE client uses the TCP/IP access method to access a SAS/SHARE server by
using an explicit port specification instead of the server ID, you can now use two consecutive
underscores (_ _) with a port number in the syntax, in place of a server ID that has been
defined in the client TCP/IP SERVICES file. An explicit port can be specified in the SERVER=
option in

● the LIBNAME statement

 ● the SERVER procedure

● the OPERATE procedure

● the Remote SQL Pass-Through (RSPT) facility.

Note: Specifying a server using a port number is not supported for ODBC clients.

Enhanced Use of the LOGPARM System Option

Specifying an automatic log rollover is a preferred strategy for managing a SAS/SHARE server
session. Setting the "ROLLOVER=AUTO" value for the LOGPARM option closes the current
log and opens a new log file if the value of the LOG= option changes. Rollover is triggered by a
change in the value of the LOG= option. For examples of configuring automatic log rollover in
the server environment, see UNIX and Windows.

New LIBNAME Options and Values

● The SERVER= option in the LIBNAME statement specifies a CONNECT server

definition that has been defined in a SAS Metadata Repository.

● The HOSTNAME= option in the LIBNAME statement specifies the name of the node on
which the SAS/SHARE server runs.

New PROC SERVER Options

● The CLIENTID= option in the PROC SERVER statement enables you to select whether
the log identifies clients by their session names or their secured names. Your choice
determines the search order that is used to locate the appropriate client ID.

● The THREADEDTCP option in the PROC SERVER statement invokes the threaded
version of the TCP/IP access method and associated threaded infrastructure when the
TCP/IP access method is specified.

CAUTION:
THREADEDTCP is an experimental option that is available in SAS 9.1

Do not use this option in production jobs.

Using the SAS Console Log to Analyze Server Errors

If the SAS/SHARE server encounters problems at SAS initialization or at SAS termination, the
server log might not be available to receive error messages. If the server log is not available,
error messages are written to the SAS console log. For details about the SAS console log, see
the companion documentation that is appropriate for the operating environment that you are
using.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS/STAT 9.0 and 9.1

Overview

This release brings several new procedures to SAS/STAT software. The MI and MIANALYZE
procedures implement the multiple imputation strategy for missing data. Experimental in
Releases 8.1 and 8.2, these procedures are now production. The ROBUSTREG procedure
analyzes data that may include outliers; it provides stable results in their presence. The
TPHREG procedure is a test release of the PHREG procedure that incorporates the CLASS
statement.

Power and sample size computations also become available in SAS 9.1. New procedures
POWER and GLMPOWER provide these computations for a number of analyses, and the
Power and Sample Size Application surfaces them through a point-and-click interface.

SAS 9.1 introduces two new procedures for the analysis of survey data. The SURVEYFREQ
procedure produces one-way to n-way frequency and crosstabulation tables for data collected
from surveys. These tables include estimates of totals and proportions (overall, row
percentages, column percentages) and the corresponding standard errors. The
SURVEYLOGISTIC procedure performs logistic regression for survey data, and it can also fit
links such as the cumulative logit, generalized logit, probit, and complementary log-log
functions. Both of these procedures incorporate complex survey sample designs, including
designs with stratification, clustering, and unequal weighting, in their computations.

In addition, this release includes numerous enhancements to existing procedures. For

example, conditional logistic regression is available in the LOGISTIC procedure through the
new STRATA statement, and scoring of data sets is available through the new SCORE
statement. The GLM procedure now provides the ability to form classification groups using the
full formatted length of the CLASS variable levels. In addition, the SURVIVAL statement in the
LIFETEST procedure enables you to create confidence bands (also known as simultaneous
confidence intervals) for the survivor function S(t) and to specify a transformation for
computing the confidence bands and the pointwise confidence intervals.

More information about the changes and enhancements to SAS/STAT software follows.
Features new in SAS 9.1 are indicated with a 9.1 icon; other features were available with SAS
9.0. Details can be found in the documentation for the individual procedures.

Parallelization
Selected functionalities in the GLM, LOESS, REG, and ROBUSTREG procedures have been
multithreaded to exploit hardware with multiple CPUs. Refer to Cohen (2002) for more details.

Statistical Graphics Using ODS

A number of SAS/STAT procedures are using an experimental extension to the Output

Delivery System (ODS) that enables them to create statistical graphics automatically. The
facility is invoked when you include an ODS GRAPHICS statement before your procedure
statements. Graphics are then created automatically, or when you specify procedure options
for graphics. Procedures taking advantage of ODS graphics are the ANOVA, CORRESP,
GAM, GENMOD, GLM, KDE, LIFETEST, LOESS, LOGISTIC, MI, MIXED, PHREG, PLS,
PRINCOMP, PRINQUAL, REG, ROBUSTREG, and TPSLINE procedures. The plots produced
and the corresponding options are described in the documentation for the individual
procedures.

CATMOD Procedure

Memory handling has been improved in the CATMOD procedure. The

PARAM=REFERENCE option has been added to the MODEL statement and produces
reference cell parameterization. Other new options include the ITPRINT, DESIGN, and
PROFILE|POPPROFILE options in the PROC statement.

DISTANCE Procedure

The new DISTANCE procedure computes various measures of distance, dissimilarity, or

similarity between the observations (rows) of a SAS data set. These proximity measures are
stored as a lower triangular matrix or a square matrix in an output data set (depending on the
SHAPE= option) that can then be used as input to the CLUSTER, MDS, and MODECLUS
procedures. The input data set may contain numeric or character variables, or both, depending
on which proximity measure is used. PROC DISTANCE also provides various nonparametric
and parametric methods for standardizing variables. Distance matrices are used frequently in
data mining, genomics, marketing, financial analysis, management science, education,
chemistry, psychology, biology, and various other fields.

FACTOR Procedure

The NOPROMAXNORM option turns off the default row normalization of the pre-rotated factor
pattern, which is used in computing the promax target matrix.
You can now produce standard errors and confidence limits with the METHOD=ML option for
the PROMAX factor solutions. You can obtain the standard errors with the SE option, control
the coverage displays with the COVER= option, and set the coverage level with the ALPHA=
option.

FREQ Procedure

The BDT option includes Tarone's adjustment in the Breslow-Day test for homogeneity of odds
ratios. Refer to Agresti (1996) and Tarone (1985).

The ZEROS option in the WEIGHT statement includes zero-weight observations in the
analysis. (By default, PROC FREQ does not process zero-weight observations.) With the
ZEROS option, PROC FREQ displays zero-weight levels in crosstabulation and frequency
tables. For one-way tables, the ZEROS option includes zero-weight levels in chi-square tests
and binomial statistics. For multiway tables, the ZEROS option includes zero-weight levels in
kappa statistics.

The CROSSLIST option displays crosstabulation tables in ODS column format. Unlike the
default crosstabulation table, the CROSSLIST table has a table definition that you can
customize with PROC TEMPLATE. The NLEVELS option provides a table with the number of
levels for all TABLES statement variables.

The FREQ procedure now produces exact confidence limits for the common odds ratio
and related tests.

GENMOD Procedure

The GENMOD procedure now forms classification groups using the full formatted length of the
CLASS variable levels. Several new full-rank CLASS variable parameterizations are now
available: polynomial, orthogonal polynomial, effect, orthogonal effect, reference, orthogonal
reference, ordinal, and orthogonal ordinal. The default parameterization remains the same less-
than-full-rank parameterization used in previous releases.

Zero is now a valid value for the negative binomial dispersion parameter corresponding to the
Poisson distribution. If a fixed value of zero is specified, a score test for overdispersion
(Cameron and Trivedi 1998) is computed.

As an experimental feature, PROC GENMOD now provides model assessment based on

aggregates of residuals.
GLM Procedure

The GLM procedure now forms classification groups using the full formatted length of the
CLASS variable levels.

In addition, you can compute exact p-values for three of the four multivariate tests (Wilks'
Lambda, the Hotelling-Lawley Trace, and Roy's Greatest Root) and an improved F-
approximation for the fourth (Pillai's Trace). The default MSTAT=FAPPROX in the MANOVA
and REPEATED statements produces multivariate tests using approximations based on the F
distribution. Specifying MSTAT=EXACT computes exact p-values for three of the four tests
(Wilks' Lambda, the Hotelling-Lawley Trace, and Roy's Greatest Root) and an improved F-
approximation for the fourth (Pillai's Trace).

GLMPOWER Procedure

The GLMPOWER procedure performs prospective analyses for linear models, with a
variety of goals:

● determining the sample size required to obtain a significant result with adequate
probability (power)
● characterizing the power of a study to detect a meaningful effect
● conducting what-if analyses to assess sensitivity of the power or required sample size to
other factors

You specify the design and the cell means using an exemplary data set, a data set of artificial
values constructed to represent the intended sampling design and the surmised response
means in the underlying population. You specify the model and contrasts using MODEL and
CONTRAST statements similar to those in the GLM procedure. You specify the remaining
parameters with the POWER statement, which is similar to analysis statements in the new
POWER procedure.

KDE Procedure

The new UNIVAR and BIVAR statements provide improved syntax. The BIVAR statement
lists variables in the input data set for which bivariate kernel density estimates are to be
computed. The UNIVAR statement lists variables in the input data set for which univariate
kernel density estimates are to be computed.
LIFETEST Procedure

The new SURVIVAL statement enables you to create confidence bands (also known as
simultaneous confidence intervals) for the survivor function S(t) and to specify a transformation
for computing the confidence bands and the pointwise confidence intervals. It contains the
following options.

● The OUT= option names the output SAS data set that contains survival estimates as in
the OUTSURV= option in the PROC LIFETEST statement.
● The CONFTYPE= option specifies the transformation applied to S(t) to obtain the
pointwise confidence intervals and the confidence bands. Four transforms are available:
the arcsine-square root transform, the complementary log-log transform, the logarithmic
transform, and the logit transform.
● The CONFBAND= option specifies the confidence bands to add to the OUT= data set.
You can choose the equal precision confidence bands (Nair 1984), or the Hall-Wellner
bands (Hall and Wellner 1980), or both.
● The BANDMAX= option specifies the maximum time for the confidence bands.
● The BANDMIN= option specifies the minimum time for the confidence bands.
● The STDERR option adds the column of standard error of the estimated survivor
function to the OUT= data set.
● The ALPHA= option sets the confidence level for pointwise confidence intervals as well
as the confidence bands.

The LIFETEST procedure now provides additional tests for comparing two or more
samples of survival data, including the Tarone-Ware test, Peto-Peto test, modified Peto-Peto
test, and the Fleming-Harrington family of tests. Trend tests for ordered alternatives can
be requested. Also available are stratified tests for comparing survival function while adjusting
for prognostic factors that affect the event rates.

LOESS Procedure

The LOESS procedure now performs DF computations using a sparse method when
appropriate. In addition, the DFMETHOD=APPROX option is available.

LOGISTIC Procedure

The new SCORE statement enables you to score new data sets and compute fit statistics and
ROC curves without refitting the model. Information for a fitted model can be saved to a SAS
data set with the OUTMODEL= option, while the INMODEL= option inputs the model
information required for the scoring.

The new STRATA statement enables you to perform conditional logistic regression on highly
stratified data using the method of Gail, Lubin, and Rubenstein (1981). The OFFSET option is
now enabled for logistic regression.

The LOGISTIC procedure now forms classification groups using the full formatted length of the
CLASS variable levels.

Several new CLASS parameterizations are available: ordinal, orthogonal effect, orthogonal
reference, and orthogonal ordinal.

You can now output the design matrix using the new OUTDESIGN= option.

The definition of concordance has been changed to make it more meaningful for ordinal
models. The new definition is consistent with that used in previous releases for the binary
response model.

Enhancements for the exact computations include

● improved performance
● Monte Carlo method
● mid-p confidence intervals

For an exact conditional analysis, specifying the STRATA statement performs an efficient
stratified analysis. The method of Mehta, Patel, and Senchaudhuri (1992), which is more
efficient than the Hirji, Tsiatis, and Mehta (1989) algorithm for many problems, is now available
with the METHOD=NETWORK option.

MI Procedure

The INITIAL= option in the EM statement sets the initial estimates for the EM algorithm. Either
the means and covariances from complete cases or the means and standard deviations from
available cases can be used as the initial estimates for the EM algorithm. You can also specify
the correlations for the initial estimates from available cases.

For data sets with monotone missingness, the REGPMM option in the MONOTONE
statement uses the predictive mean matching method to impute a value randomly from a set of
observed values whose predicted values are closest to the predicted value for the missing
value from the simulated regression model.
You can specify more than one method in the MONOTONE statement, and for each imputed
variable, the covariates can be specified separately.

The DETAILS option in the MONOTONE statement requests the display of the model
parameters used for each imputation.

The experimental CLASS statement is now available to specify categorical variables. These
classification variables are used either as covariates for imputed variables or as imputed
variables for data sets with monotone missing patterns.

The experimental options LOGISTIC and DISCRIM in the MONOTONE statement impute
missing categorical variables by logistic and discriminant methods, respectively.

MIANALYZE Procedure

You can now specify the PARMS= data set without specifying either the COVB= or XPXI=
option when the data set contains the standard errors for the parameter estimates.

The DATA= option includes data sets that contain both parameter estimates and their
associated standard errors in each observation of the data set.

The BCOV, WCOV, and TCOV options control the display of the between-imputation, within-
imputation, and total covariance matrices.

A TEST statement tests linear hypotheses about the parameters, . For each
TEST statement, the procedure combines the estimate and associated standard error for each
linear component ( a row of ). It can also combine the estimates and associated
covariance matrix for all linear components.

The MODELEFFECTS statement lists the effects in the data set to be analyzed. Each effect is
a variable or a combination of variables, and is specified with a special notation using variable
names and operators. The STDERR statement lists the standard errors associated with the
effects in the MODELEFFECTS statement when both parameter estimates and standard
errors are saved as variables in the same DATA= data set.

The experimental CLASS statement specifies categorical variables. PROC MIANALYZE reads
and combines parameter estimates and covariance matrices for parameters with CLASS
variables.
MIXED Procedure

The MIXED procedure now supports geometrically anisotropic covariance structures and
covariance models in the Matern class. The LCOMPONENTS option in the MODEL statement
produces one degree of freedom tests for fixed effects that correspond to individual estimable
functions for Type I, II, and III effects.

The experimental RESIDUAL option of the MODEL statement computes Pearson-type

and (internally) studentized residuals. The experimental INFLUENCE option in the MODEL
statement computes influence diagnostics by noniterative or iterative methods. Experimental
ODS graphics display the results for both of these options.

NPAR1WAY Procedure

The new D option provides the one-sided D+ and D- statistics for the asymptotic two-sample
Kolmogorov-Smirnov test, in addition to the two-sided D statistic given by the EDF option. The
KS option in the EXACT statement gives exact tests for the Kolmogorov-Smirnov D+, D-, and
D for two-sample problems.

PHREG Procedure

The new WEIGHT statement enables you to specify case weights when you are using the
BRESLOW or EFRON method for handling ties. Robust sandwich variance estimators of
Binder (1992) are computed for the estimated regression parameters. You can specify the
option NORMALIZE to normalize the weights so that they add up the actual sample size.

Two options have been added to the TEST statement: AVERAGE and E. The AVERAGE
option enables you to compute a combined estimate of all the effects in the given TEST
statement. This option gives you an easy way to carry out inferences of the common value of
(say) the treatment effects had they been assumed equal. The E option specifies that the
linear coefficients and constants be printed. When the AVERAGE option is specified along with
the E option, the optimal weights of the average effect are also printed in the same tables as
the coefficients.

The recurrence algorithm of Gail, Lubin, and Rubinstein (1981) for computing the exact
discrete partial likelihood and its partial derivatives has been modified to use the logarithmic
scale. This enables a much larger number of ties to be handled without the numeric problems
of overflowing and underflowing.
 You can use the PHREG procedure to fit the rate/mean model for the recurrent events
data and obtain prediction of the cumulative mean function for a given pattern of fixed
covariates.

As an experimental feature, the PHREG procedure now can produce model assessments
based on cumulative residuals.

POWER Procedure

The POWER procedure performs prospective analyses for a variety of goals such as the
following:

● determining the sample size required to get a significant result with adequate probability
(power)
● characterizing the power of a study to detect a meaningful effect
● conducting what-if analyses to assess sensitivity of the power or required sample size to
other factors

This procedure covers a variety of statistical analyses such as t tests, equivalence tests, and
confidence intervals for means; exact binomial, chi-square, Fisher's exact, and McNemar tests
for proportions; multiple regression and correlation; one-way analysis of variance; and rank
tests for comparing survival curves.

The POWER procedure is one of several tools available in SAS/STAT software for power and
sample size analysis. PROC GLMPOWER covers more complex linear models, and the Power
and Sample Size Application provides a user interface and implements many of the analyses
supported in the procedures.

Power and Sample Size Application

The Power and Sample Size Application (PSS) is an interface that provides power and sample
size computations. The application includes tasks for determining sample size and power for a
variety of statistical analyses, including t-tests, ANOVA, proportions, equivalence testing, linear
models, survival analysis, and table statistics. The application provides multiple input
parameter options, stores results in a project format, displays power curves, and produces
appropriate narratives for the results. Note that this application is included with SAS/STAT
software but needs to be installed from the Mid Tier CD.
ROBUSTREG Procedure

The ROBUSTREG procedure provides resistant (stable) results in the presence of outliers
by limiting the influence of outliers. In statistical applications of outlier detection and robust
regression, the methods most commonly used today are Huber (1973) M estimation, high
breakdown value estimation, and combinations of these two methods. The ROBUSTREG
procedure provides four such methods: M estimation, LTS estimation, S estimation, and MM
estimation. With these four methods, the ROBUSTREG procedure acts as an integrated tool
for outlier detection and robust regression with various contaminated data. The ROBUSTREG
procedure is scalable such that it can be used for applications in data cleansing and data
mining.

SURVEYFREQ Procedure

The SURVEYFREQ procedure produces one-way to n-way frequency and crosstabulation

tables for survey data. These tables include estimates of totals and proportions (overall, row
percentages, column percentages) and the corresponding standard errors. Like the other
survey procedures, PROC SURVEYFREQ computes these variance estimates based on the
sample design used to obtain the survey data. The design can be a complex sample survey
design with stratification, clustering, and unequal weighting. PROC SURVEYFREQ also
provides design-based tests of association between variables.

SURVEYLOGISTIC Procedure

The SURVEYLOGISTIC procedure performs logistic regression on data that arise from a
survey sampling scheme. PROC SURVEYLOGISTIC incorporates complex survey sample
designs, including designs with stratification, clustering, and unequal weighting, in its
estimation process. Variances of the regression parameters and odds ratios are computed
using a Taylor expansion approximation. The SURVEYLOGISTIC procedure is similar in
syntax to the LOGISTIC procedure, and it can fit link functions such as the logit, cumulative
logit, generalized logit, probit, and complementary log-log functions. Maximum likelihood
estimation of the regression coefficients is carried out with either the Fisher-scoring algorithm
or the Newton-Raphson algorithm.

SURVEYMEANS Procedure

The STACKING option requests the procedure to produce the output data sets using a
stacking table structure, which was the default in earlier releases. The new default is to
produce a rectangular table structure in the output data sets. The STACKING option affects
the Domain, Ratio, Statistics, and StrataInfo tables.

One-sided confidence limits are now available for descriptive statistics.

SURVEYREG Procedure

The SURVEYREG procedure now provides the ability to form classification groups using the
full formatted length of the CLASS variable levels, instead of just the first 16 characters of the
levels. The ANOVA option in the MODEL statement requests that the ANOVA table be
included in the output.

SURVEYSELECT Procedure

The OUTALL option produces an output data set that includes all observations from the
DATA= input data set, both those observations selected for the sample and those observations
not selected. With the OUTALL option, the OUT= data set contains a variable Selected that
indicates whether or not the observation was selected. The OUTALL option is available for
equal probability selection methods (METHOD=SRS, URS, SYS, and SEQ).

The SELECTALL option includes all stratum observations in the sample when the stratum
sample size exceeds the number of observations in the stratum. The SELECTALL option is
available for without-replacement selection methods (METHOD=SRS, SYS, SEQ, PPS, and
PPS_SAMPFORD). It is not available for with-replacement or with-minimum-replacement
methods, or for those PPS methods that select two units per stratum.

The OUTSEED option includes the initial seed for each stratum in the output data set.
Additionally, you can input initial seeds by strata with the SEED=SAS-data-set option.

TPHREG Procedure

The experimental TPHREG procedure adds the CLASS statement to the PHREG procedure.
The CLASS statement enables you to specify categorical variables (also known as CLASS
variables) as explanatory variables. Explanatory effects for the model, including covariates,
main effects, interactions, and nested effects, can be specified in the same way as in the GLM
procedure. The CLASS statement supports less-than-full-rank parameterization as well as
various full-rank parameterizations such as reference coding and effect coding. Other CLASS
statement features that are found in PROC LOGISTIC, such as specifying specific categories
as reference levels, are also available.
The TPHREG procedure also enables you to specify CONTRAST statements for testing
customized hypotheses concerning the regression parameters. Each CONTRAST statement
also provides estimation of individual rows of contrasts, which is particularly useful in
comparing the hazards between the categories of a CLASS explanatory variable.

TPSPLINE Procedure

The COEF option in the OUTPUT statement enables you to output coefficients of the fitted
function.

TRANSREG Procedure

The TRANSREG procedure has new transformation options for centering and standardizing
variables, CENTER and Z, before the transformations. The new EXKNOTS= option specifies
exterior knots for SPLINE and MSPLINE transformations and BSPLINE expansions.

The new algorithm option INDIVIDUAL with METHOD=MORALS fits each model for each
dependent variable individually and independently of the other dependent variables.

With hypothesis tests, the TRANSREG procedure now produces a table with the number of
observations, and, when there are CLASS variables, a class level information table.

Reference

Agresti, A. (1996), An Introduction to Categorical Data Analysis, New York: John Wiley &
Sons, Inc.

Binder, D.A. (1983), "On the Variances of Asymptotically Normal Estimators from Complex
Surveys," International Statistical Review, 51, 279 - 292.

Binder, D.A. (1992), "Fitting Cox's Proportional Hazards Models from Survey Data,"
Biometrika, 79, 139 - 47.

Cameron, A.C. and Trivedi, P.K. (1998), "Regression Analysis of Count Data," Cambridge:
Cambridge University Press.

Cohen, R. (2002), "SAS Meets Big Iron: High Performance Computing in SAS Analytical
Procedures," Proceedings of the Twenty-seventh Annual SAS Users Group International
Conference.

Gail, M.H., Lubin, J.H., and Rubinstein, L.V. (1981), "Likelihood Calculations for Matched Case-
Control Studies and Survival Studies with Tied Survival Times," Biometrika, 78, 703 - 7.

Hall, W.J. and Wellner, J.A. (1980), "Confidence Bands for a Survival Curve for Censored
Data," Biometrika 69, 133 - 143.

Hirji, K.F., Mehta, C.R., and Patel, N.R. (1987), "Computing Distributions for Exact Logistic
Regression," Journal of the American Statistical Association, 82, 1110 - 1117.

Hirji, K.F., Tsiatis, A.A., and Mehta, C.R. (1989), "Median Unbiased Estimation for Binary
Data," American Statistician, 43, 7 - 11.

Huber, P.J. (1973), "Robust Regression: Asymptotics, Conjectures and Monte Carlo," Annals
of Statistics, 1, 799-821.

Mehta, C.R., Patel, N., and Senchaudhuri, P. (1992), "Exact Stratified Linear Rank Tests for
Ordered Categorical and Binary Data," Journal of Computational and Graphical Statistics, 1,
21 - 40.

Nair, V.N. (1984), "Confidence Bands for Survival Functions with Censored Data: A
Comparative Study," Technometrics, 14, 265 - 275.

Tarone, R. (1985), "On Heterogeneity Tests Based on Efficient Scores," Biometrika, 72, 91 -
95.

Copyright © 2003 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
What's New

What's New in SAS Web Report Studio 2.1

Overview

A more intuitive workflow is one of the key enhancements of the latest version of SAS Web
Report Studio, which also offers improved charting, filtering, and sorting.

Details

Note: Only authorized users can create and edit reports. If you have questions about your
authorization, contact your system administrator.

Workflow

● Switch between viewing and editing a report with one click.

● Navigate sections by using tabs. Also, a new Section menu is available in the Edit
Report view for creating new sections, deleting sections, moving sections, and renaming
sections.

● A context-sensitive Report menu is available in the edit or view mode. Menu items
include: Quick Report, Page Setup, Print, View Scheduled Reports, and Export
Report.

● Information entered into the Report Wizard is automatically displayed in the Edit Report
view so that you can further fine-tune your selections. For example, you can add more
objects to the layout such as images and text. You also can add report links to objects
and specify conditional highlighting for tables and graphs.

Creation

● Link text, images, table values, graph values, and group break values to another report
or to a Web page.

● Include dynamic text in headers and footers.

 ● Combine measure data items from multidimensional data sources in order to create a
custom data item. (Previously, custom data items could only be created from relational
data sources.)

● Generate quick reports. A quick report uses one crosstabulation table and one bar chart
to present the results of a query that is based on four standard data items from a
selected data source. The data items are the first three categories and the first measure
in the data source.

● Create one-section report templates. Report templates contain layout information but do
not contain data. A report template is one of four starting points for creating reports.

● Use the same data item from a relational data source more than once in a single report
section. For measures, you can apply a different summarization method to each.

● For category data items in a relational data source, create filters that prompt users for
values.

● Create filters that use the BETWEEN operator. The BETWEEN operator is available for
relational category data items for the parent query and for measures when the filter is
applied to an individual table or graph.

● Create filters that identify missing values. Filters for missing values are supported for
category data items for the parent query and for measure data items for individual tables
and graphs.

Presentation

● Highlight table and graph values that meet certain conditions. For tables, you can
highlight using colors, formatted text, and images. For graphs, shading is used to
identify values that match the specified condition.

● Gain more control over the display of tables by specifying a size in pixels and by
indicating wrapping preferences.

● Gain more control of the display of graphs by specifying a size. Also, set styles and
colors for elements such as legends, axis labels, and titles.

● Synchronize objects in the report layout so that all objects share category-based filters,
sorting, drilling, and expanding.
 ● Format text in text objects by applying a font, font size, font style, background color,
foreground color, and alignment. Depending on the data items selected for the report
section, text objects might also include prompt and measure values.

● Insert image objects into the layout of a report. You can include images from a
repository or from your local machine into the body of a report that is based on standard
or custom data items. If you select an image from your local machine, it is saved to the
repository. You can add tool-tip text to an image as well as link the image to another
report or a Web page.

● Choose to display applied filter information when viewing a report. Filter information will
also be included in the printed report.

● Add percentage calculations, totals, and comparisons to summary values to a table.

● Rotate crosstabulation tables that use relational data. (Previously, rotation was only
available for crosstabulation tables that used multidimensional data sources.)

● When viewing a list table, you can specify a sorting priority for up to three columns.
(Previously, setting a sorting priority was only available when creating or editing a
report.)

● Specify formatting for totals and subtotals.

Graphs

● Include progressive bar charts in reports. A progressive bar chart shows how the initial
value of a measure data item increases or decreases during a series of operations or
transactions. See also bar chart.

● Include scatter plots in reports. A scatter plot is a two- or three-dimensional plot that
shows the joint variation of two (or three) data items.

Scheduling

You can schedule reports to run at specified times. Reports that are pre-generated in this way
generally render faster than reports that automatically query the data source each time that
they are viewed. You also can monitor your own list of scheduled reports to see which reports
are running, which reports have failed, and which reports have executed.
Exporting

Export the contents of an entire report to a zipped file. The contents of the file can be opened
in a Web browser.

Copyright © 2005 by SAS Institute Inc., Cary, NC, All rights reserved.