conﬁguring adaptive server enterprise for unix...

Configuring Adaptive ServerTM Enterprisefor UNIX Platforms

Version 11.5.1

Document ID: 35823-01-1151-01Last Revised: March 1998

Copyright © 1989-1998 by Sybase, Inc. All rights reserved.

This publication pertains to Sybase database management software and to any subsequent release until otherwiseindicated in new editions or technical notes. Information in this document is subject to change without notice. Thesoftware described herein is furnished under a license agreement, and it may be used or copied only in accordancewith the terms of that agreement.

To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225,fax (617) 229-9845.

Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above faxnumber. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades areprovided only at regularly scheduled software release dates. No part of this publication may be reproduced,transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise,without the prior written permission of Sybase, Inc.

Sybase, the Sybase logo, PowerBuilder, Powersoft, Replication Server, S-Designor, SQL Advantage, SQL Debug,SQL SMART, Transact-SQL, VisualWriter are registered trademarks of Sybase, Inc. Adaptable WindowingEnvironment, Adaptive Server, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, AnswerBase,Application Manager, AppModeler, Backup Server, Client-Library, Client Services, CodeBank, Connection Manager,DataArchitect, Database Analyzer, DataExpress, Data Pipeline, DataWindow, DB-Library, Designor, DevelopersWorkbench, Dimensions Anywhere, Dimensions Enterprise, Dimensions Server, DirectCONNECT, Easy SQR,Embedded SQL, EMS, Enterprise CONNECT, Enterprise Manager, Enterprise SQL Server Manager, Enterprise WorkArchitecture, Enterprise Work Designer, Enterprise Work Modeler, EWA, Gateway Manager, GeoPoint, InfoMaker,InformationCONNECT, InternetBuilder, iScript, KnowledgeBase, MainframeCONNECT, Maintenance Express,MAP, MetaWorks, MethodSet, Movedb, Navigation Server Manager, Net-Gateway, NetImpact, Net-Library,ObjectCONNECT, ObjectCycle, OmniCONNECT, OmniSQL Access Module, OmniSQL Server, OmniSQL Toolkit,Open Client, Open ClientCONNECT, Open Client/Server, Open Client/Server Interfaces, Open Gateway, OpenServer, Open ServerCONNECT, Open Solutions, Optima++, PB-Gen, PC DB-Net, PC Net Library, PowerBuilt,PowerBuilt with PowerBuilder, PowerScript, PowerSocket, Powersoft Portfolio, PowerWare Desktop, PowerWareEnterprise, ProcessAnalyst, Replication Agent, Replication Driver, Replication Server Manager, Resource Manager,RW-Library, SAFE, SDF, Secure SQL Server, Security Guardian, SKILS, smart.partners, smart.parts, smart.script,SQL Anywhere, SQL Central, SQL Code Checker, SQL Edit, SQL Edit/TPU, SQL Remote, SQL Server, SQL Server/CFT, SQL Server/DBM, SQL Server Manager, SQL Server SNMP SubAgent, SQL Station, SQL Toolset, StarDesignor,Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Dimensions, Sybase Gateways, SybaseIQ, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench,SybaseWare, SyBooks, System 10, System 11, SystemTools, Visual Components, VisualSpeller, Warehouse WORKS,Watcom, Watcom SQL, Watcom SQL Server, web.sql, WebSights, WebViewer, WorkGroup SQL Server, XA-Library,XA-Server, and XP Server are trademarks of Sybase, Inc. 1/98

All other company and product names used herein may be trademarks or registered trademarks of their respectivecompanies.

Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) ofDFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.

Sybase, Inc., 6475 Christie Avenue, Emeryville, CA 94608.

Table of Contents

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Adaptive Server Enterprise Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Other Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 1: Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

New Functionality in Adaptive Server 11.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring for High-Availability Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2: Configuring the Operating System After Installation or Upgrade . . . . . . . . 17

Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17DSLISTEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18DSQUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using the stty Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Restoring Correct Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

File Descriptors and User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19For Digital UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19For HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20For NCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20For SGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Displaying Current Soft and Hard Limits . . . . . . . . . . . . . . . . . . . . . . . . 20Increasing the Soft Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Increasing the Hard Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

For Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Displaying Current Soft and Hard Limits . . . . . . . . . . . . . . . . . . . . . . . . 23Increasing the Soft Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Increasing the Hard Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Adjusting the Client Connection Timeout Period . . . . . . . . . . . . . . . . . . . . . . . . . 25

3

Table of Contents

For Digital UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25For HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26For IBM RS/6000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26For NCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26For Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Checking for Hardware Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27For Digital UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27For HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27For IBM RS/6000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27For NCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28For SGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28For Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Monitoring the Use of Operating System Resources . . . . . . . . . . . . . . . . . . . . . 28For Digital UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28For HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29For IBM RS/6000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29For NCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30For SGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30For Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30A Sample C Shell Maintenance Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Using Large Devices on HP-UX 10.20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3: Setting Up Communications Across a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

What Is an Interfaces File? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Creating an Interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Contents of an Interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Differences Between Client and Server Interfaces Files . . . . . . . . . . 35If Your Site Has Multiple Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

How Adaptive Server Uses an Interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

How a Client Uses an Interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Heterogeneous and Homogeneous Environments . . . . . . . . . . . . . . . . . . . . . . . . 37

Understanding the Format of the Interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . 39Format by Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Digital UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40IBM RS/6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Components of an Interfaces File Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Creating Interfaces Files for SPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4

Table of Contents

Interfaces File Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Utilities for Editing the interfaces File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Creating One Interfaces File for Multiple Installations . . . . . . . . . . . . . . . . . . . . 46Using dsedit or dscp to Create a Master Interfaces File . . . . . . . . . . . . . . . 46Using a Text Editor to Create a Master Interfaces File . . . . . . . . . . . . . . . 47

Configuring Interfaces Files for Multiple Networks . . . . . . . . . . . . . . . . . . . . . . . 47Configuring the Server for Multiple Network Handlers . . . . . . . . . . . . . 47

Sample interfaces Files for Multiple Network Handlers . . . . . . . . . . 48Configuring the Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Using One Network-Independent DSQUERY Name . . . . . . . . . . . . . 49Using Different DSQUERY Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring for Query Port Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 4: Modifying the Interfaces File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Using dsedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Starting dsedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Opening an Editing Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Adding, Viewing, and Editing Server Entries . . . . . . . . . . . . . . . . . . . . . . . . 58

Adding or Editing Network Transport Addresses. . . . . . . . . . . . . . . . 59Troubleshooting dsedit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

The dsedit Utility Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Error Message: “Unable to open X display”. . . . . . . . . . . . . . . . . . . . . . 61Cannot Add, Modify, or Delete Server Entries . . . . . . . . . . . . . . . . . . . 61

Using dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Starting dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Getting Help with dscp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Using a dscp Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Opening a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Listing Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Switching Between Open Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Closing a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Adding and Modifying Server Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Adding Server Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Modifying Server Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Copying Server Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Creating New Server Entries Within a Session By Copying. . . . . . 67Copying Entries Between Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Copying All Entries to a Different Session . . . . . . . . . . . . . . . . . . . . . . . 68

Listing Server Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Viewing Contents of Server Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5

Table of Contents

Deleting Server Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Exiting dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Quick Reference for dscp Utility Commands . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 5: Localization Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Localization Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Default Character Sets for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Changing the Default Character Set for Servers . . . . . . . . . . . . . . . . . . . . . 75Supported Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Using Unicode Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Loading the Unicode Conversion Tables. . . . . . . . . . . . . . . . . . . . . . . . . . 80Resizing the Unilib Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Activating Unicode Character Conversion. . . . . . . . . . . . . . . . . . . . . . . . 81Disabling Character Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Sort Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Available Sort Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Gathering Information About Collation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Ordering Query Results Based on Collation Behavior . . . . . . . . . . . 85Comparing Strings Based on Alternate Collation Rules . . . . . . . . . . 87

Configuring for Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Directories for Localization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

About the locales Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89About the charsets Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

About the locales.dat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Format of locales.dat File Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90How Client Applications Use locales.dat . . . . . . . . . . . . . . . . . . . . . . . . . . 91Editing the locales.dat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Language Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Installing a New Language Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Message Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Japanese Language Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Limitations of Hankaku Katakana Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Hankaku Katakana Conversion and Datatypes . . . . . . . . . . . . . . . . . . . . . . 94

Conversions Between Server and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Backup Server Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Conversions in a Heterogeneous Environment. . . . . . . . . . . . . . . . . . . . . . . 96Conversion Between Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Changing the Language, Character Set, or Sort Order . . . . . . . . . . . . . . . . . . . . 96

6

Table of Contents

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7

Table of Contents

8

About This Book

This guide, Configuring Adaptive Server for UNIX Platforms, providesinstructions for performing specific configuration tasks for Sybase®

Adaptive ServerTM Enterprise on the following platforms:

• Digital UNIX

• HP 9000 Series 800 HP-UX

• IBM RISC System/6000 AIX

• Silicon Graphics IRIX

• Sun Solaris 2.x (SPARC)

• NCR System MP-RAS

• UnixWare

The operating system release levels for these platforms on whichAdaptive Server is certified to execute is provided in the installationdocumentation for your platform.

This guide provides:

• An overview of the Adaptive Server infrastructure

• Instructions for reconfiguring certain attributes of your existingAdaptive Server, Backup ServerTM, and XP ServerTM to meet yourspecific needs

AudienceThis guide is written for Sybase System Administrators.

About This Book♦Note Before configuring Adaptive Server according to the instructions in this

book, you should have a newly installed or upgraded Adaptive Serveron your system. If you do not, follow the installation and upgradeinstructions in the installation documentation for your platform.

9

About This Book

This book contains the following chapters:

• Chapter 1, “Introduction,” presents an overview of the configurationchanges you might want to make to Adaptive Server after installingor upgrading the server.

• Chapter 2, “Configuring the Operating System After Installation orUpgrade,” describes operating system configuration issues.

• Chapter 3, “Setting Up Communications Across the Network,”describes the Interfaces file, which is named interfaces on UNIXplatforms.

• Chapter 4, “Modifying the Interfaces File,” provides reference andtask information about using the dsedit and dscp utilities to modify theinterfaces file.

• Chapter 5, “Localization Issues,” provides background informationabout Sybase’s localization support as well as task information forreconfiguring character sets, sort orders, and language modules.

Adaptive Server Enterprise DocumentsThe following documents comprise the Sybase Adaptive ServerEnterprise documentation:

• The Release Bulletin for your platform – contains last-minuteinformation that was too late to be included in the books.

A more recent version of the Release Bulletin may be available on theWorld Wide Web. To check for critical product or documentinformation that was added after the release of the product CD, useSyBooksTM-on-the-Web.

• The Adaptive Server installation documentation for your platform –describes installation and upgrade procedures for all Adaptive Serverand related Sybase products.

• The Adaptive Server configuration documentation for your platform– describes configuring a server, creating network connections,configuring for optional functionality, such as auditing, installingmost optional system databases, and performing operating systemadministration tasks.

• What’s New in Adaptive Server Enterprise? – describes the new featuresin Adaptive Server release 11.5, the system changes added to support

10

Adaptive Server Enterprise Documents

those features, and the changes that may affect your existingapplications.

• Navigating the Documentation for Adaptive Server – an electronicinterface for using Adaptive Server. This online document provideslinks to the concepts and syntax in the documentation that arerelevant to each task.

• Transact-SQL User’s Guide – documents Transact-SQL®, Sybase’senhanced version of the relational database language. This manualserves as a textbook for beginning users of the database managementsystem. This manual also contains descriptions of the pubs2 and pubs3sample databases.

• System Administration Guide – provides in-depth information aboutadministering servers and databases. This manual includesinstructions and guidelines for managing physical resources and userand system databases, and specifying character conversion,international language, and sort order settings.

• Adaptive Server Reference Manual – contains detailed information aboutall Transact-SQL commands, functions, procedures, and datatypes.This manual also contains a list of the Transact-SQL reserved wordsand definitions of system tables.

• Performance and Tuning Guide – explains how to tune Adaptive Serverfor maximum performance. This manual includes information aboutdatabase design issues that affect performance, query optimization,how to tune Adaptive Server for very large databases, disk and cacheissues, and the effects of locking and cursors on performance.

• The Utility Programs manual for your platform – documents theAdaptive Server utility programs, such as isql and bcp, which areexecuted at the operating system level.

• Security Administration Guide – explains how to use the securityfeatures provided by Adaptive Server to control user access to data.This manual includes information about how to add users to AdaptiveServer, administer both system-defined and user-defined roles, grantdatabase access to users, and manage remote Adaptive Servers.

• Security Features User’s Guide – provides instructions and guidelinesfor using the security options provided in Adaptive Server from theperspective of the non-administrative user.

11

About This Book

• Troubleshooting and Error Messages Guide – explains how to resolvefrequently occurring error messages and describes solutions to systemproblems frequently encountered by users.

• Component Integration Services User’s Guide – explains how to use theAdaptive Server Component Integration Services feature to connectremote Sybase and non-Sybase databases.

• Adaptive Server Glossary – defines technical terms used in theAdaptive Server documentation.

Other Sources of InformationUse the SyBooks and SyBooks-on-the-Web online resources to learn moreabout your product:

• SyBooks documentation is on the CD that comes with your software.The DynaText browser, also included on the CD, allows you to accesstechnical information about your product in an easy-to-use format.

See the Installation Guide in your documentation package forinstructions on installing and starting SyBooks.

• SyBooks-on-the-Web is an HTML version of SyBooks that you canaccess using a standard Web browser.

To use SyBooks-on-the-Web, go to http://www.sybase.com, andchoose Documentation.

ConventionsThe following style conventions are used in this manual:

• In a sample screen display, commands that you enter exactly asshown are shown in:

this font

• In a sample screen display, words that you should replace with theappropriate value for your installation are shown in:

this font

12

Conventions

• In the regular text of this document, the names of files and directoriesappear in italic type:

/usr/u/sybase

• The names of programs, utilities, procedures, and commands appearin bold type:

sybsetup

• Commands for both the C and Bourne shells are provided in thisdocument, when they differ. The initialization file for the C shell iscalled .cshrc. The initialization file for the Bourne shell is called.profile. If you are using a different shell, such as the Korn shell, seeyour shell-specific documentation for the correct command syntax.

Table 1 shows the conventions for syntax statements in this manual.

Table 1: SQL syntax conventions

Key Definition

command Command names, command option names, utility names,utility flags, and other keywords are in bold type.

variable Variables, or words that stand for values that you fill in, arein italics.

