powercenter connect 8.1.1 for sas user guide · informatica, “as-is”, without warranty of any...

User Guide

PowerCenter Connect for SAS(Version 8.1.1)

PowerCenter Connect for SAS User GuideVersion 8.1.1November 2006

Copyright (c) 1998–2006 Informatica Corporation.All rights reserved. Printed in the USA.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data Quality and Informatica Data Explorer are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies, 1999-2002. All rights reserved. Copyright © Sun Microsystems. All Rights Reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All Rights Reserved.

Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved.

Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2005 The Apache Software Foundation. All rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved.

The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler.

The Curl license provided with this Software is Copyright 1996-2004, Daniel Stenberg, <[email protected]>. All Rights Reserved.

The PCRE library included with this software is Copyright (c) 1997-2001 University of Cambridge Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel. The source for this library may be found at ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre.

InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved.

Portions of the Software are Copyright (c) 1998-2005 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License, available at http://www.openldap.org/software/release/license.html.

This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775 and other U.S. Patents Pending.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied,including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiAbout This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . xiii

Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1: Understanding PowerCenter Connect for SAS . . . . . . . . . .1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

SAS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . .5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing the Client Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing the Repository Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing the Server Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing and Configuring the Communication Component . . . . . . . . . . . . . 13

Installing the Communication Component on Windows . . . . . . . . . . . . . 13

Installing the Communication Component on UNIX . . . . . . . . . . . . . . . 13

Configuring the Communication Component . . . . . . . . . . . . . . . . . . . . 13

Starting the Communication Component on Windows . . . . . . . . . . . . . . 15

Table of Contents iii

Starting the Communication Component on UNIX . . . . . . . . . . . . . . . . 15

Configuring a SAS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3: Working with SAS Sources . . . . . . . . . . . . . . . . . . . . . . . .17Creating a SAS Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Editing a SAS Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Column Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4: Working with SAS Targets . . . . . . . . . . . . . . . . . . . . . . . . . 21Creating a SAS Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Editing a SAS Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Column Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring Indexes and Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring a Key Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Working with Field Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuring Load Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Full Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Append Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Update Else Insert Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5: Working with SAS Sessions . . . . . . . . . . . . . . . . . . . . . . . 27Editing a SAS Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 6: Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Reading SAS Character Columns with Binary Zeros . . . . . . . . . . . . . . . . . . . 30

Session Identification Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Removing Leading Spaces in Text Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Appendix A: SPI Server Configuration Options . . . . . . . . . . . . . . . . . 33Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Appendix B: SAS Datatypes and Formats . . . . . . . . . . . . . . . . . . . . . 35SAS Datatypes and Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

iv Table of Contents

Character Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Numeric Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Date, Time, and Datetime Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Appendix C: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Client Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Integration Service Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Communication Component Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table of Contents v

vi Table of Contents

List of Figures

Figure 1-1. PowerCenter Integration with SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 2-1. SPI Server Configuration for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 2-2. SPI Server Configuration for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 4-1. SAS Target Field Attributes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

List of Figures vii

viii List of Figures

List of Tables

Table 2-1. Installation Guidelines and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Table 2-2. SAS Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

List of Tables ix

x List of Tables

Preface

Welcome to PowerCenter Connect, Informatica’s family of packaged software products that helps you extract data and metadata from ERP and other third-party applications.

PowerCenter Connect for SAS is a natural extension to the open architecture of PowerCenter, which supports data extraction from a wide variety of operational data sources. PowerCenter Connect for SAS lets you directly extract data from SAS, transform the data according to your business rules, and load data into SAS or data warehouses.

xi

About This Book

This book describes the installation, configuration and use of PowerCenter Connect for SAS. It is intended as a reference for those maintaining the installation and for those working with SAS sources and/or targets in PowerCenter as a developer of mappings and workflows.

The material in this book is also available online.

Document ConventionsThis guide uses the following formatting conventions:

If you see… It means…

italicized text The word or set of words are especially emphasized.

boldfaced text Emphasized subjects.

italicized monospaced text This is the variable name for a value you enter as part of an operating system command. This is generic text that should be replaced with user-supplied values.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

Warning: The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure.

monospaced text This is a code example.

bold monospaced text This is an operating system command you enter from a prompt to run a task.

xii Preface

Other Informatica Resources

In addition to the product manuals, Informatica provides these other resources:

♦ Informatica Customer Portal

♦ Informatica web site

♦ Informatica Developer Network

♦ Informatica Knowledge Base

♦ Informatica Technical Support

Visiting Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

Visiting the Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Visiting the Informatica Developer Network You can access the Informatica Developer Network at http://devnet.informatica.com. The Informatica Developer Network is a web-based forum for third-party software developers. The site contains information about how to create, market, and support customer-oriented add-on solutions based on interoperability interfaces for Informatica products.

Visiting the Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

Obtaining Technical SupportThere are many ways to access Informatica Technical Support. You can contact a Technical Support Center by using the telephone numbers listed the following table, you can send email, or you can use the WebSupport Service.

Preface xiii

Use the following email addresses to contact Informatica Technical Support:

♦ [email protected] for technical inquiries