{ } Curly braces indicate that you choose at least one of theenclosed options. Do not include braces in your option.

[ ] Brackets mean choosing one or more of the enclosed optionsis optional. Do not include brackets in your option.

( ) Parentheses are to be typed as part of the command.

| The vertical bar means you can select only one of the optionsshown.

, The comma means you can choose as many of the optionsshown as you like, separating your choices with commas tobe typed as part of the command.

13

About This Book

If You Need HelpEach Sybase installation that has purchased a support contract has one ormore designated people who are authorized to contact Sybase TechnicalSupport. If you cannot resolve a problem using the manuals or onlinehelp, please have the designated person contact Sybase TechnicalSupport or the Sybase subsidiary in your area.

14

Chapter 1

Introduction

After installing Adaptive Server, you can change the configuration tomodify the way the server works. This manual covers configurationtopics, including:

• Setting up Adaptive Server to communicate with clients

• Using the dcsp and dsedit utilities to modify the interfaces file

• Localization features such as languages, character sets, and sort orders

New Functionality in Adaptive Server 11.5.1Adaptive Server 11.5.1 provides the following new functionality:

• Use of the UnicodeTM-based conversion mechanism offered by theUnicode Infrastructure Library. New character sets can be added byadding a new external table. All existing Sybase-supported charactersets are included. For details, see “Character Sets” in Chapter 5,“Localization Issues.”

• The sortkey and compare functions, which provide sophisticatedcollation support for companies that use languages other thanus_english. For details, see “Gathering Information About Collation”on page 85.

• For HP only, you can now use devices of more than 4GB. For details,see “Using Large Devices on HP-UX 10.20” on page 32.

Configuring for High-Availability ProductsAdaptive Server is compatible with high-availability products for severalplatforms and operating systems, such as the Compaq On-Line RecoveryServer. Configuration procedures for these high-availability products areavailable at the Sybase World Wide Web site.

15

Chapter 1 Introduction

H To view the high-availability configuration procedures

1. In your browser, enter the following address to access the Sybase Website:

http://www.sybase.com

2. Click the Technical Support button.

3. Navigate to the Technical Information Library.

4. Enter “High Availability” in the Search utility.

The Search utility generates a list of titles for Technical Notes that containhigh-availability configuration procedures. See the titles that include“Configuring Sybase SQL Server for High Availability”, and a referenceto your platform or operating system.

16

Chapter 2

Configuring the Operating System AfterInstallation or Upgrade

This chapter discusses the operating system configuration settings thatyou can adjust after installing or upgrading Adaptive Server. Unlessstated otherwise, the information pertains to all supported UNIXplatforms.

Topics covered are:

• Setting Environment Variables 17

• Using the stty Setting 19

• Restoring Correct Permissions 19

• File Descriptors and User Connections 19

• Adjusting the Client Connection Timeout Period 25

• Checking for Hardware Errors 27

• Monitoring the Use of Operating System Resources 28

• Using Large Devices on HP-UX 10.20 32

Setting Environment VariablesIt is crucial to the operation of Sybase products that the systemenvironment variables are set correctly. Environment variables are set inthe user’s environment either interactively or by including them in theuser’s .login and .cshrc files (for C shell) or .profile file (for Bourne shell).

Only the file owner or the ‘‘root’’ user can edit a user’s .login, .cshrc, or.profile file.

You may want to verify that the Adaptive Server environment variablesin Table 2–1 are set correctly.

H To check the current value of environment variables

• Enter the following command at the operating system prompt:

setenv

17

Chapter 2 Configuring the Operating System After Installation or Upgrade

Table 2–1 describes the system environment variables for AdaptiveServer:

Table 2–1: System environment variables

Variable Sample Value Function

DSLISTEN IGNATZ Used at Adaptive Server start-up; enables thespecified Adaptive Server to listen for inputfrom front-end software.

DSQUERY IGNATZ Defines the Adaptive Server to which localclient applications connect.

PATH /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin

Appends the full path to the Adaptive Serverbin subdirectories.

DSLISTENThe DSLISTEN environment variable defines the name used by AdaptiveServer to listen for client connections, when no name is given duringAdaptive Server start-up. If DSLISTEN is not set, and no name is givenduring start-up, the Adaptive Server name defaults to the server namegiven at installation.

DSQUERYThe DSQUERY environment variable defines the Adaptive Server nameto which client programs attempt to connect when no Adaptive Servername is specified with a command line option. If DSQUERY is not set,and you do not supply the Adaptive Server name with a command lineoption, clients try to connect to the server name given at installation.

PATHThe PATH environment variable specifies which directory paths to searchfor executables. The Sybase executables are in the bin and installdirectories in the Sybase installation directory. The install programappends these paths to the current PATH environment variable.

♦Note The new executables are added at the end of the PATH variable. Be sureto verify that you do not have any old Sybase executables, instead of thenew executables, in the PATH that will be invoked.

18

Using the stty Setting

Using the stty SettingSetting the stty tostop option causes a background Adaptive Server to stopas soon as it tries to write to the terminal. To avoid this error, execute thefollowing command before starting Adaptive Server:

stty -tostop

If you are redirecting all Adaptive Server output to files, you do not haveto change the stty setting.

Restoring Correct PermissionsSybase software files and directories are installed with the correct accesspermissions. If you notice that the permissions are no longer correct, youcan restore the correct permissions with the script setperm_all, located inthe $SYBASE/install directory.

File Descriptors and User ConnectionsThe number of user connections used by Adaptive Server cannot exceedthe number of file descriptors available to Adaptive Server on theoperating system. When configuring user connections on AdaptiveServer, the System Administrator should take into account the number offile descriptors available per process. Although most of the open filedescriptors are available for user connections, a few are used byAdaptive Server for opening files and devices.

For Digital UNIXThe number of file descriptors per process is determined by theoperating system parameter open_max. The default value of open_max is4096. For more information on setting open_max, see the Digital UNIXoperating system documentation.

H To obtain the current value of the open_max parameter:

• Use the Korn or Bourne shell ulimit command:

ulimit -n

Adaptive Server can use a maximum of 1024 file descriptors,regardless of the value of open_max.

19


H To obtain the number of current file descriptors programmatically:

• Use the sysconf or getdtablesize function.

For HP-UXThe kernel parameters maxfiles and maxfiles_lim control the number of filedescriptors available to any one process.

For NCRYou can set both the soft and hard limits for files descriptors. Anyprocess can use the setrlimit system call to increase its soft limit. A processwith an effective user ID of 0 (root) can also raise the hard limit. Thekernel soft limit parameter SFNOLIM specifies the maximum number offile descriptors a process can have. The kernel hard limit parameterHFNOLIM specifies the maximum value of SFNOLIM.

For SGIFor SGI you can set both “soft” and “hard” limits for file descriptors.The soft limit can be increased up to the hard limit by the user, but thehard limit can be increased only by someone with “root” permissions.The soft limit determines the number of open file descriptors available toan Adaptive Server engine.

Although most of the open file descriptors are available for userconnections, a few are used by Adaptive Server engines for opening filesand devices.

See the System Administration Guide for additional information on userconnections.

Displaying Current Soft and Hard Limits

H To display the current soft limit:

• For C shells, enter:

limit descriptors

For Bourne shells, enter:

ulimit -n

20

File Descriptors and User Connections

H To display the current hard limit:


limit -h descriptors


ulimit -Hn

Increasing the Soft Limit

H To increase the soft limit:


limit descriptors n


ulimit -Sn new_value

where n is the current value for the soft limit, and new_value is thevalue to which you want to increase the soft limit.

♦Note The preceding commands can be used in your runserver file to increasethe hard and soft limits. Because the runserver file is a Bourne shellscript, be sure to use the Bourne shell versions of these commands in therunserver file.

Increasing the Hard Limit

To increase the hard limit, use a program like the sample program shownin “Sample Program” on page 22.

H To set up the sample program to increase the hard limit:

1. Create the ASCII file file_name.c (where file_name is the name you givethe file), by using a text editor. Type the text shown in the sample in“Sample Program” on page 22.

2. Compile the file using the following command:

cc file_name.c -o program_name

where file_name is the name of the source file you created, andprogram_name is the name you want to give the program.

21


3. Change the program’s permissions and ownership so that it willexecute as “root”:

chmod 755 program_namechown root program_name

where program_name is the name of the compiled program.

4. The “root” user can use the program to start Adaptive Server withincreased user connections by typing the following command at theoperating system prompt:

# program_name dataserver -d master_device_name

where program_name is the name of the compiled program, andmaster_device_name is the full path of Adaptive Server’s master device.Instead of typing the command at the operating system prompt, youcan add program_name preceding the dataserver command line in theAdaptive Server runserver file.

Sample ProgramThe following example shows the source code that you can use toincrease the hard limit:

#include <sys/time.h>#include <sys/resource.h>#include <sys/types.h>/*** define MAX_CONNECTIONS to a number less than**10000. The number defined will then become the maximum** number of connectionsallowed by an Adaptive Server.*/#define MAX_CONNECTIONS 9999externint errno;main(argc,argv)char **argv;{

structrlimit rlp;uid_t uid;

rlp.rlim_cur= MAX_CONNECTIONS;rlp.rlim_max = MAX_CONNECTIONS;

[nbsp ] /*set the number of open file desriptors toMAX_CONNECTIONS*/if (setrlimit (RLIMIT_NOFILE,&rlp) == -1){

perror(‘‘setrlimit’’);exit(1);

}

22

File Descriptors and User Connections

[nbsp ] /*reset the user id to disable superuserprivileges*/uid = getuid();setuid(uid);

[nbsp ] /*run the program indicated as arguments tothisprogram */execv(*++argv, argv);

}

For additional information on user connections, see the SystemAdministration Guide.

For Sun SolarisFor Sun Solaris you can set both “soft” and “hard” limits for filedescriptors. The soft limit can be increased up to the hard limit by theuser, but the hard limit can be increased only by someone with “root”permissions. The soft limit determines the number of open filedescriptors available to an Adaptive Server engine.

Although most of the open file descriptors are available for userconnections, a few are used by Adaptive Server engines for opening filesand devices.

See the System Administration Guide for additional information on userconnections.

Displaying Current Soft and Hard Limits

H To display the current soft limit:


limit descriptors


ulimit -n

H To display the current hard limit:


limit -h descriptors


ulimit -Hn

23


Increasing the Soft Limit

H To increase the soft limit:


limit descriptors n


ulimit -Sn new_value

where n is the current value for the soft limit, and new_value is thevalue to which you want to increase the soft limit.

♦Note The preceding commands can be used in your runserver file to increasethe hard and soft limits. Because the runserver file is a Bourne shellscript, be sure to use the Bourne shell versions of these commands in therunserver file.

Increasing the Hard Limit

To increase the hard limit, use a program like the sample program shownin “Sample Program” on page 22.

H To set up the sample program to increase the hard limit:

1. Create the ASCII file file_name.c (where file_name is the name you givethe file), by using a text editor. Type the text shown in the sample in“Sample Program” on page 22.

2. Compile the file using the following command:

cc file_name.c -o program_name

where file_name is the name of the source file you created, andprogram_name is the name you want to give the program.

3. Change the program’s permissions and ownership so that it willexecute as “root”:

chmod 755 program_namechown root program_name

where program_name is the name of the compiled program.

24

Adjusting the Client Connection Timeout Period

4. The “root” user can use the program to start Adaptive Server withincreased user connections by typing the following command at theoperating system prompt:

# program_name dataserver -d master_device_name

where program_name is the name of the compiled program, andmaster_device_name is the full path of Adaptive Server’s master device.Instead of typing the command at the operating system prompt, youcan add program_name preceding the dataserver command line in theAdaptive Server runserver file.

Adjusting the Client Connection Timeout PeriodAdaptive Server uses the KEEPALIVE option of the TCP/IP protocol todetect clients that are no longer active. When a connection to a client isinactive for a period of time (the timeout period), the operating systemsends KEEPALIVE packets at regular intervals. If it does not receive aresponse from the client machine for any of these packets, the operatingsystem notifies Adaptive Server that the client is no longer responding.Adaptive Server then terminates the client’s connection.

The KEEPALIVE default timeout period is 2 hours (7,200,000 ms). Todisplay the current time value, use the command for your platform asshown in the following sections.

For Digital UNIX

H To display the current timeout value:

• Enter:

/usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval

H To reduce the timeout period to 15 minutes (900,000 ms):

• Enter:

/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 900000

25


For HP-UX

H To display the current timeout period:

• Enter:

/usr/contrib/bin/nettune -l

♦Note The switch is a lower case “l”, not a numeral one (1).

The tcp_keepstart parameter specifies the length of time (measured inseconds) to keep an idle connection active before the system checks tosee if the connection died.

H To change the timeout period:

• Use the nettune -s command.

For IBM RS/6000

H To display the current timeout value:

• Enter:

/usr/sbin/no -o tcp_keepidle

The tcp_keepidle parameter specifies the length of time (measured inhalf seconds) to keep an idle connection active before the systemchecks to see if the connection died. The default is 14,400 halfseconds (7200 seconds, or 2 hours).

IBM recommends a value of at least 15 minutes.

For NCRUse the getsockopt system call to obtain the value of KEEPALIVE. You canalso use getsockopt to change the value of KEEPALIVE.

26

Checking for Hardware Errors

For Sun Solaris

H To display the timeout value:

• Enter:

/usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval

H To reduce the timeout period to 15 minutes (900,000 ms.):

• Enter:

/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 900000

Checking for Hardware ErrorsThe following types of hardware error messages indicate problems thatmay lead to database corruption:

• Disk read, write, or retry errors

• Timeouts

• System panics

• Memory problems of any type

For Digital UNIXCheck the /var/adm/messages file on a regular basis. See the operatingsystem documentation for more information on this file.

For HP-UXCheck the /var/adm/syslog/syslog.log file on a regular basis. You can viewthe file directly, or you can use the HP-UX dmesg command. See youroperating system documentation for more information.

For IBM RS/6000The errpt command includes several flags for limiting the report to eventsthat match certain criteria. Use the errpt command on a regular basis. Iferrors appear, use the diagnostic tool diag to check your memory and

27


disks. Or use the System Management Interface Tool (SMIT) to run theerrpt command. This command may produce a lot of output.

For NCRCheck the file in /var/adm/streams for errors. See the operating systemdocumentation for more information.

For SGICheck the /var/adm/SYSLOG file on a regular basis. You can view the filedirectly. See the operating system documentation for more information.

For Sun SolarisCheck the /var/adm/messages file on a regular basis. If any of the types ofhardware errors described in the beginning of this section appear, use theSun Microsystems diagnostic tool, sundiag, to check memory and disks.See the operating system documentation for more information.

Monitoring the Use of Operating System ResourcesThe System Administration Guide discusses maintaining the optimalnumber of Adaptive Server engines for your work-load and systemconfiguration. To determine the optimal number, you need to monitorsystem and CPU usage.

For Digital UNIXThe following tools help monitor performance:

• The iostat command reports the amount of I/O on terminals and harddisks and how CPU time is spent.

• The vmstat command monitors virtual memory usage.

• The netstat command monitors network status.

• The ps command provides an accurate snapshot of accumulated CPUtime and usage for individual processes. This can be very helpful indetermining the load of the dataserver, engine, and processes.

28

Monitoring the Use of Operating System Resources

• The time command can be useful in determining the various user,system, and real-time resources used over a complete run.

For details on these tools, see your operating system documentation.

For HP-UXHP-UX supplies many tools to help monitor performance, some of whichare described as follows:

• The sar command reports relative and absolute I/O throughput ratesto each disk and controller.



• The ps command provides a snapshot of accumulated CPU time andusage for individual processes.



For IBM RS/6000IBM RS/6000 supplies the following tools for monitoring performance:




– netstart -v displays Transmit/Receive Statistics. It is also used todetermine if enough mbufs have been configured for networktraffic.

– no -a displays current network options. It is also used for tuningmbuf pools.

• The ps command provides a snapshot of accumulated CPU time andusage for individual processes.

• The time command determines the various user, system, and real-timeresources during a complete run.


29


For NCRNCR supplies the following tools for monitoring performance:


• The netstat command reports network status.

• The ps command gives an accurate snapshot of accumulated CPUtime and usage for individual process.

• The timex command can be used to report process data and systemactivity.

For SGISGI supplies the following tools for monitoring performance:

• The osview command monitors various activities of the operatingsystem and displays them on a full screen.

• The gr_osview command provides a graphical representation of systemresources.

• The sar command reports usage of system resources on a line basis.

• The ps command provides a snapshot of accumulated CPU time andusage for indivifual processes.

• The timex command determines various user, system, and real-timeresources during a complete run.


For Sun SolarisSun Solaris supplies the following tools to help monitor performance:




• The ps command gives you an accurate snapshot of accumulated CPUtime and usage for individual processes. This can be very helpful indetermining the dataserver-, engine-, and process-specific loading.

30

Monitoring the Use of Operating System Resources



A Sample C Shell Maintenance ScriptThe following sample C shell script calls several isql scripts:

#!/bin/csh -fif ( -e dbcc_mail.out) then

rm dbcc_mail.outendifforeach i (*.dbcc)isql -Usa -Ppassword < $i > dbcc_outif ( ‘grep -c ’Msg 25[0-9][0-9]’ dbcc_out’ ) then

echo "There are errors in" $i >> dbcc_mail.outcat dbcc_out >> dbcc_mail.out

elseecho "Backing up " $i:r >> dbcc_mail.outisql -Usa -Ppassword < $i:r.backup

endifendmail -s "Backup Report" jjones < dbcc_mail.out

The first set of scripts (one for each database with a file name appendedwith .dbcc) runs dbcc checkalloc and dbcc checkdb for each database andsends the messages to an output file called dbcc_out.

For example, the script master.dbcc runs dbcc to check the master database:

dbcc checkalloc (master)godbcc checkdb (master)go

The C shell script then runs the grep command to find 2500-level errormessages in the dbcc output. The results of the grep command go into anoutput file called dbcc_mail.out.

Next, the script invokes an isql backup script for each database for whichno 2500-level errors occurred and adds the “Backing up database_name”line to dbcc_mail.out. For example, the script master.backup backs up themaster database:

use mastergodump database master to master_dumpgo

31


You may want to add appropriate dump transaction commands to yourscripts.

If there are 2500-level error messages, the script does not back up thedatabase. At the end of the script, dbcc_mail.out is mailed to the SystemAdministrator ‘‘jjones,’’ who then has a record of fatal dbcc errors andsuccessful backups.

You can tailor the sample shell and isql scripts to suit the needs of yourinstallation.

To have the scripts execute automatically, edit the crontab file, and add anentry similar to this:

00 02 * * * /usr/u/sybase/dbcc_ck 2>&1

In this example, a C shell script called dbcc_ck executes every morning at2:00 a.m.

Using Large Devices on HP-UX 10.20You can create and access large devices and files in Adaptive Server onHP-UX version 10.20 machines. Prior to Adaptive Server version 11.5.1,there was a limit of 4GB for disk access on these machines. By using64-bit datatypes and routines, Adaptive Server 11.5.1 can access up to 264

bits of disk resources, allowing the server to access the upper limit of itsinternal database size, which is 32GB.

32

Chapter 3

Setting Up Communications Across a Network

This chapter provides information about how to set up communicationsacross the network. Adaptive Server uses a configuration file called the“interfaces” file to provide the information Adaptive Server needs toallow servers and clients to communicate. On UNIX platforms theinterfaces file is named interfaces. This chapter describes the interfaces fileand provides specific configuration information for each supported UNIXplatform.

Topics covered are:

• What Is an Interfaces File? 34

• How Adaptive Server Uses an Interfaces File 36

• How a Client Uses an Interfaces File 36

• Heterogeneous and Homogeneous Environments 37

• Understanding the Format of the Interfaces File 39

• Utilities for Editing the UNIX Interfaces File 46

• Creating One Interfaces File for Multiple Installations 46

• Configuring Interfaces Files for Multiple Networks 47

Adaptive Servers and clients have their own interfaces files. Interfacesfiles of either type contain entries for all Adaptive Servers, backupservers, and other server products on the network.

Table 3–1 shows where to find more information on server and clientinterfaces file tasks and topics.

Table 3–1: Where to find interfaces file tasks and topics

Type of InterfacesFile Task or Topic See

UNIX server or client Adding entries for multipleAdaptive Server installations

Chapter 4, “Modifying the InterfacesFile.” and Chapter 5, “LocalizationIssues.”

Modifying or deleting entries Chapter 4, “Modifying the InterfacesFile.” and Chapter 5, “LocalizationIssues.”

33

Chapter 3 Setting Up Communications Across a Network

Type of InterfacesFile Task or Topic See

Creating a master interfaces file formultiple installations

“Creating One Interfaces File forMultiple Installations” on page 46

Configuring for multiple networks “Configuring Interfaces Files forMultiple Networks” on page 47

Reference information “Understanding the Format of theInterfaces File” on page 39

PC client Configuring a client Installing Adaptive Server andOmniConnect on UNIX Platforms

Reference information andinstructions for advanced tasks

Open Client Supplement for your PCclient platform or the appropriate OpenClientTM documentation

Client platforms notlisted

Configuring, reference information,and instructions for advanced tasks

Open Client Supplement for your clientplatform or the appropriate OpenClient documentation

What Is an Interfaces File?An interfaces file contains information about the network locations ofservers.

In the Sybase client/server environment, a client can connect withAdaptive Server if it knows where the server resides on the network andif the server supports the client’s language or character set. When aclient initiates a connection, it looks in its interfaces file for the networklocation of the target server.

The interfaces file lists the name and address of every server, includingBackup ServerTM. When you are using a client program, and you want toconnect with a particular server, the client program looks up the servername in the interfaces file and connects to that server. You can alsosupply the name of the server by using the DSQUERY environmentvariable.

Servers also need network information. When a server starts up, it looksin its interfaces file to determine where to listen for client connectionrequests. In addition, Adaptive Server can take on a client role when itmakes remote procedure calls to other Adaptive Servers.

34

What Is an Interfaces File?

Creating an Interfaces FileThe installation program, srvbuild, automatically creates an interfaces filefor each server and client installation. The default location for theinterfaces files is the Sybase installation directory (as determined by thevalue of the SYBASE environment variable).

Contents of an Interfaces FileAn interfaces file contains network information about all servers on yournetwork, including Adaptive Server, Backup Server, XP Server, plus anyother server applications such as Adaptive Server Enterprise MonitorTM

Server, Replication Server® and Open ServerTM.

The network information in the file includes the server name, networkname or address of the host machine, and the port, object, or socketnumber (depending on the network protocol) on which the server listensfor queries. See “Understanding the Format of the Interfaces File” onpage 39 for the specific makeup of the interfaces file entry.

Each entry in an interfaces file can contain two types of lines:

• Master lines, which are used by server applications to listen forqueries over the network. This information is called a listener service.

• Query lines, which are used by client applications to connect toservers over the network. This information is called a query service.

The network information contained in the master and query lines for aserver is identical because a server listens for connection requests on thesame port that clients use to request connections.

Differences Between Client and Server Interfaces Files

A server needs both master and query lines in its interfaces file, sinceservers sometimes act as clients to other servers.

A client’s interfaces file does not need a master line. It functionscorrectly with only a query line.

If Your Site Has Multiple Installations

If you have more than one Adaptive Server installation, each server’sinterfaces file should contain information about all servers on thenetwork. See Chapter 5, “Localization Issues,” for information aboutadding entries for additional servers.

35


If all of your server products are running on the same platform, you cancreate one master interfaces file and copy that file to each machine. Formore information, see “Creating One Interfaces File for MultipleInstallations” on page 46.

If the host machine supports multiple networks, see “ConfiguringInterfaces Files for Multiple Networks” on page 47.

How Adaptive Server Uses an Interfaces FileAdaptive Server uses its interfaces file to listen for clients. To listen forqueries, the server:

• Determines its own name by checking the value of the DSLISTENenvironment variable

• Looks in the interfaces file for an entry whose name matches theDSLISTEN name and finds the corresponding master line

• Uses the network information provided by the master line to listenfor queries

How a Client Uses an Interfaces FileWhen a client, or a server acting as a client, connects to a server it:

• Determines the name of the server either programmatically or byreferring to the DSQUERY environment variable. If the applicationuser has not set DSQUERY, the run-time value for the server namedefaults to the SYBASE environment variable.

• Looks in the interfaces file for an entry whose name matches thename of the server, stops at the first instance of that name, and readsthe query line.

• Uses the network information provided by the query line to connectto the server. If the client is unable to connect the first time, it makesadditional attempts according to the delay and retry numbersindicated in the interfaces file. If no matching entry is found, an errormessage is written to the client’s standard error file. If multiplenetworks are supported, the client attempts to connect using theinformation in the second query entry for the server. (See“Configuring for Query Port Backup” on page 52.)

36

Heterogeneous and Homogeneous Environments

The Open Client documentation discusses client connections in muchgreater detail. See the Open/Client Supplement for your client platformor the appropriate Open/Client documentation.

Heterogeneous and Homogeneous EnvironmentsYou can run Adaptive Server and clients on the same platform or ondifferent platforms.

If the platforms are different, each platform may require a differentformat and configuration for its interfaces file. Figure 3–1 illustrates howa client PC uses network information in its interfaces file (sql.ini) toconnect to Adaptive Server running under UNIX, and how AdaptiveServer uses its interfaces file (interfaces) to connect to another serverduring a remote procedure call.

37


Figure 3–1: Establishing network connections in a heterogeneous environment

sql.ini [HARP0]

[CHICO]

interfacesHARP0

CHICO

HARPO SQL SERVER

CHICO SQL SERVER

PC Clients

"Get HARPO'saddress andconnect."

"Get CHICO'saddress andconnect."

"Make a RemoteProcedure Callto CHICO."

If both a client and a server are running under UNIX, a copy of the sameinterfaces file is valid for both. Figure 3–2 illustrates how clients andAdaptive Servers running in a homogeneous environment can use copiesof the interfaces file to establish connections. Because the two AdaptiveServers are running under the same operating system, they can use thesame interfaces file or exact copies of the same file.

38

Understanding the Format of the Interfaces File

Figure 3–2: Establishing network connections in a homogeneous environment

interfacesHARP0

CHICO

HARPO SQL SERVER

CHICO SQL SERVER

Homogeneous Clients

"Get HARPO'saddress andconnect."

"Get CHICO'saddress andconnect."

" Get CHICO'saddress and makean RPC."

Understanding the Format of the Interfaces FileWhen an Adaptive Server is installed, srvbuild creates an entry for it in theinterfaces file. The following examples show the different components of

39


an interfaces file entry. For descriptions of the components, see“Components of an Interfaces File Entry” on page 41

Format by PlatformThe following rules apply to the format of interfaces file entries:

• Each Adaptive Server has only one entry, although there may bemultiple lines in the entry.

• Each line that follows the servername line must begin with a space ora character tab.

• Each element on the line must be separated by a single space.

• Each entry is separated by a blank line.