♦ [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

Toll Free 877 463 2435

Standard RateUnited States: 650 385 5800

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

Toll Free Australia: 00 11 800 4632 4357Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

xiv Preface

C h a p t e r 1

Understanding PowerCenter Connect for SAS

This chapter includes the following topics:

♦ Overview, 2

♦ SAS Architecture, 3

♦ User Authentication, 4

1

Overview

PowerCenter Connect for SAS is an extension to PowerCenter that facilitates the use of SAS Data Objects in the data integration processes. It seamlessly integrates with the PowerCenter Client and the PowerCenter Integration Service.

PowerCenter Connect for SAS consists of the following components:

♦ Repository. Extends the repository so it can store SAS metadata.

♦ Client. Extends the PowerCenter Client capabilities to facilitate the registration and use of SAS Data Objects.

♦ Server. Adds a dedicated reader that implements the actual reading of data from SAS.

♦ Communication (SPI Server). Takes care of all tasks that are requested from the machine hosting the SAS Data Objects in question.

2 Chapter 1: Understanding PowerCenter Connect for SAS

SAS Architecture

The central component of the architecture for PowerCenter Connect for SAS is the communication component, also known as the SPI Server. The SPI Server is a multi-threading TCP/IP listener service. It handles requests from the Designer and from sessions started from the PowerCenter Integration Service.

When import a SAS source or target definition, the client component requests the metadata from the SPI Server. The SPI Server starts a SPI session to retrieve the information from SAS, then passes it to the client component. When you save the SAS source or target definition, the repository component helps save it to the PowerCenter repository.

When you run a workflow that uses a SAS source or target, the Integration Service uses the server component to start a session with the SPI Server. The SPI Server accesses SAS data and passes it back to the server component for processing.

Figure 1-1 shows PowerCenter integration with SAS:

Figure 1-1. PowerCenter Integration with SAS

SAS Architecture 3

User Authentication

User authentication is required to connect to an SPI Server.

UsersThere are two defined users. It is not possible to add or remove users. The role of the users is as follows (case sensitive):

♦ sasuser. Used to connect to the SPI Server to get table metadata when importing sources or targets with the Designer. Also used to request access to SAS data.

♦ Administrator. Used to remotely stop the SPI Server. For more information, see “Configuring the Communication Component” on page 13.

Changing PasswordsAfter installation, the default passwords are set. You can change passwords locally only. To change a password, use the SPI Server Configuration tool. For more information, see “Configuring the Communication Component” on page 13.

4 Chapter 1: Understanding PowerCenter Connect for SAS

C h a p t e r 2

Installation and Configuration


♦ Overview, 6

♦ Installing on Windows, 7

♦ Installing the Client Component, 9

♦ Installing the Repository Component, 10

♦ Installing the Server Component, 12

♦ Installing and Configuring the Communication Component, 13

♦ Configuring a SAS Connection, 16

5

Overview

Before using PowerCenter Connect for SAS, you need to install and configure the components. First, decide what to install on which machine. For more information about the components and how they work together, see “Understanding PowerCenter Connect for SAS” on page 1.

Table 2-1 describes installation guidelines based on the tasks you want each machine to perform:

For more information about installation and configuration, see the specialized section for the installation of each component.

Table 2-1. Installation Guidelines and Prerequisites

Tasks and functions performed on this machine... Component Requirements

Run the Repository Service Repository Component

Repository Service installed.

Register SAS Data Objects and design mappings using the Designer

Client Component Designer installed. Repository component installed in repository.

Run workflows and sessions processing SAS Data Objects

Server Component Integration Service installed. Repository component installed in repository.

Define sessions processing SAS Data Objects using Workflow Manager

None Repository component installed in repository.

Submit and monitor workflows and sessions processing SAS Data Objects using Workflow Manager/Monitor

None Integration Service installed. Repository component installed in repository.

Hosts SAS Data Objects to be accessed by PowerCenter

Communication Component

SAS installed.

6 Chapter 2: Installation and Configuration

Installing on Windows

Use the following procedure to install PowerCenter Connect for SAS on Windows.

To install components on a Windows machine:

1. Launch setup.exe on the installation CD.

2. Enter the installation key and click Next.

3. Choose a directory for the PowerCenter Connect for SAS Installation.

This directory is for uninstall scripts and online help files. Plug-in components are installed in the appropriate Informatica component installation directories.

4. Click Next.

5. Select the components to install on this machine, and click Finish.

Installing on Windows 7

For Windows Client workstations, select Compact Installation, and install only the client component.


Installing the Client Component

Before you install the client component of PowerCenter Connect for SAS, make sure the PowerCenter 8.1.1 Client is installed on the machine.

The client component is installed by running the Setup program. Just step through the screens of the Setup Wizard.

Installing the Client Component 9

Installing the Repository Component

Before installing the repository component of PowerCenter Connect for SAS, install the PowerCenter Services and create a repository.

Complete the following steps to install the repository component of PowerCenter Connect for SAS:

1. Install the plug-in.

2. Register the plug-in in the repository.

Installing on WindowsUse the following procedure to install and register the repository component on Windows.

To install the repository component on Windows:

1. On the machine that runs the Repository Service, run setup.exe from the installation CD and choose the Repository Component from the list of components to install.

This installs tbsaspi.xml in the Plugin directory of the Repository Service installation.

2. To register the plug-in, log in to the PowerCenter Administration Console.

3. Run the Repository Service in exclusive mode.

4. In the Navigator, select the Repository Service to which you want to add the plug-in.

5. Click the Plug-ins tab.

6. Click the link to register a Repository Service plug-in.

7. On the Register Plugin for <Repository Service> page, click the Browse button to locate the plug-in file.

8. Enter the repository user name and password.

9. Click OK.

The Repository Service registers the plug-in with the repository. The results of the registration operation appear in the activity log.

10. Run the Repository Service in normal mode.

For more information about registering plug-ins, see the PowerCenter Administrator Guide.


Installing on UNIXUse the following procedure to install the repository component on UNIX.

To install the repository component on UNIX:

1. Run the install script from the installation CD.

2. Follow the instructions and choose Install Repository Plugin.

This installs tbsaspi.xml in the Plugin directory of the Repository Service installation.

3. To register the plug-in, log in to the PowerCenter Administration Console.

4. Run the Repository Service in exclusive mode.

5. In the Navigator, select the Repository Service to which you want to add the plug-in.

6. Click the Plug-ins tab.

7. Click the link to register a Repository Service plug-in.

8. On the Register Plugin for <Repository Service> page, click the Browse button to locate the plug-in file.

9. Enter the repository user name and password.

10. Click OK.

The Repository Service registers the plug-in with the repository. The results of the registration operation appear in the activity log.

11. Run the Repository Service in normal mode.

You can also register the plug-in using pmrep. For information on pmrep, see the PowerCenter Command Line Reference.

Installing the Repository Component 11

Installing the Server Component

Before installing the server component of PowerCenter Connect for SAS, install the PowerCenter Services.

Installing on WindowsTo install the server component on Windows, run setup.exe from the installation CD and select Server Component from the list of components.

Installing on UNIXTo install the server component on UNIX, run the install script from the installation CD and choose Install Server Plugin. Use the same login that you used to install the PowerCenter Services.


Installing and Configuring the Communication Component

Install the communication component, also known as the SPI Server, on the machine that runs the SAS environment that you want to use.

The communication component usually runs on a machine with no PowerCenter components installed. Because the communication component does not have a connection to the PowerCenter repository, its configuration is stored locally.

Installing the Communication Component on WindowsIf you have an existing version of the communication component, uninstall the component.

To install the communication component on Windows, run setup.exe from the installation CD and select SAS Communication Component from the list of components. The communication component installs as a Windows Service. For information about configuring the start-up settings for this service, see “Configuring the Communication Component on Windows” on page 14.

Installing the Communication Component on UNIXInstall the communication component using a login with authorization to start SAS and to access the SAS data you want to read or write. The Integration Service uses this login to access SAS data.

To install the communication component on UNIX, run the install script from the installation CD. Choose a directory where you want this component to be installed. Follow the instructions and choose Install SAS Communication Component.

Two files are installed: the spiserver executable and the spiserver.cfg configuration file. For information about configuring the communication component, see “Configuring the Communication Component on UNIX” on page 15.

Configuring the Communication ComponentTo configure the communication component, you use a configuration tool to maintain the spiserver.cfg configuration file. The configuration file is located in the SPI Server Working Directory. On Windows, this is the installation path you chose when you installed PowerCenter Connect for SAS. On UNIX, this is the current working directory of the spiserver process, which is the directory from where spiserver was started.

Installing and Configuring the Communication Component 13

Configuring the Communication Component on WindowsTo start the configuration tool on Windows, click SPI Server Configuration from the Start menu.

Figure 2-1 shows the Windows configuration dialog box:

Use this dialog box to configure the port that the SPI Server will listen from, the location of the SPI Server log file, and the SPI Server passwords. For more information, see “User Authentication” on page 4.

Enter the PowerCenter Connect for SAS License Key (five groups of four characters).

In addition, you must configure the actual SAS environment. In Working Directory Path, enter the directory from which SAS runs. In Autoexec Name, enter the file name that SAS uses as its initialization file. You can use this initialization file to assign SAS Library Names or SAS Libnames that must be accessible by both Designer and the PowerCenter sessions accessing SAS data. The following is a sample SAS Autoexec file:

/*

Sample SAS autoexec file

*/

LIBNAME whdata 'W:\data\saswhdata' ;

LIBNAME oltp 'W:\data\sales\2003Q1' ;

For valid LIBNAME syntax and options, see the SAS documentation.

Figure 2-1. SPI Server Configuration for Windows


Configuring the Communication Component on UNIXTo start the configuration tool on UNIX, enter ./spiconfig on the shell prompt in the SPI Server installation directory.

Figure 2-2 shows the UNIX configuration dialog box:

Choose an option you want to change. The configuration tool prompts you for a new value.

Starting the Communication Component on WindowsOn Windows, SPI Server runs as a Windows Service called The Bridgers SPI Server. You can start and stop this service in the following ways:

♦ Set Startup mode to manual. Start and stop the service as needed.

♦ Set Startup mode to automatic. The service starts automatically when Windows starts.

♦ From a Windows command line or script file, run the command net start “the bridgers spi server” or net stop “the bridgers spi server.”

Starting the Communication Component on UNIXOn UNIX, SPI Server is an executable that runs as a daemon when it is started. It does not change the current user, but it does detach from the terminal and from the current shell so you can safely end the shell and terminal without causing SPI Server to stop.

♦ To start, go to the directory where SPI Server is installed and issue the command spiserver. Check the SPI Server log file (see configuring SPI Server for location) to check if the server started successfully.

♦ To stop, issue the command spiserver stop <host> <portnumber> <administrator password>. For more information on passwords, see “User Authentication” on page 4.

♦ You can build an init script to start SPI Server automatically during system boot. See your system administrator or contact The Bridgers for assistance if needed.

Note: If SPI Server does not shut down normally, it might not restart properly. If this happens, remove the SPI Server lock file in the SPI Server working directory, and restart the SPI Server.

Figure 2-2. SPI Server Configuration for UNIX

Installing and Configuring the Communication Component 15

Configuring a SAS Connection

Configure a SAS connection before running SAS sessions. The Integration Service uses the SAS connection to access SAS data needed for the session. After you register a SAS connection, you can use it when configuring SAS sessions.

To configure a SAS connection:

1. From the Workflow Manager, click Connections > Relational.

2. Click Add, select SAS, and click OK.

The Connection Object Definition dialog box appears.

3. Enter the following SAS connection properties:

Table 2-2. SAS Connection Properties

Property Required/Optional Description

Name Required Name of SAS connection.

Host Required Host name of the machine running the SPI Server.

Port Required Port number of the machine running the SPI Server. Must correspond to the port number used in configuring the SPI Server. For information about configuring the SPI Server, see “Configuring the Communication Component” on page 13.

User Name Required Login used to access SAS data. Use “sasuser”. For more information about users, see “User Authentication” on page 4.

Password Required Password for the SAS user.


C h a p t e r 3

Working with SAS Sources


♦ Creating a SAS Source Definition, 18

♦ Editing a SAS Source Definition, 19

17

Creating a SAS Source Definition

You can manually create a SAS source definition. Select SAS as the database type when you manually create the source definition.

You can also import a SAS Data Object as a source definition.

To import a SAS source definition:

1. In the Source Analyzer, click Sources > Import SAS Source.

The Import SAS Source dialog box appears.

2. Select the SAS Server you want to use and enter the password for user “sasuser.”

For more information about sasuser, see “Configuring the Communication Component” on page 13.

3. Click Connect.

You can add or change SAS server definitions by clicking Reconnect.

4. Expand the Library nodes to access tables and views and select the table or view you want to import.

5. Click OK.

18 Chapter 3: Working with SAS Sources

Editing a SAS Source Definition

You can edit a SAS source definition just like other source definitions.

Table AttributesMost table attributes are accessed through the Rename button on the Table tab:

♦ Table Name. Corresponds with the name of the table to read from SAS.

♦ Database Name. Constitutes a logical grouping of data objects in the Designer. After importing a SAS table, the value of this attribute is the name of the SAS Library the table was imported from.

♦ Business Name. Corresponds with the SAS Label assigned to the table.

The following attributes can be accessed through the Metadata Extensions tab.

♦ LibraryName. Holds the actual Library Name from which the SAS table is read. The LibraryName can be overruled in the session. For more information, see “Editing a SAS Session” on page 28.

♦ Whereclause. Lets you specify a selection of rows from the SAS Source. This Whereclause results in a WHERE statement in SAS: WHERE Whereclause. For more information about whereclauses in SAS, see the SAS documentation.

Column AttributesYou can access the following column attributes on the Columns tab:

♦ Column Name. Corresponds with the name of the column in the SAS table.

♦ Precision and Scale. Determine how the data is represented in the mapping, and also how the data is transported from SAS.

♦ Data Type. Indicates how the data should be interpreted and processed in the mapping. For more information about SAS datatypes, see “SAS Datatypes and Formats” on page 35.

Editing a SAS Source Definition 19

20 Chapter 3: Working with SAS Sources

C h a p t e r 4

Working with SAS Targets


♦ Creating a SAS Target Definition, 22

♦ Editing a SAS Target Definition, 23

♦ Configuring Indexes and Keys, 24

♦ Working with Field Attributes, 25

♦ Configuring Load Types, 26

21

Creating a SAS Target Definition

You can manually create a SAS target definition. Select SAS as the database type when you manually create the target definition.

You can also import a SAS Data Object as a target definition.

To import a SAS target definition:

1. In the Target Designer, click Targets > Import SAS Target.

The Import SAS Target dialog box appears.

2. Select the SAS Server you want to import the target definition from and click Connect.

You can add or change SAS server definitions by clicking Reconnect.

3. Expand the Library nodes to access tables and views, and select the table or view you want to import.

4. Click OK.

22 Chapter 4: Working with SAS Targets

Editing a SAS Target Definition

You can edit a SAS target as you would other target definitions.

Table AttributesMost table attributes are accessed through the Rename button on the Table tab:

♦ Table Name. Corresponds with the name of the table to read from SAS.

♦ Database Name. Constitutes a logical grouping of data objects in the Designer. After importing a SAS table, the value of this attribute will be the name of the SAS Library the table was imported from.

♦ Business Name. Corresponds with the SAS Label assigned to the table.

You can access the Library Name attribute through the Metadata Extensions tab. The LibraryName attribute holds the actual Library Name from which the SAS Table will be read.

Column AttributesYou can access the following column attributes on the Columns tab:

♦ Column Name. Corresponds with the name of the column in the SAS table.

♦ Precision and Scale. Determine how the data is represented in the mapping, and also how the data is transported from SAS.

♦ Data Type. Indicates how the data should be interpreted and processed in the mapping. For more information on SAS datatypes, see “SAS Datatypes and Formats” on page 35.

Edit ing a SAS Target Definition 23

Configuring Indexes and Keys

You can create and configure indexes and key indexes for SAS target definitions.

Configuring IndexesUse the following procedure to create, edit, or delete indexes from SAS target definitions.

To create, configure, or delete indexes:

1. In the Target Designer, edit a target definition and click the Indexes tab.

2. Optionally, add, delete and reorder indexes in the left pane, and add, delete and reorder fields for each index in the right pane.

3. To configure a unique index, check Unique.

4. Optionally, describe the index in the Description field.

Configuring a Key IndexOne of the indexes defined for the SAS target can be defined as the Key Index by checking the Key box in front of the Index Name. The key index designates the key identifying each row to be used in a Update Else Insert Load.

Check to configure a unique index.


Working with Field Attributes

You can edit SAS target field attributes by editing the target definition. You can edit the following SAS field attributes:

♦ Formats

♦ Informats

♦ Length for a SAS Target Object

The length can not be changed directly for String fields. The length follows the precision value on the Columns Tab for String Fields.

To edit field attributes, open the target definition. On the Field Attributes tab, select the attribute you want to edit and click Edit.

Figure 4-1 displays the Field Attributes tab:

Figure 4-1. SAS Target Field Attributes Tab

Working with Field Attributes 25

Configuring Load Types

Load Type is a SAS target property that specifies how the Integration Service writes to the physical SAS Data Object.

You can use three load types:

♦ Full load

♦ Append load

♦ Update Else Insert load

You can specify load type when you edit a session. For more information about configuring load type in the session properties, see “Editing a SAS Session” on page 28.

Full LoadBy default, the Integration Service uses full load when writing to a SAS dataset in the SAS environment. When you use full load, a new SAS dataset is created from the output, overwriting an existing dataset if present. Any attributes defined for the target definition are applied to the SAS dataset. These include Indexes and (In)Formats. For more information about indexes, see “Configuring Indexes” on page 24. For more information about Informats, see “Column Attributes” on page 23.

Append LoadThe effect of an Append Load is that the output will be appended to an existing SAS dataset. If the layout of the target definition and the existing SAS dataset do not match, an error condition will occur in the SAS processing and this will be reported in the Session Log.

Update Else Insert LoadTo update row values by an identifying key, choose the Update Else Insert Load. A proper key must be defined for the existing SAS dataset to which the output is to be applied. For more information about keys, see “Configuring a Key Index” on page 24.


C h a p t e r 5

Working with SAS Sessions

This chapter includes the following topic:

♦ Editing a SAS Session, 28

27

Editing a SAS Session

When you edit a SAS session, you can configure SAS source and target properties. You can configure the following SAS properties in a session:

♦ SAS Library Name. Overrule the library name associated with the SAS source or target when necessary. By default, the Integration Service uses the library name configured on the Metadata Extensions tab of the source or target.

♦ Load Type. Configure a load type for the session. For more information about load types, see “Configuring Load Types” on page 26.

♦ Compress Option. Determine whether SAS compresses target data. Used only in sessions writing to SAS targets using a full load type. For more information about SAS compression, see the SAS documentation.

To edit SAS session properties:

1. In the Workflow Manager, open a SAS session task.

The Task Properties dialog appears.

2. To edit SAS source properties, click the Sources tab.

To edit SAS target properties, click the Targets tab.

3. Click the Properties tab.

4. Configure the properties you want to edit and click OK.

28 Chapter 5: Working with SAS Sessions

C h a p t e r 6

Advanced Features


♦ Reading SAS Character Columns with Binary Zeros, 30

♦ Session Identification Attributes, 31

♦ Removing Leading Spaces in Text Fields, 32

29

Reading SAS Character Columns with Binary Zeros

SAS allows binary zero bytes inside character columns. In PowerCenter, characters with binary zeros are not allowed. These PowerCenter transformation logic cannot process these fields.

However, you can enable a check for binary zeros to be replaced by NULL characters before the Integration Service passes the data to the PowerCenter transformation logic.

To enable binary zeros to be replaced by NULL characters, assign the macro variable CHCKNLLS in the SAS autoexec file. Add the following line in the SAS autoexec file:

%let CHCKNLLS=YES;

For more information on the SAS autoexec file, see “Installing and Configuring the Communication Component” on page 13.

30 Chapter 6: Advanced Features

Session Identification Attributes

Two identifying attributes of a session are passed to the environment where SAS runs. These attributes are the name of the PowerCenter Integration Service that runs the corresponding workflow and the name of the PowerCenter connection used to access the SAS machine. This is useful for conditional initialization logic in the SAS autoexec script.

These attributes are exposed to the SAS process through the system variables TBPC_PMSERVER_NAME and TBPC_CONNECTION_NAME. To use these system variables in the SAS autoexec script, they can be retrieved using the SAS function sysget().

For example:

/* Store system variables into SAS macro variables: */

srvname = sysget("TBPC_PMSERVER_NAME");

conname = sysget("TBPC_CONNECTION_NAME");

/* Use the SAS macro variables to code logic: */

.............

.............

/* End of logic */

For more information about the SAS autoexec file, see “Installing and Configuring the Communication Component” on page 13.

When a connection to the SAS machine is initiated from the Designer, the system variables contain no meaningful information. In this case their values default to “_NONE_”.

Session Identificat ion Attributes 31

Removing Leading Spaces in Text Fields

In older versions of PowerCenter Connect for SAS (version 3.2.3.0 and before) leading spaces in text fields in a SAS source were removed. Also when writing to a SAS target leading spaces were trimmed off.

You can add the following statement to the SAS autoexec file to remove leading spaces:

%let TRMLDSPC=YES ;

32 Chapter 6: Advanced Features

A p p e n d i x A

SPI Server Configuration Options

This appendix includes the following topic:

♦ Configuration Parameters, 34

33

Configuration Parameters

Section Parameter Description Example

ServerConfig Portnumber TCP/IP port number for SPI Server listener process. 11080

ServerConfig SasAppPath Full path to SAS executable. c:\progs\sas\V8\sas.exe

ServerConfig SasWorkingDir SAS Working Environment directory path. d:\spi\work

ServerConfig SasAutoExec Autoexec file containing library definitions. autoexec.sas

ServerConfig LogFile Specifies location of the server log file. d:\spi\spiserver.log

ServerConfig SasLogMax Maximum number of SAS log-files stored by the server. If the value is not set then 256 is used as a default, the minimum value for this parameter is 12.

256

Authentication sasuser Encypted password. 89FD2A5347541028C9FA9A26A9057FF7

Authentication administrator Encypted password. 200CEB26807D6BF99FD6F4F0D1CA54D4

34 Appendix A: SPI Server Configuration Options

A p p e n d i x B

SAS Datatypes and Formats

This appendix includes the following topic:

♦ SAS Datatypes and Formats, 36

35

SAS Datatypes and Formats

SAS stores all its data using two datatypes:

♦ Numeric

♦ Character

You can specify additional type information by using SAS formats. SAS formats determine how the data will actually be presented to the end user.

Character DataThe length attribute from SAS specifies the number of characters making up the column. PowerCenter uses this value as the scale attribute in the source definition.

Numeric DataFor numeric data, PowerCenter looks at the SAS format assigned to the column to determine the right precision and scale values. For example, if the SAS format of a numeric column is 10.2, this means that the column will be presented using 10 positions in total, including a decimal point and two digits after the decimal point. This is translated to a precision of 9 and a scale of 2.

Note: If no format is assigned to a numeric column, PowerCenter assigns an arbitrary precision of 10 and scale of 0 when this source definition is imported. This may not be adequate for holding the data. You should adjust precision and scale manually to get a definition for the column that is adequate for holding the data you expect for this column.

Date, Time, and Datetime DataAll Date, Time and Datetime columns are represented in SAS by numeric columns. The format of the column usually indicates the intended use of this numeric column, but supported formats differ between SAS releases and localized versions. For this reason, when importing a SAS Data Object, PowerCenter does not attempt to determine whether a numeric column should be interpreted as a Date value, Time value or Datetime value. These datatypes are available in a SAS source definition, but you must manually assign them. The necessary conversion will then be done automatically.

For more information about SAS datatypes and formats, see the SAS documentation.

36 Appendix B: SAS Datatypes and Formats

A p p e n d i x C

Error Messages

This appendix includes the following topics:

♦ Client Messages, 38

♦ Integration Service Messages, 43

♦ Communication Component Messages, 45

37

Client Messages

Nothing has been selected for import.Cause: No items have been selected in the table tree.

Action: Select an item.

Can not create table <table name>.Cause: The table cannot be defined in the repository.

Action: Look for accompanying messages.

Can not create field <field name>.Cause: The field cannot be defined in the repository.

Action: Look for accompanying messages.

Failed to add menu item <item name>.Cause: Internal error.

Action: Contact Informatica Technical Support.

Can not initialize Windows Sockets.Cause: The Windows network environment is not properly configured.

Action: Contact your Windows system administrator.

Can not connect to the SPI Server, host = <host name>, port = <port number>, error = <error code>.Cause: SPI Server TCP/IP port is not accessible.

Action: Check the communication component and network configuration. Make sure SPI Server is running.

Failed to close the session.Cause: Unexpected error.

Action: Check the environment for a temporary network or operating system failure.

Session open request failed, host = <host name>, port = <port number>, error = <error code>.Cause: SPI Server is unable to initialize a session.

Action: Check the SPI Server log for additional information.

Failed to retrieve session ID.Cause: Unexpected error.

38 Appendix C: Error Messages


Failed to retrieve metadata, error code = <error code>.Cause: SAS does not start.

Action: Check the SAS environment. Try to start SAS manually, and check the error messages from SAS.

Library information is not available.Cause: The SAS session did not return the expected metadata.

Action: Check the SAS log for error conditions.

No information available about table <table name>.Cause: The SAS session did not return the expected metadata.

Action: Check the SAS log for error conditions.

Received data has not valid format or the imported table/view has no columns.Cause: Unexpected error.

Action: Check the SAS environment and the assigned library or table for abnormal conditions.

No selection has been made.Cause: You attempted to edit a field attribute before selecting an attribute.

Action: Make a selection before attempting the edit.

The field can not be empty.Cause: Field left empty while trying to add an SPI Server to the server list.

Action: Enter a value in the field.

The port number is not valid.Cause: Invalid value for port number while adding an SPI Server.

Action: Specify a valid TCP/IP port number.

Failed to load config file: <file name>, the file doesn’t exist or it is not valid config file.Cause: The configuration file is not accessible.

Action: Make sure the configuration file exists and is accessible

Failed to access config file data, wrong file format.Cause: The configuration file is accessible, but the content is invalid.

Action: Check the configuration file.

Client Messages 39

Failed to save config file: <file name>.Cause: The configuration file could not be saved.

Action: Check the file system.

Failed to retrieve SAS session log, error code = <error code>.Cause: The SAS error log file could not be retrieved from the SAS machine.

Action: Check the existence of the SAS log file.

Failed to open the help file: <file name>.Cause: Help file could not be found or could not be opened.

Action: Check the client installation.

Failed to retrieve the registry key: <key name>.Cause: The installation of PowerCenter has not been performed properly.

Action: Reinstall PowerCenter.

Index name can not be empty.Cause: You tried to define an index without giving it a name.

Action: Supply a name for the index.

This index name has already been used. Please enter a unique name.Cause: You tried to define an index with a name that already exists.

Action: Choose a unique name for the index.

All available columns have already been added to this index.Cause: You tried to add a column to an index where no columns are available

anymore.

Action: No action.

The field <field name> has been removed from the table, it will be removed from the index <index name>.Cause: You removed a column from a table that was used in an index.

Action: The column is automatically removed from the index. No action.

The index <index name> has no fields and will be removed.Cause: An index has become invalid because all of its columns were removed.

Action: No action.

Failed to load index information from metadata.Cause: Internal error.



The metadata field <field name> does not correspond to any table field.Cause: Internal error.


The text contains characters (<characters>) that are not allowed to use.Cause: Special characters were used where this is not allowed (e.g. in an index name).

Action: Remove the special characters.

The specified length of a numeric field is out of range (a valid value for SAS must be in the range from <value> to <value>). It will be set to the default value.Cause: You specified an invalid field length.

Action: Specify a valid length or accept the default value.

Spaces or tabs are not allowed in the index name. Cause: You used spaces or tabs in an index name.

Action: Remove spaces and tabs from the index name.

SPI Server login failed because of wrong user name or password.Cause: Authentication to SPI Server failed.

Action: Use the right credentials to connect to SPI Server. For more information, see “Configuring the Communication Component” on page 13.

Enter a password please.Cause: A password has not been entered to connect to the SPI Server.

Action: Enter a valid password.

Version mismatch is detected. The client version is not compatible with a server you are trying to connect to.Cause: The client component of PowerCenter Connect for SAS is not of the same

version as the communication component.

Action: Make sure you install both components from the same version.

The repository is not licensed for PowerConnect for SAS, or the license has expired.Cause: There is no valid license for the use of PowerCenter Connect for SAS.

Action: Install the proper license keys.

Client Messages 41

SAS data viewer requires .NET runtime. It appears that .NET runtime is not installed on this system, continue anyway?Cause: .NET runtime may not be available on your system.

Action: Install Microsoft .NET runtime environment.

Failed to launch SAS data viewer, error code = <error code>.Cause: .NET runtime may not be available on your system.

Action: Install Microsoft .NET runtime environment.


Integration Service Messages

Only one source per source qualifier is supported.Cause: Joining SAS tables in SAS is not supported.

Action: Use a Joiner transformation to join SAS tables.

Can not connect to the SPI Server, host = <host name>, port = <port number>, error = <error code>.Cause: SPI Server TCP/IP port is not accessible.

Action: Check the communication component and network configuration. Make sure SPI Server is running.

Session open request failed, host = <host name>, port = <port number>, error = <error code>.Cause: SPI Server is unable to initialize a session.

Action: Check the SPI Server log for additional information.

Failed to retrieve a session ID.Cause: Internal error.


Failed to close the session.Cause: Internal error.


Requested not supported data type, field = <field name>, data type = <data type enumeration>.Cause: Internal error.


Failed to flush PowerCenter buffer, buffer capacity = <buffer capacity>, records to flush = <number of records>.Cause: Internal error.


Failed to retrieve data, error code = <error code>.Cause: SAS does not start.

Action: Check the SAS environment. Try to start SAS manually and check the error messages from SAS.

Integration Service Messages 43

Failed to retrieve SAS session log, error code = <error code>.Cause: The SAS log file cannot be read and/or passed by SPI Server.

Action: Check the existence and permissions of the SAS log file.

SAS code generation failed, not supported data type: <data type enumeration>.Cause: Internal error.


SPI Server login failed because of wrong user name or password.Cause: Authentication to SPI Server failed.

Action: Use the right credentials to connect to SPI Server. For more information, see “Configuring the Communication Component” on page 13.

Data field length exceeds the maximum value.Cause: The value for the length of the field is larger than that allowed by SAS.

Action: Specify a valid length. Check SAS documentation for valid lengths.

A version mismatch is detected. The client version is not compatible with a server you are trying to connect to.Cause: The reader or writer component of PowerCenter Connect for SAS is not of the

same version as the communication component.



Communication Component Messages

Unknown message received.Cause: Internal error.


Failed to start SAS session, errno = <error message>.Cause: SAS could not be started.

Action: Check the SAS installation and the communication component configuration.

SAS session wait failed.Cause: Internal error.


SAS session time out expired.Cause: The SAS process does not end.

Action: Check the SAS log for possible problems.

Failed to receive data from SAS, errno = <error message>.Cause: SAS does not start.


Failed to send data to SAS, errno = <error message>.Cause: SAS does not start.


Unexpected command received, message ID = <message ID>.Cause: Unexpected error.


Failed to open SAS log file <file name>.Cause: The SAS log file could not be opened.

Action: Check the file and directory permissions and the communication component configuration.

Failed to generate SAS dummy log file.Cause: No empty SAS log file could be created.

Communication Component Messages 45

Action: Check the file and directory permissions and the communication component configuration.

Failed to stop SPI Server, errno = <error message>.Cause: SPI Server could not be stopped using the spiserver command.

Action: Make sure you specified the right hostname and port number.

Failed to create SAS data code file <file name>.Cause: The indicated file could not be created in the Working directory as specified in

the communication component configuration.

Action: Check the configuration and the directory permissions.

Failed to write data to SAS data code file <file name>.Cause: The indicated file could not be written to.

Action: Check file permissions.

Failed to set SAS working directory <directory path>.Cause: Could not set the indicated path as the current working directory.

Action: Check the existence of the directory and its permissions and the communication component configuration.

A version mismatch is detected, the client connection has been rejected.Cause: The Reader, Writer, or Client Component of PowerCenter Connect for SAS is

not of the same version as the communication component.



I n d e x

AAdministrator user (SAS)

definition 4append load (SAS)

load type 26architecture (SAS)

SAS integration with PowerCenter 3autoexec file (SAS)

sample 14

Bbinary zeros (SAS)

reading 30business name (SAS)

editing in targets 23editing sources 19

CCharacter (SAS)

datatype 36character columns (SAS)

reading binary zeros 30client component (SAS)

description 2, 3installing 9

requirements 6column attributes (SAS)

editing in sources 19in target definitions 23

column name (SAS)editing in sources 19in target definitions 23

command (SAS)spiserver 15

communication component (SAS)configuring 13description 2installing 13requirements 6starting on UNIX 15starting on Windows 15

Compress option (SAS)configuring in session 28

Ddatabase name (SAS)

editing in targets 23editing sources 19

datatypes (SAS)editing in sources 19in target definitions 23SAS 36

47

datetime (SAS)datatype 36

Ffield attributes (SAS)

editing in target definitions 25formats (SAS)

in target definitions 25SAS 36

full load (SAS)load type 26

Iindexes (SAS)

in SAS target definitions 24informats (SAS)

in target definitions 25integration (SAS)

SAS with PowerCenter 3

Kkey indexes (SAS)

configuring 24

Lleading spaces (SAS)

removing 32length (SAS)

in target definitions 25library name (SAS)

overwriting in session 28LibraryName (SAS)

editing sources 19load types (SAS)

configuring in session 28for SAS target definitions 26

Nnumeric (SAS)

datatype 36

Pprecision and scale (SAS)

editing in sources 19in target definitions 23

Rrepository component (SAS)

description 2installing 10requirements 6

requirements (SAS)for client component 6for communication component 6for repository component 6server component 6

SSAS connections (SAS)

registering 16SAS source definitions (SAS)

creating 18editing 19

SAS target definitions (SAS)column attributes 23configuring indexes 24configuring key indexes 24creating 22editing 23editing field attributes 25load types 26

SASautoexec file (SAS)sample 14

sasuser (SAS)definition 4

server component (SAS)description 2, 3installing 12requirements 6

sessions (SAS)editing SAS options 28

SPI Server (SAS)configuring 13description 2, 3starting on UNIX 15starting on Windows as a service 15user authentication 4

48 Index

spiserver (SAS)command 15

Ttable attributes (SAS)

editing 19editing targets 23

table name (SAS)editing in targets 23editing sources 19

time (SAS)datatype 36

UUNIX (SAS)

configuring the communication component 15installing the communication component 13installing the repository component 11installing the server component 12SPI Server settings 15starting the SPI Server 15

update else insert load (SAS)load type 26

users (SAS)authentication 4

WWhereclause (SAS)

editing sources 19Windows (SAS)

configuring the communication component 14installing PowerCenter Connect for SAS 7installing the communication component 13installing the repository component 10installing the server component 12starting the SPI Server service 15

Index 49

50 Index

powercenter connect 8.1.1 for sas user guide · informatica, “as-is”, without warranty of any...

Documents