• You can add comments to an interfaces file by adding a pound sign(#) at the beginning of the line and a line break at the end.

The format of entries is described in the following sections.

Digital UNIX

This platforms uses three formats:

servername retry_attempts delay_interval <newline><tab> service_type api protocoldevice address <newline>

Or

servername retry_attemptsdelay_interval <newline><tab> service_type driver protocol device address <newline>

Or

servername retry_attempts delay_interval <newline><tab> service_type protocolnetwork host port/object_number <newline>

HP-UXservername retry_attempts delay_interval <newline><tab> service_type protocol network machine port <newline>

40


IBM RS/6000servername retry_attempts delay_interval <newline><tab> service_type api protocol device address <newline>

servername retry_attempts delay_interval <newline><tab> service_type protocol network machine port <newline>

Sun Solarisservername retry_attempts delay_interval <newline><tab> service_type api protocol device address <newline>

Components of an Interfaces File EntryTable 3–2 describes the components of an interfaces file entry.

Table 3–2: Components of an interfaces file

Component Value

servername Name of Adaptive Server or Backup Server.Requirements for a server name are:

• The name must be not more than 30 characters long.

• First character must be a letter (ASCII a-z, A-Z).

• The characters that follow must be letters, numbers, orunderscores (_).

retry_attempts (optional) Number of times you want the client to try to connect to a serverafter initial failure. Default is 0.

delay_interval (optional) Number of seconds between connection attempts. Default is 0.

service_type Type of service defined by entry. Must be one of three values:

• master (see “Contents of an Interfaces File” on page 35)

• query (see “Contents of an Interfaces File” on page 35)

• debug (connection for use by Sybase Technical Support only)

api Application programming interface available to the network. Theavailable interface file for UnixWare is TLI (Transport LayerInterface), represented by the letters “tli”.

protocol Name of the network protocol. Protocols available are:

• For HP-UX, IBM RS/6000, Sun Solaris, UnixWare:

– TCP/IP, represented by the letters “tcp”

– SPX, represented by the letters “spx”

• For Digital UNIX:

DECnet, represented by the letters “decnet”

41


Component Value

network Name of the network; not currently used by Adaptive Server. srvbuildenters “ether” as a placeholder.

host Network name or address of server’s host machine.

• For TCP/IP, use either the host name or internet address.Maximum size of entry is 32 bytes.

To determine the host name of a machine, log into that machineand enter:

/bin/hostname

• For DECnet, use the node name. Maximum size of entry is 6 bytes.

machine Network name or address of server’s host machine.You can use either the host name or internet address. Maximum sizeof entry is 32 bytes.To determine the host name of a machine, log into that machine andenter:

/bin/hostname

device The network device endpoint.

• For TCP networks, it varies according to the vendor supplying thenetworking software. Check the vendor-specific documentationfor the name of the device. Your network may provide multiplestreams devices corresponding to different protocols in the TCPprotocol suite. Choose the TCP streams device. Common TCPstreams devices include /dev/tcp, /dev/ito, and /dev/inet/tcp.

• For the IPX protocol, the value is always /dev/nspx.

address for a TCP protocolentry

Address consists of:

• Address prefix, “\x” for tli.

• Network type, always 0002.

• Port number converted to a hexadecimal, four digits. Must bebetween 1025 and 65535. Must be unique. Check the /etc/servicesfile on each machine on the network to see what port numbers arein use. Enter the Adaptive Server port number in a new section of/etc/services labeled “Sybase specific services”. You do not have tomake this entry for the operating system to function properly, butthe presence of the port number in the file may prevent otherusers from using the port number.

• IP network node address of the host machine converted to ahexadecimal, 8 digits.

• Trailing zeros, optional, 16 digits.

42


Component Value

address for an SPX protocolentry

Address consists of:

• Address prefix, “\x” for tli.

• Network address, 8 digits

• Node address, 12 digits

• Socket number, 4 digits

port/object number • For TCP/IP networks, port is a unique port number between 1025and 65535. Check the /etc/services file on each machine on thenetwork to see what port numbers are in use. Enter the AdaptiveServer port number in a new section of /etc/services labeled“Sybase specific services”. You do not have to make this entry forthe operating system to function properly, but the presence of theport number in the file may prevent other users from using thatnumber.

• For DECnet networks, object is an object number between 128 and253. The number must be unique to the node on which the serveris running.

port A unique port number between 1025 and 65535. Check the /etc/services file on each machine on the network to see what portnumbers are in use. Enter the Adaptive Server port number in a newsection of /etc/services labeled “Sybase specific services”. You do nothave to make this entry for the operating system to function properly,but the presence of the port number in the file may prevent otherusers from using that port number.

Creating Interfaces Files for SPXIf Novell Protocol Suite Version 3.0.1 is installed on your machine, youcan create interfaces file entries to support the SPX/IPX protocol.Interfaces file entries for SPX have the following format:

servername retry_attempts delay_interval <newline><tab> service_type api protocol device address <newline>

♦Note Each entry line that follows the servername line must begin with a <tab>character or a blank space. Use a single space between each componenton an entry line.

The servername, retry_attempts, delay_interval, and service_type componentshave the same meaning in an SPX entry as in a TCP entry.

The following sections describe the remaining components in theinterfaces file.

43


api

api is the application programming interface to the network. SinceAdaptive Server uses the Transport Layer Interface (TLI) for SPXprotocol connections, use the letters “tli”.

protocol

protocol is the name of the network protocol. Use the letters “spx” todesignate the SPX protocol.

device

device is the network device endpoint supplied for SPX networks. Thedevice that is supplied with the Novell Protocol Suite network softwareis named /dev/nspx.

address

address is a composite entry generated from the network number, node,and socket number, defined as follows:

• The first 4 bytes of the address represent the network numberconverted to hexadecimal.

• The next 6 bytes represent the network node of the machine runningAdaptive Server.

Both the network number and node are assigned by the networkadministrator of your system. You can check the /usr/netware/npsconfigfile to determine the network and node numbers for your machine.

• The socket number is a hexadecimal number between 0x8000 and0xFFFF that identifies the process on the machine.

If you choose a socket number that is already in use on the machinewhere your Adaptive Server is located, you receive a message similarto the following when you attempt to restart your Adaptive Server:

ninit: t_bind, Incorrect permissionsninitconn_free: t_close, fd=5, Illegal transport fdninit: All master network listeners have failed.Shutting down.ueshutdown: exiting

More than one Adaptive Server can have the same socket number, ifeach server is on a different machine. The combination of networknumber, node, and socket uniquely identifies the Adaptive Server.

For example, if your machine has a network number of 4D160D14and a node number of 000000000001, and you use socket number86bb, sybinit adds the address entry:

44


/x4D160D1400000000000186bb

Interfaces File ExampleFigure 3–3 illustrates an environment with three UNIX Adaptive Serversand one UNIX client. The interfaces file shown is a master interfaces filethat works for each server and the client on the four machines shown.

Figure 3–3: Interfaces file for three Adaptive Servers and one client

##TEST on gummo (131.214.1.246) using tcp# services: query (3874) master (3874)#TEST

query tli tcp /dev/tcp \x00020f2283d601f60000000000000000master tli tcp /dev/tcp \x00020f2283d601f60000000000000000

##PRACTICE on chico (131.214.1.247) using tcp# services: query (4874) master (4874)#PRACTICE

query tli tcp /dev/tcp \x0002130a83d601f70000000000000000master tli tcp /dev/tcp \x0002130a83d601f70000000000000000

##PRODUCTION on groucho (131.214.2.71) using tcp# services: query (8086) master (8086)#PRODUCTION

query tli tcp /dev/tcp \x00021f9683d602470000000000000000master tli tcp /dev/tcp \x00021f9683d602470000000000000000

DSQUERY = PRODUCTION

DSQUERY = TEST

DWB

GUMMO

HARPO (user)

DSQUERY = PRACTICE

CHICO

GROUCHO

45


Utilities for Editing the interfaces FileThe following Sybase utilities are provided for editing the networkinformation in the interfaces file.

• dsedit – an X-Windows GUI utility

• dscp – a UNIX command line utility

For details on using these utilities, see Chapter 4, “Modifying theInterfaces File.”

Creating One Interfaces File for Multiple InstallationsDistributing copies of one interfaces file (a master file) with entries for allAdaptive Servers is the easiest way to maintain consistency in theinterfaces files in a homogeneous environment on a network.

You make all changes to one version of the file and then copy theupdated master file to all appropriate Sybase directories.

You can make a master file in one of two ways:

• Using dsedit or dscp

• Using a text editor

Using dsedit or dscp to Create a Master Interfaces FileYou can use the dsedit or dscp utility to create a master interfaces file,which you can then distribute to all servers. If you are not an experiencedSybase user, you may find that using dsedit or dscp is easier than using atext editor. Using dsedit or dscp also ensures that your interfaces file isconsistent in format (no aberrant spaces, tabs, and so forth).

To create a master interfaces file with dsedit or dscp:

1. Select the interfaces file that contains the most complete, up-to-dateinformation.

2. Begin a dsedit or dscp session in your latest Sybase installation to editthis interfaces file.

3. Add entries for any Adaptive Servers or Backup Servers that are notlisted in this file.

For details on using dsedit or dscp, see Chapter 4, “Modifying theInterfaces File.”

46

Configuring Interfaces Files for Multiple Networks

Using a Text Editor to Create a Master Interfaces FileTo construct a single master interfaces file from several individualinterfaces files:

1. Concatenate the individual interfaces files.

2. Make a copy of the file.

3. Use a text editor to modify the copy of the concatenated file.

♦Note When you manually edit an interfaces file, be sure that, for each entry,each line following the first line begins with a <tab> character.

The following elements must be correct and unique in the resultingfile:

– servername

Each server entry in the interfaces file must be unique. During thesrvbuild session, you had the choice of entering a server name oraccepting the default server name, SYBASE, for those servers. Ifyou accepted the default name, find any duplicate SYBASE entriesin your merged file, and rename them.

– A combination of the host machine’s network name or addressand Adaptive Server’s port or object number.

– If the original interfaces file was created when there was only onemachine on the network, its entries may have the word “loghost”in place of the machine name (address). If “loghost” is present,replace it with the machine name.

Configuring Interfaces Files for Multiple NetworksOn some platforms, Adaptive Server can accommodate multiplenetworks. This allows Adaptive Server to listen for clients over multiplenetwork interfaces. You must add an entry for each network interface tothe interfaces file.

Configuring the Server for Multiple Network HandlersTo configure multiple network listeners:

1. Define a unique host name for each network interface in youroperating system’s host database.

47


2. In your interfaces file, use a text editor to add copies of the “master”line for your Adaptive Server, one for each additional interface youwant the server to listen on.

3. Include a unique host name on each line to configure a networkhandler for each network interface.

4. Port numbers within the interface need not be the same, but they canbe. They fall under the same rules for naming and numeric range asthe primary network interface.

Sample interfaces Files for Multiple Network Handlers

The following example shows an interfaces file for an Adaptive Serverwith two network interfaces, each connected to a different network. Theserver host machine’s network address is 131.214.1.246 on Network 1 and131.214.1.247 on Network 2.

# PRODUCTION server with two network listenersPRODUCTION<tab>3<tab>3<newline><tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000<tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000<tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000

The following example shows an interfaces file for an Adaptive Serverwith two network interfaces, each connected to a different network. Theserver host machine is connected to a TCP/IP network, on which it iscalled SERV_CORPNET, and a DECnet network, on which it is calledSERV_ENGNET.

# PRODUCTION server with two network listenersPRODUCTION<tab>3<tab>3<newline><tab>master tcp ether SERV_CORPNET 6464<tab>master decnet ether SERV_ENGNET 150<tab>query tcp ether zeppo 6464

The following example shows an interfaces file for an Adaptive Serverwith two network interfaces. The server host machine is known asSERV_CORPNET on the corporate network and SERV_ENGNET on theengineering network.

# PRODUCTION server with two network listenersPRODUCTION<tab>3<tab>3<newline><tab>master tcp ether SERV_CORPNET 4559<tab>master tcp ether SERV_ENGNET 5479<tab>query tcp ether SERV_CORPNET 4559

The next time Adaptive Server is restarted, it spawns a network handlerprocess for each master line in the entry that corresponds to the server’s

48


DSLISTEN value. Connections made on each interface will be handledequally, as peers.

Configuring the Client ConnectionsWhen an Adaptive Server client scans the interfaces file for a servername, the client uses the first “query” entry it encounters for the server’sentry. This makes configuring clients to use multiple networkconnections less straightforward than configuring the server ports. Youhave two choices:

• Use different DSQUERY names for the clients. The interfaces files onall the machines are the same, but they contain multiple DSQUERYnames.

• Use the same DSQUERY name for all clients. The interfaces files onthe different machines contain different network names.

Using One Network-Independent DSQUERY Name

If uniform client DSQUERY naming is important, you can mask thenecessary difference in the network addressing of the clients in theinterfaces file. You can install separate Sybase installation directories anddistinct interfaces files on client file servers on each network to allowusers to connect to the correct network address. Instead of altering theDSQUERY name the clients use, you maintain one DSQUERY name forall clients, on all networks, and alter each network’s interfaces fileaccordingly.

This method assumes that:

• You have complete control over what the Sybase installation clientssee on each network.

• The interfaces file (at the very least) is not shared or copied amongSybase installations on different networks.

Using this method, if the interfaces file examples shown in “Sampleinterfaces Files for Multiple Network Handlers” on page 48 were adaptedfor this single DSQUERY method, they would look like the followingexample. The following example shows an interfaces file on the“corporate” network in a homogeneous environment:

#PRODUCTION server network1PRODUCTION<tab>3<tab>3<newline><tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000

49


<tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000<tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000

#PRODUCTION server network1PRODUCTION<tab>3<tab>3<newline><tab>query tcp ether ZEPPO 6464<tab>master tcp ether ZEPPO 6464<tab>master decnet ether CHICO 150

# PRODUCTION server network1PRODUCTION<tab>3<tab>3<newline><tab>query tcp ether SERV_CORPNET 4559<tab>master tcp ether SERV_CORPNET 4559<tab>master tcp ether SERV_ENGNET 5479

The interfaces file would look like the following example on the“engineering” network:

#PRODUCTION server on network2PRODUCTION<tab>3<tab>3<newline><tab>query tli tcp /dev/tcp \x0002130a83d601f70000000000000000<tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000<tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000

#PRODUCTION server network2<newline>PRODUCTION<tab>3<tab>3<newline><tab>query decnet ether CHICO 150<tab>master tcp ether ZEPPO 6464<tab>master decnet ether CHICO 150

# PRODUCTION server network2<newline>PRODUCTION<tab>3<tab>3<newline><tab>query tcp ether SERV_ENGNET 5470<tab>master tcp ether SERV_CORPNET 4559<tab>master tcp ether SERV_ENGNET 5479

The “query” line in each file name is different, depending on thenetwork to be used.

The full “master” entry is present in both files. This is allowed becauseonly Adaptive Server will use the “master” lines. Assuming that theserver host machine can see both networks (both host names areinterchangeable), it does not matter which interfaces file is used forAdaptive Server start-up.

Using Different DSQUERY Names

H To use different DSQUERY names for each network listener:

1. Choose an additional server name.

50


You can concatenate the original server name and the network name.For example, if your server is named PRODUCTION, you can choosethe names PRODUCTION_network1 and PRODUCTION_network2.

2. Do one of the following:

• For PC clients, use sqledit to create multiple sql.ini file entries forthe server, one for each network. In the following example, youcreate one entry for PRODUCTION_network 1 and one forPRODUCTION_network2. For more information, see the OpenClient documentation for your client platform.

• For UNIX clients, you can edit the interfaces files with a texteditor. From the server’s interfaces files, copy the server name lineand the “master” line for each network into the client interfacesfile. Add the appropriate server name for each entry, and change“master” to “query.”

Clients on each network must use the DSQUERY value thatcorresponds to the network the client is on. In the followingexample, either PRODUCTION_network1 orPRODUCTION_network2 can be used.

# Client entry for PRODUCTION on network1PRODUCTION_network1<tab>3<tab>3<newline><tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000# Client entry for PRODUCTION on network2PRODUCTION_network2<tab>3<tab>3<newline><tab>query tli tcp /dev/tcp \x0002130a83d601f70000000000000000

# Client entry for PRODUCTION on network1PRODUCTION_network1<tab>3<tab>3<newline><tab>query tcp ether zeppo 6464# Client entry for PRODUCTION on network2PRODUCTION_network2<tab>3<tab>3<newline><tab>query decnet ether chico 150

# Client entry for PRODUCTION on network1PRODUCTION_network1<tab>3<tab>3<newline><tab>query tcp ether serv_corpnet 4559

# Client entry for PRODUCTION on network2PRODUCTION_network2<tab>3<tab>3<newline>query tcp ether serv_engnet 5479

51


Configuring for Query Port BackupAnother use for multiple network interfaces is to provide a backup incase of network failure. If a client is connected to a server via twonetworks, the client can establish a connection via the second network ifthe first one goes down.

H To configure Adaptive Server for query port backup:

1. Install multiple “master” and “query” lines in a server entry in theinterfaces file.

Adaptive Server listens for connections at both ports. Clients lookingfor a host name and a port number for a connection to an AdaptiveServer will try the port on each “query” line in order, until theyestablish a connection.

The following example shows how to configure a backup networkthat will be used only if the normal connection fails. The secondnetwork is named “network2”.

# PRODUCTION serverwith two network listenersPRODUCTION<tab>3<tab>3<newline><tab>mastertli tcp /dev/tcp \x0002130a83d601f60000000000000000<tab>master tlitcp /dev/tcp \x0002130a83d601f70000000000000000<tab>query tli tcp /dev/tcp\x0002130a83d601f60000000000000000<tab>query tli tcp /dev/tcp \x0002130a83d601f70000000000000000

#PRODUCTION server with two network listenersPRODUCTION<tab>3<tab>3<newline><tab>querytcp ether ZEPPO 6464<tab>query decnet ether CHICO 150<tab>mastertcp ether ZEPPO 6464<tab>master decnet ether CHICO 150

# PRODUCTION server with two network listenersPRODUCTION<tab>3<tab>3<newline><tab>mastertcp ether SERV_CORPNET 4559<tab>master tcp ether SERV_ENGNET 5479<tab>querytcp ether SERV_CORPNET 4559<tab>query tcp ether SERV_ENGNET 5479

2. Configure PC client interfaces files with the appropriate multiple“query” entries, as described in the Open Client documentation. Forclient interfaces files in a homogeneous environment, you can copythe entire interfaces file entry for the Adaptive Server into the clientinterfaces file.

52


A connection on the secondary port occurs only if the corporatenetwork is disabled, or the if corporate network interface on the hostmachine fails or is shut down due to a network-related failure.

53


54

Chapter 4

Modifying the Interfaces File

This chapter explains how to use the dsedit and dscp utilities to edit theAdaptive Server interfaces file. Topics covered are:

• Using dsedit 55

• Using dscp 61

Using dsedit

dsedit is an X-Windows-based graphical tool that lets you view and editserver entries in the interfaces file.

If your system does not have X-Windows, use dscp to configure serverentries in the interfaces file. See “Using dscp” on page 61.

Topics covered are:

• Starting dsedit 55

• Opening an Editing Session 56

• Adding, Viewing, and Editing Server Entries 58

• Troubleshooting dsedit 60

Starting dsedit

Before starting dsedit, make sure that you have UNIX write permission onthe interfaces file.

If you are running dsedit from a remote machine, make sure that theDISPLAY environment variable is set so the dsedit screens will show onyour machine instead of on the remote machine.

H To set the DISPLAY environment variable:

1. Log into the remote machine.

2. Enter the following command:

setenv DISPLAY your_machine_name :0.0

55

Chapter 4 Modifying the Interfaces File

H To start dsedit :

• Enter the following command:

$SYBASE/bin/dsedit

The Select a Directory Service screen appears. This screen lets youopen editing sessions for the interfaces file. The full path name of thedefault interfaces file is shown in the Interfaces File to Edit box. Thefull path name of the configuration file is shown below it.

Opening an Editing Session

H To open the default interfaces file for editing:

1. Select Sybase Interfaces File.

2. Click OK.

H To open a file other than the default interfaces file:

1. Select Sybase Interfaces File.

2. Edit the displayed file name.

3. Click OK.

The Directory Service Session window appears.

You can open multiple interfaces file sessions with different files.

Figure 4–1 shows an example of the Directory Service Session screen.

56

Using dsedit

Figure 4–1: Directory Service Session screen

The Directory Service Session screen displays the full path name of theinterfaces file and lists the server entries contained within it.

Add new server entry – Displays the Server Entry Editor window, whereyou specify the name and network addresses for a new server entry.

Modify server entry – Lets you view and modify the network addressesfor a selected server entry. To view or modify a server entry, select theserver in the list, then click Modify server entry to display the server’sattributes in the Server Entry Editor window.

Copy server entry – Lets you copy one or more entries to anotherinterfaces file.

Close Session – Closes the session window and writes changes to theinterfaces file.

For procedures on using these buttons, see “Adding, Viewing, andEditing Server Entries” on page 58.

Clicking the Add new server entry or Modify server entry button in theSession screen displays the Server Entry Editor screen.

You use the Server Entry Editor window to view or edit server entries inan interfaces file.

57


Server name – If you are adding a server entry, type the name of thenew server. If you are editing a server entry, you can edit the name fieldto rename the server. The new name cannot exist already in theinterfaces file.

Available network transports – A list of the network addresses wherethe server accepts client connections. Do any of the following:

• To create a new address, click Add network transport. See “Addingor Editing Network Transport Addresses” on page 59.

• To edit an existing address, click Modify network transport. See“Adding or Editing Network Transport Addresses” on page 59.

• To remove a selected network address, click Delete networktransport.

• To rearrange the order of addresses in the list, click Move networktransport up or Move network transport down.

OK – Commits your changes and closes the window. Changes to theinterfaces file are not applied until you close the session using the Closesession button in the Directory Service Session screen.

Cancel – Closes the window and discards any edits.

Adding, Viewing, and Editing Server EntriesTo perform the procedures in this section, open the interfaces sessionwindow. For details, see “Opening an Editing Session” on page 56.

♦Note After performing each procedure in this section, you must click on CloseSession to apply your edits to the interfaces file. Clicking this buttonalso closes the interfaces session window.

H To add a new server entry:

1. Click on Add new server entry.

The Server Entry Editor window appears.

2. Specify the name and network addresses for a new server entry.

H To view or modify a server entry:

1. Click on Modify server entry.

The Server Entry Editor window displays the server’s attributes.

58

Using dsedit

2. Modify the attributes as desired.

H To copy a server entry to another interfaces file:

1. Use one of the following methods to select the entries to copy:

• To copy a single entry, click it once.

• To copy a range of consecutive entries, click the first entry in therange, press and hold down Shift, and click the last entry in therange. (You can also select “backwards” by clicking the last entry,holding down Shift, and clicking the first entry.)

• To select multiple, nonconsecutive entries, press and hold downthe Ctrl key while you click each entry.

2. Click Copy server entry.

3. Select the Sybase interfaces file from the list.

4. Edit the displayed file name.

5. Click OK.

Adding or Editing Network Transport Addresses

The Network Transport Editor window allows you to view, edit, orcreate the transport addresses at which a server accepts clientconnections. This window displays the name of the server entry for theaddress and allows you to configure the following items:

• Transport type – Specifies the protocol and interface for the address.For all platforms except Digital UNIX, values are tcp, tli tcp, tli spx, andspx. For Digital UNIX, values are decnet, tcp, and tli tcp.

• Address information – Depending on the transport type, differentaddress components are required. The following sections discussaddress formats in detail.

TCP/IP AddressesThe address information for a TCP/IP entry consists of a host name (orIP address) and a port number (entered as a decimal number). For tlitcp-formatted interfaces entries, the host’s IP address and the portnumber are converted to the 16-byte hexadecimal representation requiredfor tli tcp-formatted interfaces entries.

59


In interfaces entries, use tli tcp for:

• All pre-10.0 clients on platforms that use tli-formatted interfacesentries

• Adaptive Server or Replication Server release 11.0.x or earlier onplatforms that use tli-formatted interfaces entries

Use tcp for other clients and servers.

To indicate a TCP/IP address choose tcp or tli tcp from the TransportType menu.

SPX/IPX AddressesSPX/IPX addresses allow Adaptive Server to listen for connections fromclient applications running on a Novell network. SPX/IPX addressesconsist of the following information:

• Host address – An 8-digit hexadecimal value representing the IPaddress of the computer on which the server runs. Each componentof the dot-separated decimal IP address format maps to 1 byte in thehex address format. For example, if your host’s IP address is128.15.15.14, enter “800F0F0E” as the SPX/IPX host address value.

• Port number – The port number, expressed as a 4-digit hexadecimalnumber.

• Endpoint – The path for the device file that points to the SPX devicedriver. Defaults to /dev/mspx on Solaris and /dev/nspx on any otherplatform. If necessary, adjust the path so that it is correct for themachine on which the server runs. The default path is based on theplatform on which you are running dsedit.

To indicate an SPX/IPX address choose tli spx or spx from the TransportType menu.

Troubleshooting dsedit

This section lists some common problems and describes how to correctthem.

60

Using dscp

The dsedit Utility Does Not Start

Check for the following:

• The SYBASE environment variable is not set or points to the wrongdirectory.

• X11 is not configured correctly. If you are running dsedit on a remotehost, make sure that X11 clients on the remote host can connect to theX11 server on your own machine. See your X11 documentation formore troubleshooting information. If X11 is not available, use dscpinstead of dsedit.

Error Message: “Unable to open X display”

dsedit might not work if the display machine is set up to reject X11connections from remote hosts. If this is the problem, you will see amessage similar to the following:

Unable to open X display. Check the value of your$DISPLAY variable. If it is set correctly, use the’xhost +’ command on the display machine to authorizeuse of the X display. If no X display is available,run dscp instead of dsedit.

This error may be caused by either of the following situations:

• The value for the DISPLAY environment variable is not enteredcorrectly or is not set.

Solution: Enter the DISPLAY environment variable correctly.

• You are not authorized to open windows on the machine to whichDISPLAY refers.

Solution: Run the command "xhost +’ on the display machine.

Cannot Add, Modify, or Delete Server Entries

Check for permissions problems with the interfaces file. To editinterfaces entries, you must have write permission on both the interfacesfile and the Sybase installation directory.

Using dscp

dscp is a command line utility that you can use to view and edit serverentries in the interfaces file. This section covers the following topics:

61


• Starting dscp 62

• Getting Help on dscp 62

• Using a dscp Session 62

• Adding and Modifying Server Entries 64

• Copying Server Entries 67

• Deleting Server Entries 69

• Viewing Contents of Server Entries 69

• Listing Server Entries 68

• Exiting dscp 70

Starting dscp

H To start dscp :

• Enter:

$SYBASE/bin/dscp

The dscp prompt, >>, appears.

Getting Help with dscp

To view the dscp help screen, enter one of the following commands:

help

h

?

Using a dscp SessionBefore you can view, add, or modify server entries, you must open asession so that you can interact with the interfaces file.

You can have multiple sessions open at one time.

62

Using dscp

Opening a Session

H To open a session with the interfaces file:

• Enter:

open InterfacesDriver

When you open a session, dscp provides the session’s number. Forexample, if you open a session using the open InterfacesDriver command,dscp displays the following message:

ok

Session 1 InterfacesDriver>>

Listing Sessions

H To list all open sessions:

• Enter:

sess

Switching Between Open Sessions

H To switch to another open session:

• Enter:

switch sess

where sess is the session number.

For example, if you enter:

switch 3

you are switched to session 3. The switch keyword is optional. Forexample, entering:

3

also switches you to session 3.

63


Closing a Session

H To close a session:

• Enter:

close sess

where sess is the session number.


close 3

session 3 is closed.

If you do not specify a session number, dscp closes the current session.

Adding and Modifying Server EntriesAfter you open a session, you can add or modify server entriesassociated with that session.

♦Note When you add or modify a server entry, dscp automatically creates ormodifies both master and query lines. The master line and the query lineof an interfaces file entry contain identical information.

Each server entry is made up of a set of attributes. When you add ormodify a server entry, dscp prompts you for information about eachattribute. Table 4–1 describes each attribute:

Table 4–1: Server attributes

Attribute Type of ValueDefault Value and ValidValues

Can be edited whenadding or modifying aserver entry

Server ObjectVersion

Integer 110 Adding: NoModifying: No

Server Name Character string n/a Adding: n/aModifying: No

Server Service Character string SQL SERVER Adding: YesModifying: No

64

Using dscp

Attribute Type of ValueDefault Value and ValidValues

Can be edited whenadding or modifying aserver entry

Server Status Integer 4Valid values are:1 Active2 Stopped3 Failed4 Unknown

Adding: NoModifying: No

Transport Type Character string tcpValid values are:decnet, spx, tcp, tli spx,tli tcp

Adding: YesModifying: Yes

TransportAddress

Character string NoneValid values are characterstrings in a formatrecognized by thespecified transport type


SecurityMechanism

Character stringNote: You can add up to20 security mechanismstrings for each serverentry.

NoneValid values are characterstrings associated withobject identifiers definedin the user’s objectid.dat.


Adding Server Entries

H To add a server entry:

1. Enter:

add servername

You are now in add mode. You can continue to add server entries,but you cannot execute any other dscp commands until you exit thismode. While in add mode, dscp prompts you for information aboutservername.


• Enter a value for each attribute, or

• Press Return to accept the default value, which is shown inbrackets [ ].


add myserver

dscp prompts for the following information:

65


Service: [SQL Server]Transport Type: [tcp] tcpTransport Address: victory 8001Security Mechanism []:

A server entry can have up to 20 transport type/addresscombinations associated with it.

For a description of the server attributes, see Table 4–1.

H To exit add mode:

• Enter:

#done

Modifying Server Entries

You cannot use dscp to modify the Version, Service, and Status entries inthe interfaces file.

H To modify a server entry:

1. Enter:

mod servername

You are now in modify mode. You can continue to modify serverentries, but you cannot execute any other dscp commands until youexit this mode. In modify mode, dscp prompts you for informationabout servername.


• Enter a value for each attribute, or

• Press Return to accept the default value, which is shown inbrackets [ ].


mod myserver

dscp prompts for the following information:

Version: [1]Service: [SQL Server] Open ServerStatus: [4]Address:

Transport Type: [tcp]Transport Address: [victory 1824] victory 1826

66

Using dscp

Transport Type: [tcp]Transport Address: [victory 1828]Transport Type: []

Security Mechanism []:

For a description of the server attributes, see Table 4–1, “Serverattributes,” on page 64.

H To delete an address:

• Enter:

#del

H To exit modify mode:

• Enter:

#done

Copying Server Entriesdscp allows you to copy server entries within a session and between twosessions. You have four options when copying a server entry.

You can copy:

• A server entry to a new name in the current session

• A server entry to a different session

• A server entry to a new name in a different session

• All entries in the current session to a different session

Creating New Server Entries Within a Session By Copying

H To create a new server entry within a session by copying:

• Enter:

copy name1 to name2


copy myserver to my_server

dscp creates a new entry, “my_server”, that is identical to “myserver.”You can then modify the new entry and leave the original intact.

67


Copying Entries Between Sessions

H To copy a server entry without changing the name:

• Enter:

copy name1 to sess


copy myserver to 2

dscp copies the “myserver” entry in the current session to session 2.

H To copy a server entry and rename it:

• Enter:

copy name1 to sess name2


copy myserver to 2 my_server

dscp copies the “myserver” entry in the current session to session 2and renames it “my_server.”

Copying All Entries to a Different Session

H To copy all entries in the current session to a different session:

• Enter:

copyall sess


copyall 2

dscp copies all entries in the current session to session 2.

Listing Server Entries

H To list the names of server entries associated with a session:

• Enter:

list

68

Using dscp

H To list the attributes of server entries associated with a session:

• Enter:

list all

For a description of server attributes, see Table 4–1.

Viewing Contents of Server Entries

H To view the contents of a server entry:

• Enter:

read servername


read myserver

the following information is displayed:

DIT base for object: interfacesDistinguish name: myserverServer Version: 1Server Name: myserverServer Service: SQL ServerServer Status: 4 (Unknown)Server Address:

Transport Type: tcpTransport Addr: victory 1824Transport Type: tcpTransport Addr: victory 1828

For a description of the server attributes, see Table 4–1, “Serverattributes,” on page 64.

Deleting Server EntriesYou can delete one entry or all entries associated with a session.

H To delete one server entry:

• Enter:

del servername


69


del myserver

dscp deletes the entry for “myserver.”

H To delete all entries associated with a session:

• Enter:

delete-all

Exiting dscp

H To exit dscp :

• Enter one of the following commands:

exit

quit

Quick Reference for dscp Utility Commandsdscp allows you to perform functions by entering commands at the dscpprompt. Table 4–2 provides a quick reference to these commands.

Table 4–2: dscp commands

Command Description

add servername Adds server entry servername in the current session.dscp prompts you for information about servername. Press Return toaccept the default value, which is shown in square brackets [ ]. Enter“#done” to exit add mode.

addattr servername Adds an attribute to the server entry servername in the current session.

close [sess] Closes a session identified by the sess number. If you do not specifysess, closes the current session.

config Displays configuration information related to your Sybaseenvironment.

copy name1 to {name2| sess | sess name2}

Copies server entry name1 in the current session to:

• Server entry name2 in the current session,

• Session sess, or

• Server entry name2 in session sess.

copyall to sess Copies all server entries in the current session to session sess.

70

Using dscp

Command Description

del servername Deletes server entry servername in the current session.

delete-all Deletes all server entries in the current session.

exit Exits dscp.

help, ?, h Displays the on-line help.

list [all] Lists the server entries for the current session.To list the names of the entries, use the list command. To list theattributes for each entry, use the list all command.

mod servername Modifies server entry servername in the current session.dscp prompts you for information about servername. Press Return toaccept the default value, which is shown in square brackets [ ]. Enter“#done” to exit modify mode.

open [dsname] Opens a session for the specified directory service, where dsname isthe directory service name. If you do not specify a value for dsname,this command opens a session for the default directory service.To open a session, specify the value “InterfacesDriver” for dsname.

quit Exits dscp.

read servername Displays the contents of server entry servername.

sess Lists all open sessions.

[switch] sess Makes session number sess the current session.

71


72

Chapter 5

Localization Issues

This chapter provides background information about Sybase’slocalization support as well as task information for reconfiguringcharacter sets, sort orders, and language modules.

Topics covered include:

• Localization Support 73

• Character Sets 74

• Sort Orders 81

• Configuring for Localization 89

• Language Modules 92

• Conversions Between Server and Client 95

• Changing the Language, Character Set, or Sort Order 96

Localization SupportLocalization is the process of setting up an application to run in aparticular language or country environment. Adaptive Server supportslocalization for international customers and customers withheterogeneous environments.

Sybase provides the following localization support:

• Data support – Adaptive Server comes with a base set of characterset and sort order definition files that it uses to process the charactersused in different languages. The base set provides data processingsupport for the major business languages in Western Europe, EasternEurope, the Middle East, Latin America, and Asia.

For character sets that are not included in the base set, you canpurchase the Sybase Character Sets on a separate CD. AdaptiveServer also provides a Unicode conversion mechanism, which allowsyou to use new character sets by adding an external table.

73

Chapter 5 Localization Issues

• Translated system messages – Adaptive Server has languagemodules for Brazilian, Chinese (Simplified), French, German,Japanese, Korean, Portuguese, and Spanish.

• Translated documentation – Translated documentation is available inChinese (Simplified), French, German, Japanese, Korean, and Spanish.

By default, Adaptive Server and Backup Server have:

• Character set definition files for Western European languages

• Sort order definition files for Western European character sets

• us_english system messages

Character SetsIn heterogeneous environments, Adaptive Server and Backup Server mayneed to communicate with other servers or applications running on aplatform that has a different default character set. You can preventpossible data conversion errors by installing the other platform’s defaultcharacter set as the default for Adaptive Server and Backup Server.

Alternatively, you can install additional character sets in Adaptive Serverto allow Adaptive Server to convert data from servers and clients thatuse other character sets. For character set conversion paths, see“Conversion Paths Supported” in chapter 14, “Configuring Client/ServerCharater Set Conversions” in the System Administration Guide.

Adaptive Server includes character set definition files (charset.loc files) inthe Sybase installation directory for each character set in the charsetsdirectory. These files permit you to configure your system for optimumserver-client and server-server communication.

Default Character Sets for ServersThe default character set is the character set in which data is encodedand stored on the Adaptive Server databases. At installation time,Adaptive Server and Backup Server have character set definition files forthe character sets shown in Table 5–1. These character sets support theWestern European languages on the specified platforms.

74

Character Sets

Table 5–1: Platforms and their default character sets

Server Platform Default Character Set

Digital UNIX iso_1 (ISO 8859-1)

HP-UX iso_1 (ISO 8859-1)

IBM RS/6000 iso_1 (ISO 8859-1)

NCR MP-Ras iso_1 (ISO 8859-1)

SGI iso_1 (ISO 8859-1)

Sun Solaris iso_1 (ISO 8859-1)

UnixWare iso_1 (ISO 8859-1)

Changing the Default Character Set for ServersYou can select any character set as the default on Adaptive Server orBackup Server. Determine Adaptive Server’s default character set basedon the character set used by your client. For example, if most of yourclients use Code Page 850, specify Code Page 850 on your server tominimize the amount of data conversion that has to occur.

If your server is operating in a heterogeneous environment, choose acharacter set that will interoperate with all the character sets needed.Often, this will be Unicode (UTF8).

WARNING! Make all changes to the character set and sort order for a new AdaptiveServer before creating any user databases or making any changes to theSybase-supplied databases. Changing the character set and sort orderafter data or data structures have been added to Adaptive Server cancause incorrect behavior. If you need to change the character set or sortorder after you have added data, see the System Administration Guide.

For the name of the default character set for each platform, see “DefaultCharacter Sets for Servers” on page 74. For a list of the client charactersets supported by Adaptive Server, see “Supported Character Sets” onpage 76.

For more information about character sets, see the System AdministrationGuide and the Adaptive Server Reference Manual.

75


Supported Character SetsThe following categories of character sets are supported by AdaptiveServer version 11.5.1:

• Arabic - see Table 5–2on page 77

• Chinese - see Table 5–3on page 77

• Cyrillic - see Table 5–4on page 77

• Latin Characters - see Table 5–5on page 77

• Greek - see Table 5–6on page 78

• Hebrew - see Table 5–7on page 78

• Japanese - see Table 5–8on page 79

• Korean - see Table 5–9on page 79

• Thai - see Table 5–10on page 79

• Turkish - see Table 5–11on page 79

The tables indicate information on whether the character set:

• Converts without using UnilibTM conversion. The character set is oneof the default character sets that come with Adaptive Server, anddoes not require the Unilib converter.

• Is built into Adaptive Server. It does not need to be loaded from theCD. It is installed as part of the Adaptive Server installation.

• Is not built into Adaptive Server. It must be loaded from the SybaseCharacter Sets CD. It is not installed as part of the Adaptive Serverinstallation. If you want to use this character set, you must install it.

♦Note These character sets are for use on client machines only, not on AdaptiveServer. You cannot install any character set on the server other thanthose specifically created for it by Sybase and shipped with the currentpackage or with the Sybase Character Sets CD.

76

Character Sets

Table 5–2: Arabic client character sets supported by Adaptive Server

Character Set Unilib NotRequired

Built–In Load fromCD

Description

cp864 x PC Arabic

cp1256 x MS Windows Arabic

iso88596iso8859-6:19878859_6

xISO 8859-6 Latin/Arabic

Table 5–3: Chinese client character sets supported by Adaptive Server



Description

cp950x

PC (MS) TraditionalChinese

euccns x EUC CNS encoding =TradChin with exts

eucgb x EUC GB encoding =SimpChin

Table 5–4: Cyrillic client character sets supported by Adaptive Server



Description

cp855 x x IBM PC Cyrillic

cp866 x x PC Russian

cp1251 x x MS Windows 3.1 Cyrillic

iso88595, iso_8859-5:1988,8859_5 x x

ISO 8859-5 Latin/Cyrillic

koi8 x x KOI-8 Cyrillic

mac_cyr x x Macintosh Cyrillic

Table 5–5: Latin Characters client character sets supported by Adaptive Server



Description

ascii8 x x US ASCII, with 8-bitdata, ISO 646

cp437 x x IBM CP437 - U.S. code set

cp850x x

IBM CP850 - Europeancode set

77




Description

cp852 x x PC Eastern Europe

cp860 x PC Portuguese

cp863 x IBM PC Canadian Frenchcode page

cp1250 x x MS Windows 3.1 EasternEuropean

cp1252 x MS Windows 3.1 US(ANSI)

iso_1 x x ISO 8859-1 Latin-1

iso88592x x

ISO 8859-2 Latin-2Eastern Europe

macx x

Standard Macintoshcoding

mac_eex x

Macintosh EasternEuropean

roman8 x x HP Roman-8

Table 5–6: Greek client character sets supported by Adaptive Server



Description

cp869 x x IBM PC Greek

cp1253 x x x MS Windows 3.1 Greek

greek8 x x x HP Greek-8

iso88597, iso_8859-7:1987,8859_7 x x ISO 8859-7 Latin/Greek

macgrk2 x x Macintosh Greek

Table 5–7: Hebrew client character sets supported by Adaptive Server



Description

cp1255 x MS Windows Hebrew

78

Character Sets

Table 5–8: Japanese client character sets supported by Adaptive Server



Description

cp932 x IBM J-DBCS:CP897 +CP301 (Shift-JIS)

deckanji x x x DEC UNIX JIS encoding

eucjis x x x EUC JIS encoding

sjis x x x Shift JIS (no extensions)

Table 5–9: Korean client character sets supported by Adaptive Server



Description

euckscx

EUC KSC Koreanencoding = CP949

Table 5–10: Thai client character sets supported by Adaptive Server



Description

tis620 x TIS-620 Thai standard

cp874 x

Table 5–11: Turkish client character sets supported by Adaptive Server



Description

cp857 x x IBM PC Turkish

cp1254 x x MS Windows 3.1 Turkish

iso88599x x

ISO 8859-9 Latin-5Turkish

mackturk x x Macintosh Turkish

turkish8 x x x HP Turkish-8

Using Unicode Character ConversionThe Unicode conversion engine is part of Unilib. Unilib provides efficientconversions between 16-bit Unicode (UTF–16) and a wide range andnumber of character sets and encodings. In addition to many built-inconversions, Unilib provides external conversion tables that can be loaded

79


by name, allowing for extensibility. Unilib provides a comprehensivelibrary for accessing attributes of each character set and conversion.

For existing Adaptive Server installations that have the UTF-8 characterset installed, the Unicode conversion functionality is the default.

H To use the Unicode Character conversion functionality:

1. If the default conversion tables do not meet your requirements, loadthe Unicode conversion tables.

See “Loading the Unicode Conversion Tables” on page 80.

2. Activate Unicode character conversion.

For details, see “Activating Unicode Character Conversion” on page81.

Loading the Unicode Conversion Tables

Conversion tables can be loaded:

• From memory in the existing Adaptive Server conversion code

• From memory in Unilib built–in conversions

• From files on disk via Unilib

The Unicode conversion tables are located in:

$SYBASE/charsets/unicode/*.uct

Resizing the Unilib Cache

If your site uses multiple conversions (such as Japanese, Chinese, orKorean), you may need a larger Unilib cache.

H To change the size of the Unilib cache:

• Enter:

sp_configure "size of unilib cache", cache_size

where cache_size is the size in kilobytes.

80

Sort Orders

Activating Unicode Character Conversion

H To activate Unicode Character Conversion for a new AdaptiveServer 11.5.1 installation:

• Enter one of the following commands:

sp_configure "enable unicode conversions", 1

When you use this command, Adaptive Server first searches for abuilt-in converter. If it finds one, Adaptive Server uses that converter.If it cannot find a built-in converter, Adaptive Server searches for anappropriate Unicode converter and uses it.

sp_configure "enable unicode conversions", 2

When you use this command Adaptive Server searches for anappropriate Unicode converter and uses that converter. It does nottry to find a pre-11.5.1 converter.

♦Note You will see the conversion behavior change only if you are using acharacter conversion that was not previously covered by the pre-11.5.1converters, such as iso_1 to roman8 or eucjis to sjis.

Disabling Character Conversion

H To disable character conversion:

• Enter:

sp_configure "disable character set conversion", 1

Sort OrdersYou can select a sort order (collating sequence) for your data accordingto the needs at your site. Adaptive Server includes sort order definitionfiles (.srt files) in the appropriate directory in the charsets directory. Theserver can support only one sort order at a time, so be sure to select asort order that will work for all of your clients.

81


WARNING! Make all changes to the character set and sort order for a new AdaptiveServer before creating any user databases or making any changes to theSybase-supplied databases. Changing the character set and sort orderafter data or data structures have been added to Adaptive Server maycause incorrect behavior. If you need to change the character set or sortorder after you have added data, see the System Administration Guide.

Available Sort OrdersThe sort order determines the collating sequence Adaptive Server uses toorder, compare, and index character data. Each character set comes withone or more sort orders. Sort orders are located in sort order definitionfiles (.srt files) that accompany your character set definition files.

♦Note Available sort orders vary according to the character set installed onAdaptive Server.

You can see the available sort orders for your character set by looking inthe .srt file for your language. The .srt files are stored in the followinglocation:

$SYBASE/charsets/ charset_name /*.srt

For a detailed explanation of localization files, see “Directories forLocalization Files” on page 89.

Table 5–12 describes the sort orders that you can specify at installationtime or at a later time using the sqlloc utility. Table 5–13on page 85describes the sort orders that come with the basic Adaptive Server.

82

Sort Orders

Table 5–12: Sort orders available in the basic Adaptive Server

Sort Order Name .srt File Name Description

Binary ordering bin.srt Sorts all data according to numeric byte values forthat character set. Binary order sorts all ASCIIuppercase letters before lowercase letters. Accentedor ideographic (multibyte) characters sort in theirrespective standards order, which may be arbitrary.All character sets have binary order as the default. Ifbinary order does not meet your needs, you canspecify one the other sort orders either at installationor at a later time by using the sqlloc utility.

Dictionary ordering dictionary.srt Case sensitive. Sorts each uppercase letter before itslowercase counterpart, including accented characters.Recognizes the various accented forms of a letter andsorts them after the associated unaccented letter.General purpose dictionary sort order for use withseveral Western-European languages includingEnglish, French, and German.

Dictionary order, caseinsensitive

nocase.srt Case insensitive dictionary sort order. Uppercaseletters are equivalent to their lowercase counterpartsand are intermingled in sorting results. For use withseveral Western-European languages includingEnglish, French, and German.

Dictionary order, caseinsensitive, accentinsensitive

noaccents.srt Case-insensitive dictionary sort order. Diacriticalmarks are ignored. For use with severalWestern-European languages including English,French, and German.

Dictionary order, caseinsensitive withpreference

nocasepref.srt Case-insensitive dictionary sort order, with casepreference for collating purposes. A word writtenwith uppercase letters is equivalent to the same wordwritten with lowercase letters. Uppercase andlowercase letters are distinguished only when youuse an order by clause. The order by clause sortsuppercase letters before it sorts lowercase. For usewith several Western-European languages includingEnglish, French, and German.

Note: Do not select this sort order unless yourinstallation requires that uppercase letters be sortedbefore lowercase letters in otherwise equivalentstrings for order by clauses. Using this sort ordercould cause poor performance in large tables when

the columns specified in an order by clause match thekey of the table’s clustered index.

83


Sort Order Name .srt File Name Description

Alternate dictionarysorting with casesensitivity

altdict.srt Case-sensitive alternate dictionary sort order withlowercase variants sorted before uppercase. For usewith several Western-European languages.

Alternate dictionarysorting with case andaccent insensitivity

altnoacc.srt Case-insensitive and accent-insensitive alternatedictionary sort order. For use with several WesternEuropean languages.

Alternate dictionarysorting with caseinsensitivity anduppercase preference

altnocsp.srt Case-insensitive alternate dictionary sort order withuppercase preference. For use with severalWestern-European languages.

Spanish dictionaryordering

espdict.srt Case-sensitive Spanish dictionary sort order. For usewith Spanish and most Latin American locales.

Spanishcase-insensitivedictionary order

espnoaccents.srt Spanish case-insensitive dictionary sort order. For usewith Spanish and most Latin American locales.

Spanish case andaccent insensitivedictionary order

espnocase.srt Spanish case-insensitive and accent-insensitivedictionary sort order. For use with Spanish and mostLatin American locales.

Scandinaviandictionary sortingwith case sensitivity

scandict.srt Case-sensitive dictionary sort order. For use withScandinavian languages.

Scandinaviandictionary sorting,case insensitive,uppercase preference

scannocp.srt Case-insensitive and accent-insensitive dictionarysorting, with uppercase preference. For use withScandinavian languages.

By default, each Western European character set that comes withAdaptive Server and Backup Server comes with the sort ordercombinations shown in Table 5–13

84

Sort Orders

Table 5–13: Sort order combinations for Western European languages

Language Available Sort Orders

All Western European languages • Binary sort order

EnglishFrenchGerman

• Accent insensitive, dictionary order, caseinsensitive

• Case insensitive, dictionary order, accentsensitive

• Case insensitive, dictionary order, accentsensitive, order with preference

• Dictionary order, case sensitive, accentsensitive

Spanish • Accent insensitive, dictionary order, caseinsensitive

• Case insensitive, dictionary order, accentsensitive

• Dictionary order, case sensitive, accentsensitive

Gathering Information About CollationThe following functions enable you to perform collation operations inyour application:

• sortkey – Generates binary values that you can use to order queryresults based on collation behavior. For details see, “Ordering QueryResults Based on Collation Behavior” on page 85.

• compare – Compares two character strings based on alternate collationrules. For details see, “Comparing Strings Based on AlternateCollation Rules” on page 87.

These functions can be nested and can be used anywhere that anexpression is allowed, including stored procedures and triggers.

Ordering Query Results Based on Collation Behavior

The sortkey function generates values that can be used to order resultsbased on collation behavior. The return value is a varbinary datatypevalue that contains coded collation information for the input string thatis retained from the sortkey function. This allows you to work withcharacter collation behaviors beyond the default set of Latin-characterbased dictionary sort orders and case or accent sensitivity.

85


For example, you can store the values returned by sortkey in a columnwith the source character string. When you want to retrieve the characterdata in the desired order, the select statement only needs to include anorder by clause on the columns that contained the results of runningsortkey. The sortkey function guarantees that the values it returns for agiven set of collation criteria work for the binary comparisons that areperformed on varbinary datatypes.

Syntax for sortkey

The syntax is:

sortkey( char_expression[,{ collation_name | collation_ID }])

where:

• char_expression can be one of the following:

– Character type (char, varchar, nchar, or nvarchar),

– Character variable, or

– Constant character expression (must be enclosed in single ordouble quotation marks)

• collation_name can be a quoted string or a character variable thatspecifies the collation to use.

• collation_ID is an integer constant or variable that specifies thecollation to use.

Rules for Using sortkey

The following rules apply when you use the sortkey function:

• char_expression must be composed of characters that are encoded inthe server’s default character set.

• char_expression can be an empty string. In this case, sortkey returns azero length varbinary value. Adaptive Server stores a blank for theempty string. Therefore, a real empty string has a different collationvalue than an NULL string from a database column.

• If char_expression is NULL, sortkey returns a NULL value.

• If you do not specify a value for collation_name or collation_ID, sortkeyassumes binary collation.

86

Sort Orders

♦Note sortkey may generate up to 6 bytes of collation information for each inputcharacter. Therefore, the result from using sortkey may exceed the 255byte length limit of the varbinary datatype. If this happens, the result istruncated to fit. Truncation removes result bytes for each input characteruntil the result string is less that 255 bytes. If this occurs, a warningmessage is issued, but the query or transaction that contained the sortkeyfunction continues to work.

Comparing Strings Based on Alternate Collation Rules

The compare function allows you to directly compare two character stringsbased on alternate collation rules.

Syntax for compare

The syntax is:

compare( char_expression1 , char_expression2[,{ collation_name | collation_ID }])

where:

• char_expression1 is the character expression you want to compare tochar_expression2.

char_expression2 is the character expression against which you want tocompare char_expression1

char_expression1 and char_expression2 can be one of the following:

– Character type (char, varchar, nchar, or nvarchar)

– Character variable

– Constant character expression (must be enclosed in single ordouble quotation marks)

• collation_name can be a quoted string or a character variable thatspecifies the collation to use.

• collation_ID is an integer constant or variable that specifies thecollation to use.

compare returns the following values, based on the collation rules youchose:

• 1 if char_expression1 is greater than char_expression2

• 0 if char_expression1 is equal to char_expression2

• -1 if char_expression1 is less than char_expression2

87


Rules for Using compare

The following rules apply when using the compare function:

• Both char_expression1 and char_expression2 must be characters that areencoded in the server’s default character set.

• Either char_expression1 or char_expression2, or both, can be emptystrings. If both strings are empty, then they are equal and a 0 value isreturned. If char_expression1 is empty, a -1 is returned. Ifchar_expression2 is empty, a 1 is returned.

compare does not equate empty strings and strings with just spaces asAdaptive Server does. compare uses the sortkey function to generatecollation keys for comparison. Therefore, a truly empty string, a stringwith one space, or a string with two spaces will not compare equally.

• If either char_expression1 or char_expression2 is NULL, then the resultwill be NULL.

• If you do not specify a value for collation_name, compare assumesbinary collation.

• If you do not specify a value for collation_ID, compare assumes binarycollation.

88

Configuring for Localization

Configuring for LocalizationBy default, svrbuild configures Adaptive Server and Backup Server with:

• The us_english language

• The default character set for your platform

• Binary sort order

During the Adaptive Server installation process, you can specify adifferent language, character set, and sort order.

Directories for Localization FilesFigure 5–1 illustrates the structure of the localization files. It does notshow a complete listing of all the files.

Figure 5–1: Localization files in the Sybase installation directory

$SYBASE charsets

charset_name

*.srt files

charset.loc

locales

locales.dat

language_name*.loc filescharset_name

language_name....

charset_name...

charset_name...

collate unicode *.ust files

unicode *.uct files

About the locales Directory

The $SYBASE/locales directory contains a subdirectory for each availablelanguage. Each language subdirectory contains a subdirectory for eachcharacter set available with that language. The .loc files in these

89


subdirectories enable Adaptive Server or Backup Server to report errorsin a specific language encoded in a specific character set. There are avariety of .loc files in each subdirectory. Most of these files containtranslated error messages for a specific product or utility. The common.locfile in each subdirectory contains localized information used by allproducts, such as local date, time, and money formatting.

The $SYBASE/locales directory also contains the locales.dat file, whichcontains entries that associate platform-specific locale names with Sybaselanguage and character set combinations.

About the charsets Directory

Files in the $SYBASE/charsets/charset_name directory contain informationrelated to particular character sets, such as the definition of the characterset and any sort orders available for that character set.

About the locales.dat FileYou can edit the locales.dat file to change the default language orcharacter set for a platform, or to add new associations between platformlocale names and Sybase language and character set names.

Format of locales.dat File Entries

Each entry in the locales.dat file links a platform-specific locale definitionto a Sybase language and character set combination. Each entry has thefollowing format:

locale = platform_locale , syb_language , syb_charset

where:

• platform_locale is the platform-specific keyword for a locale. See youroperating system manual for appropriate values. When the localebeing defined is the default for the site, then platform_locale is“default.”

• syb_language is the name of the language directory to be used (in$SYBASE/locales/language_name).

• syb_charset is the character set name used for determining characterset conversion and to identify the directory location of the messagefiles for clients (in $SYBASE/locales/language_name/charset_name).

90

Configuring for Localization

For example, the following entry specifies that the default locale usesus_english for the language and iso_1 for the character set:

locale = default, us_english, iso_1

How Client Applications Use locales.dat

Client applications use the locales.dat file to identify the language andcharacter set to use. When a client application starts, it checks theoperating system locale setting, and then checks the locales.dat file to seeif that setting is appropriate for Adaptive Server. For Example, a localeentry for French can look like the following:

locale = fr_FR, french, iso_1

When the client connects to Adaptive Server, the language and characterset information is passed to Adaptive Server in the login record. Then,Adaptive Server:

• Uses the character set information (for example, iso_1) to identify theclient’s character set and verifies whether it can convert characterdata to this character set.

• Uses the language (for example, “french”) and character setinformation (iso_1) to see if it has messages in the client’s language.

♦Note Adaptive Server software comes with some locale entries already definedin the locales.dat file. If these entries do not meet your needs, you caneither modify them or add new locale entries.

Editing the locales.dat File

H To edit the locales.dat file:

1. Make a copy of the original, unedited locales.dat file, in case you haveproblems with the edited version.

2. Find the section for your platform.

3. Make sure the section contains an entry for the language(syb_language) and character set (syb_charset) combination you want touse.

91


♦Note The value for platform_locale must match the value required by youroperating system. If locales definitions in your system configuration filesdo not match the Sybase locale definitions, your applications will not runproperly.

For example, if you want your Open Client messages to appear inFrench, and Adaptive Server is using the roman8 character set, youwould check the locales.dat entries for the your platform and look forthe following entry:

locale = fr_FR, french, roman8

4. If the entry for your locale does not exist, add the required entry ormodify an existing entry.

5. Save the edited file.

Language ModulesIf you want Adaptive Server error messages to be displayed in alanguage other than us_english, you must purchase and install theappropriate Language Module.

Language Module features are located in the Sybase installation directory($SYBASE) under the locales and charsets subdirectories.

The language, character set, and sort order files to support a newlanguage are automatically loaded into the Sybase installation directorywhen a Language Module is installed.

Installing a New Language Module

H To install a new Language Module:

1. Prepare your operating system according to the instructions in theinstallation documentation for your platform. (These preparations arenot necessary if you completed them when you installed or upgradedAdaptive Server.)

2. Load the Language Module software from the distribution media,according to the instructions in the installation documentation foryour platform. You must load this software into the same directorywhere you loaded Adaptive Server.

92

Limitations of Hankaku Katakana Conversion

3. See “Changing the Language, Character Set, or Sort Order” on page96 for instructions on reconfiguring the language, character set, andsort order for Adaptive Server or Backup Server.

Message LanguagesFor messages, us_english is installed as the default language in AdaptiveServer. If your clients require messages in a different language thanus_english, you must purchase and install the Language Module for thatlanguage.

During the installation of Adaptive Server, you can specify a defaultlanguage other than us_english for Adaptive Server. However, you musthave the Language Module for the language you specify.

Japanese Language ModuleThe Japanese Language Module includes the following multibytecharacter sets:

• eucjis – Extended UNIX Code for JIS-X0201 and JIS-X0208

• deckanji – DEC-Kanji Code for JIS-X0208

• sjis (Shift-JIS) – IBM/Microsoft Code for JIS-X0201 and JIS-X0208

Limitations of Hankaku Katakana ConversionThis section describes the limitations of Hankaku Katakana conversions.

Hankaku Katakana conversions have the following limitations and rules:

• Hankaku Katakana conversion is enabled only if Adaptive Server isusing EUC-JIS and clients are using Shift-JIS.

• Hankaku Katakana (half-width phonetic Japanese) character setconversion between Shift-JIS and EUC-JIS is not enabled by default inAdaptive Server. However, it is possible to enable Hankaku Katakanacharacter set conversion by turning on trace flag 2402 when startingthe Adaptive Server. Include “-T2402” on the command line in thescript used to start Adaptive Server.

• After Hankaku Katakana conversion is enabled, you cannot changethe conversion on a per-client basis. To turn off the conversion, either

93


remove “-T2402” from the script or use a different script with thetrace flag disabled; then restart Adaptive Server.

• If conversion is disabled for Hankaku Katakana, each unconvertedHankaku character is replaced with a question mark (?).

• The client application using Shift-JIS must recognize differentcharacter sizes when defining a table. Data that is longer than thecolumn length is truncated. No warning message appears.

• In an Adaptive Server using EUC-JIS, characters are stored in theEUC-JIS sort order. Zenkaku characters come after Hankakucharacters in the EUC character set. Therefore, Adaptive Server sortsHankaku first, followed by Zenkaku.

• If the column contains Hankaku Katakana, the Adaptive Server usingEUC-JIS sends the client application using Shift-JIS the convertedcharacters, using nulls to pad the length.

• Hankaku Katakana can be used in logical expressions, for example:

select * from tablewhere column="Hankaku_Katakana_here"

• The Transact-SQL search functions treat Hankaku Katakana andZenkaku Katakana as different sets of characters. Katakana can beeither half-width (Hankaku) or full-width (Zenkaku) in both EUC-JISand Shift-JIS. For example, if the data in a table is stored in HankakuKatakana, the following SQL statement returns no rows, even if bothHankaku and Zenkaku data have the same meaning:

select * from tablewhere column="Zenkaku_Katakana_here"

• Hankaku Katakana cannot be used for procedure names or parameternames because the internal memory allocated for these names may beless than the length required by EUC-JIS.

• Although you can use bcp from a client application using Shift-JIS toan Adaptive Server using EUC-JIS, you cannot run bcp from Shift-JISclient applications containing Hankaku Katakana characters.

Hankaku Katakana Conversion and DatatypesThe following limitations apply to datatypes in Hankaku Katakanaconversion:

94

Conversions Between Server and Client

• Hankaku Katakana can be used only in char, varchar, nchar, nvarchar,and text datatypes.

• The char, varchar, nchar, nvarchar, and text datatypes stored in anAdaptive Server using EUC-JIS can be used for a Shift-JIS clientapplication. However, because one Shift-JIS Hankaku character usesone byte of storage and one EUC-JIS Hankaku character uses twobytes of storage, a client application using Shift-JIS can insert amaximum of 127 Hankaku Katakana characters, rather than the 255characters of an Adaptive Server using Shift-JIS. Inserting more than127 characters during conversion to EUC-JIS generates an errormessage.

• It is not recommended to use Hankaku Katakana for the sysnamedatatype, such as database names, table names, column names, andso on, because of the conversion length changes.

• If you plan to convert with Shift-JIS, do not use Hankaku Katakana intext datatypes that are larger than one data page (typically 2K). If thetext column contains Hankaku Katakana, and the character spans twopages in the database, the partial byte in the first page is notconverted. A warning message advises that the conversion did notsucceed. There is no problem converting EUC-JIS to EUC-JIS orShift-JIS to Shift-JIS.

Conversions Between Server and ClientIf Adaptive Server does not support the client’s language or characterset, the client can connect with the server, but no character conversionswill occur.

When a localized client application connects to Adaptive Server, theserver checks to see if it supports the client’s language and character set.If it does, then it automatically performs all character set conversion anddisplays Adaptive Server messages in the client’s language and characterset. If the language is not supported, use the user’s default language orAdaptive Server’s default language. If the character set is not supported,issue a warning, turn conversion off and set the language to us_english.

Backup Server ConversionsBackup Server returns messages to Adaptive Server in the client’slanguage and Adaptive Server’s character set. Adaptive Server then

95


issues the messages in the client’s language and character set. IfAdaptive Server or Backup Server does not support a client’s languageor character set, a warning message is displayed. Errors also occur if theBackup Server character set is not compatible with the Adaptive Servercharacter set.

WARNING! Single-byte and multibyte character sets are not compatible fornon-English data. To avoid conversion problems, configure AdaptiveServer and Backup Server with the same character set.

See the System Administration Guide for detailed information aboutsupported conversion paths.

Conversions in a Heterogeneous EnvironmentIn a heterogeneous environment, Adaptive Server and Backup Servermay need to communicate with clients that run on different platformsusing different character sets. To maintain data integrity, the serverconverts the code between the character sets. To enable automatic codeconversion, you need to install character set definition files on the serverfor all the character sets used by your clients, or use Unilib conversion.

Conversion Between Character SetsCode conversion is supported between character sets for the samelanguage or group of languages only. For example, code conversion issupported between the character sets for the Western Europeanlanguages (8859-1, cp437, cp850, mac, and roman8). Similarly, codeconversion is supported between the character sets for the Japaneselanguage (eucjis, sjis, and deckanji). However, code conversion is notsupported between the Western European language character sets andthe Japanese character sets. For more information about supportedconversions, see the System Administration Guide.

Changing the Language, Character Set, or Sort OrderTo change the language, character set, or sort order for an existingAdaptive Server or Backup Server:

1. Start the sqlloc utility:

$SYBASE/bin/sqlloc

96

Changing the Language, Character Set, or Sort Order

sqlloc displays a list of servers, both active and inactive, that exist onyour machine.

2. From the list, select the server for which you want to change thelanguage, character set, or sort order.

If you select an inactive server, sqlloc will start it for you.

3. Use the sqlloc online help to guide you through the various screens tochange the language, character set, or sort order of Adaptive Serveror Backup Server.

4. Exit sqlloc when you are finished.

97


98

Index

A

Adaptive Servernaming in interfaces file 41support for international systems 73

address option, interfaces file 42, 44Address, server 34ANSI character set 78api option, interfaces file 41, 44Arabic character set 77ASCII character set 77

B

Bourne shell 13, 17

C

C shell 13, 17Canadian French character set 78Changing

character set 96server language 96sort order 96

Character sets 74ANSI 78Arabic 77ASCII 77Canadian French 78changing 96Chinese 77conversion of 95Cyrillic 77deckanji 96default for platforms 74eucjis 93, 96

European 77Greek 78Hankaku Katakana 93Hebrew 78in heterogeneous environments 96Japanese 79, 93Korean 79Macintosh 78multibyte 93Portuguese 78Roman-8 78selecting default 75sjis 93, 96Thai 79Turkish 79

Characters, comparing 87charsets directory 90, 92Chinese character set 77Client interfaces files

differences between client andserver versions 35

heterogeneous 37homogeneous 37

Clientscommunicating with Adaptive

Server 25, 95default character set 75DSQUERY and 49file servers 49interfaces files for 52

Collationfinding information about 85rules, comparing characters using 87

Commandsdscp utility 70

compare function 87and sortkey 88rules for using 88values returned by 87

Comparing characters 87Conventions used in this book 12Conversions, character set 95

99

Index

Creatinginterfaces file 46

.cshrc file 13, 17Cyrillic character set 77

D

deckanji character set 93, 96Default

character sets, selecting 75language 89

default character sets 74Default languages 74Default location of interfaces files 35delay_interval option, interfaces file 41device option, interfaces file 42, 44Digital UNIX, default character set for 75Directories

charsets 90for character sets 92locales 89, 92

DISPLAY environment variabledsedit utility 55setting 55

Displaying current file descriptors 20Documentation, translated 73dscp utility

adding server entries 65closing a session 64commands 70copying server entries 67creating master interfaces files with 46deleting server entries 69described 61exiting 70help 62help on 71listing server entries 68modifying server entries 66opening a session 63quick reference for 70server attributes 64

starting 62switching between sessions 63viewing contents of server entries 69

dsedit utilitycommand to start 56creating master interfaces files with 46described 55Directory Service Session screen 56DISPLAY and 55permissions required for 55running from remote machine 55Select a Directory Service screen 56starting 55

DSLISTEN and multiple networkhandlers 48

DSLISTEN environment variable 18described 18, 36

DSQUERY 49DSQUERY and client connections 49DSQUERY environment variable 18

described 18, 36using different values for multiple

networks 50

E

Editinginterfaces files 56

Environment variablesDSLISTEN 18, 36DSQUERY 18, 36PATH 18

Errorsdbcc messages 31

/etc/services file 43ether placeholder, interfaces file 42eucjis character set 93, 96European character sets 77Exit dscp utility 70Extended UNIX character set 93

100

Index

F

File descriptors 19File servers 49Files

.cshrc 13, 17for localization 89locales.dat 90.login 17.profile 13, 17

Format, of interfaces file entries 44French (Canadian) character set 78French language modules 92

G

German language modules 92gettablesize command 20Greek character sets 78

H

Hankaku Katakana, conversion of 93Hard limit, for file descriptors 21, 24Hebrew character set 78Help

on dscp utility 62, 71support contract 14

Heterogeneous environments 73and interfaces files 37character sets in 96

High-availability products, configuring15

Homogeneous environmentsand interfaces files 37

Host namedetermining 42

host option, interfaces file 42HP-UX, default character set for 75

I

I/O monitoring 29IBM RS/6000, default character set for 75Information

sorting 85Interfaces files

and heterogeneous environments 37and homogeneous environments 37automatic creation of 35configuring for query port backup 52contents of 35creating master copy with text

editor 47creating master with dscp 46creating master with dsedit 46creating, for beginners 46defined 34differences between client and

server versions 35editing with dsedit 56example of 45format of 39formatting 43location of 35loghost placeholder 47multiple network listeners 48name of 35network name in 44opening a dscp session with 62opening for editing 56spaces in 40, 43tab characters in 40, 43unique elements in entries 47used by Adaptive Server 36used by clients 34, 36used by servers 34

International support 73iostat command

Digital UNIX 28IBM RS/6000 29, 30NCR 30

101

Index

J

Japanesecharacter sets 93language modules 92

Japanese character sets 79

K

Kanji 93KEEPALIVE option, TCP/IP 25Korean character set 79Korn shell 13

L

Languagechanging 96default 89

Language modules 92Languages, default 74Limits, for file descriptors 20, 23Listener service 35locales directory 89, 92locales.dat file 90

client applications 91predefined entries in 91

Localization files 89, 92Loghost, in interfaces files 47.login file 17

M

machine option, interfaces file 42Macintosh character set 78Master interfaces file 46maxfiles 20mbuf pools, tuning 29Message language

default 93selecting 93

Messages

default language for 74Messages indicating hardware errors 27Monitoring

I/O 29network status 29operating system resources 28virtual memory usage 29

Multibyte character set 93Multiple installations

affecting interfaces files 35creating one interfaces file for 46

Multiple networksand interfaces files 36configuring interfaces files for 47used as a backup in case of network

failure 52

N

NCR MP-RAS, default character set for75

netstat commandDigital UNIX 28HP-UX 29IBM RS/6000 29, 30NCR 30

network option, interfaces file 42Network protocols

types available for Digital UNIX 41Networks

backup connections and 52DSQUERY and 49failure of 53in interfaces files 34monitoring status 29multiple 36

no -a command, IBM RS/6000 29Novell Protocol Suite Version 3.0.1 43

O

open_max parameter 19

102

Index

Operating systemmonitoring resource usage 28monitoring resources 28

OrderingSee Sorting

P

PATH environment variable 18described 18

Permissions 17, 19Platforms supported 9Platforms, default character sets for 74Port numbers, interfaces file and 48port option, interfaces file 43port/object number option, interfaces

file 43Portuguese character set 78Predefined locale entries 91.profile file 13, 17Protocol

Novell Protocol Suite Version 3.0.1 43SPX/IPX 43

protocol option, interfaces file 41ps command

Digital UNIX 28HP-UX 29IBM RS/6000 29, 30NCR 30

Q

Queriesordering results of 85sorting results of 85

Query port backup configuration 52for clients 52

Query service 35Quick Reference, dscp utility 70Quitting

See Exiting

R

Remote machinesusing dsedit utility on 55

Renaming server entries 67Results of queries

sorting 85retry_attempts option, interfaces file 41Roman—8 character set 78

S

Sample interfaces file 45Scripts

C shell 31maintenance 31sample maintenance 31

Select a Directory Service screen 56select statements

sorting results of 85Selecting message language 93Server entries

renaming 67Server interfaces files

differences between client andserver versions 35

servername option, interfaces file 41Servers

communicating with clients 95Service types

listener 35Query 35

service_type option, interfaces file 41Services 41Sessions

multiple 56setenv command 17Setting

DISPLAY 55SGI, default character set for 75Shells 13Shift-JIS character set 93

103

Index

sjis (Shift-JIS) character set 93sjis character set 93, 96Socket number 44Soft limit, for file descriptors 21, 24Sort orders

alternative 84available for your platform 82binary 83case insensitive 83case preference for collating 83case sensitive 83changing 96choosing 81default 84default definition files 74dictionary 83for sqlloc utility 82Latin American 84location of 82lowercase before uppercase 84Scandinavian 84Spanish 84specifying at installation 82uppercase before lowercase 83

Sortinginformation 85results of queries 85

sortkey function 85rules for using 86

Spaces, in interfaces files 40, 43SPX network protocol 43sqlloc utility

specifying sort order in 82Starting

dsedit utility 55stty settings 19Style conventions 12Sun Solaris, default character set for 75

sundiag system diagnostic tool 28Supported platforms 9Sybase

globalization support 74SYBASE environment variable

as default server name 47Sybase interfaces file 56Syntax conventions 12, 13sysconf command 20System messages, translated 73

T

Tab characters, in interfaces files 40, 43TCP/IP network protocol 25Thai character set 79time command

Digital UNIX 29HP-UX 29IBM RS/6000 29, 31

Timeout period, for client connections 25timex command, NCR 30TLI (Transport Layer Interface) protocol

41, 44Trace flag 2402 93Turkish character set 79

U

UnixWare, default character set for 75User connections 19

V

Values returned by compare 87vmstat command

Digital UNIX 28HP-UX 29IBM RS/6000 29, 30

104