Your SlideShare is downloading. ×
DirectCONNECT™ for DB2/MVS Installation Guide for IBM RISC ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

DirectCONNECT™ for DB2/MVS Installation Guide for IBM RISC ...

451

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
451
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. DirectCONNECT™ for DB2/MVS Installation Guide for IBM RISC System/6000 AIX DirectCONNECT for DB2/MVS Release 10.5 Document ID: 34203-01-1050-01 Last Revised: November 19, 1996
  • 2. Document ID: 34203-01-1050 This publication pertains to DirectCONNECT for DB2/MVS Release 10.5 of the Sybase database management software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. Document Orders 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 fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. Copyright © 1989–1996 by Sybase, Inc. All rights reserved. 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 Trademarks Sybase, the Sybase logo, APT-FORMS, Data Workbench, DBA Companion, Deft, GainExposure, Gain Momentum, PowerBuilder, Powersoft, Replication Server, S- Designor, SQL Advantage, SQL Debug, SQL SMART, SQL Solutions, SQR, Transact-SQL, and VQL are registered trademarks of Sybase, Inc. Adaptable Windowing Environment, ADA Workbench, AnswerBase, Application Manager, AppModeler, APT-Build, APT-Edit, APT-Execute, APT-Library, APT-Translator, APT Workbench, Backup Server, BayCam, Bit-Wise, Client-Library, Client/Server Architecture for the Online Enterprise, Client/Server for the Real World, Client Services, Column Design, Connection Manager, DataArchitect, Database Analyzer, DataExpress, Data Pipeline, Datawindow, DBA Companion Application Manager, DBA Companion Resource Manager, DB-Library, Deft Analyst, Deft Designer, Deft Educational, Deft Professional, Deft Trial, Designor, Developers Workbench, DirectCONNECT, Easy SQR, Embedded SQL, EMS, Enterprise Builder, Enterprise Client/Server, Enterprise CONNECT, Enterprise Manager, Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, EWA, Gateway Manager, InfoMaker, InformationCONNECT, Intermedia Server, InternetBuilder, MainframeCONNECT, Maintenance Express, MAP, MDI, MDI Access Server, MDI Database Gateway, media.play, media.splash, MetaWorks, MethodSet, Movedb, Navigation Server Manager, Net-Gateway, Net-Library, New Media Studio, ObjectCONNECT, ObjectCycle, OmniCONNECT, OmniSQL Access Module, OmniSQL Server, OmniSQL Toolkit, Open Client, Open ClientCONNECT, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerCONNECT, Open Solutions, Optima++, PB-Gen, PC APT-Execute, PC DB-
  • 3. Net, PC Net Library, PowerBuilt, PowerBuilt with PowerBuilder, PowerScript, PowerSocket, Powersoft Portfolio, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Replication Agent, Replication Driver, Replication Server Manager, Report-Execute, Report Workbench, Resource Manager, RW-DisplayLib, RW-Library, SAFE, SDF, Secure SQL Server, Secure SQL Toolset, SKILS, smart.partners, smart.parts, smart.script, SQL Anywhere, SQL Code Checker, SQL Edit, SQL Edit/TPU, SQL Server, SQL Server/CFT, SQL Server/DBM, SQL Server Manager, SQL Server Monitor, SQL Server SNMP SubAgent, SQL Station, SQL Toolset, SQR Developers Kit, SQR Execute, SQR Toolkit, SQR Workbench, StarDesignor, Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Gateways, Sybase Intermedia, Sybase Interplay, Sybase IQ, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual Server Architecture, Sybase User Workbench, SybaseWare, SyBooks, System 10, System 11, the System XI logo, Tabular Data Stream, The Architecture for Change, The Enterprise Client/Server Company, The Online Information Center, Turning Imagination Into Reality, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, web.sql, web.works, WebSights, WorkGroup SQL Server, XA-Library, and XA-Server are trademarks of Sybase, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Restricted Rights Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 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.
  • 4. Table of Contents About This Book Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii How to Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Style Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v How to Get Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Sybase ICD Technical Support Services . . . . . . . . . . . . . . . . . . . . . . . . . vi Contacting Sybase ICD Technical Support . . . . . . . . . . . . . . . . . . . . . . . vi InformationCONNECT Bulletin Board . . . . . . . . . . . . . . . . . . . . . . . . vii InformationCONNECT Fax-on-Demand . . . . . . . . . . . . . . . . . . . . . . . vii CompuServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Electronic Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Professional Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Questions About DirectCONNECT Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . viii 1. Introduction Introduction to Enterprise CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 DirectCONNECT for DB2/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 MainframeCONNECT for DB2/MVS-CICS. . . . . . . . . . . . . . . . . . . . . . . . 1-2 Open ServerCONNECT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Open ClientCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 DirectCONNECT Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Mainframe Client CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 How to Get Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 About the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 DirectCONNECT for DB2/MVS Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Criteria for Creating Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Directory Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 DirectCONNECT for DB2/MVS Hardware and Software Requirements . . . . . . . . . . . . 1-8 2. Preparing for Installation Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Preinstallation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Preliminary Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Title for Your Book’s Footers -v
  • 5. Record the Tape Device Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Designate the Sybase Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Verify Installation of Previous Sybase Products. . . . . . . . . . . . . . . . . . . . . 2-4 Designate DirectCONNECT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Designate DirectCONNECT Service(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Designate TCP/IP Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 3. Installing a DirectCONNECT Server Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Tape Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Configure the Sample Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Test Mainframe Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Set Up Service Name Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Set Up Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Client Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Configure your Client Connectivity Files using sqledit . . . . . . . . . . . . . . 3-8 Verify Client Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Set Up the DirectCONNECT ODBC Driver . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Install your application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 4. Setting Up the ODBC Driver Configuring the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Connecting to the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Using a Logon Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Using a Connection String. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Mapping Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 ODBC Conformance Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 5. Creating Database Tables SQL Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Creating PUBS Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Creating CSP Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Glossary
  • 6. DirectCONNECT for DB2/MVS Release 10.5 List of Tables Table 1: Syntax conventions...........................................................................................................v Table 1-1: AIX Open Server directory...........................................................................................1-6 Table 1-2: Common econnect subdirectories ...............................................................................1-7 Table 1-3: Common server subdirectories....................................................................................1-7 Table 1-4: System requirements .....................................................................................................1-8 Table 4-1: Required data source configuration properties.........................................................4-2 Table 4-2: Optional data source configuration properties .........................................................4-2 Table 4-3: Logon dialog box information .....................................................................................4-6 Table 4-4: Connection string long and short names ...................................................................4-7 Table 4-5: DirectCONNECT for DB2/MVS and ODBC data types..........................................4-7 Table 5-1: CSP tables .......................................................................................................................5-3 DirectCONNECT for DB2/MVS Installation Guide for Windows NT i
  • 7. DirectCONNECT for DB2/MVS Release 10.5 ii List of Tables
  • 8. About This Book This guide describes how to install DirectCONNECT™ for DB2/MVS on IBM RISC System/6000 AIX. Audience This guide is for System Administrators or other qualified persons familiar with their system environment, resources, and devices. How to Use This Book This guide provides the following information: • Chapter 1, “Introduction,” describes the installed directory structure and lists DirectCONNECT for DB2/MVS hardware and software requirements. • Chapter 2, “Preparing for Installation,” lists the major tasks and related documentation in preparing for installation of your DirectCONNECT for DB2/MVS and MainframeCONNECT products. • Chapter 3, “Installing a DirectCONNECT Server,” provides step- by-step installation procedures, plus suggestions for post-installation configuration and setup. • Chapter 4, “Setting Up the ODBC Driver,” provides instructions for setting up the DirectCONNECT ODBC driver for using DirectCONNECT for DB2/MVS. • Chapter 5, “Creating Database Tables,” explains how to run SQL scripts to set up database tables for using DirectCONNECT for DB2/MVS. • The glossary provides definitions of technical terms used in this guide. Related Documents To set up DirectCONNECT for DB2/MVS connectivity, refer to the DirectCONNECT for DB2/MVS Connectivity Guide for IBM RISC/6000 AIX. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX iii
  • 9. Conventions DirectCONNECT for DB2/MVS Release 10.5 To configure and administer DirectCONNECT for DB2/MVS products, use the following documents: • DirectCONNECT Server Administration Guide • DirectCONNECT for DB2/MVS Access Service Guide • DirectCONNECT Transaction Router Service Guide • DirectCONNECT Error Message Guide To install and administer MainframeCONNECT products, use the following documents: • MainframeCONNECT for DB2/MVS-CICS Installation and Administration Guide • Open Client CONNECT Client Services Application Programmer’s Guide • Open Server CONNECT Remote Stored Procedure Programmer’s Guide For additional references, use the following documents: • Open Client Client-Library Reference Manual • Open Client DB-Library Reference Manual • Open Server Server-Library Reference Manual • Open Client/Server Installation Guides (by platform) • Open Client/Server Supplements (by platform) • OmniSQL Server System Administration Guide • OmniSQL Server Server Classes and Utilities Reference Manual • OmniCONNECT User’s Guide Conventions The following sections describe style and syntax conventions used in this guide. Style Conventions The following style conventions are used in this guide: • The names of files and directories are shown as: econnect/ServerName/CFG iv About This Book
  • 10. DirectCONNECT for DB2/MVS Release 10.5 Conventions • The names of programs, utilities, procedures, and commands are shown as: snrfck • The names of properties are shown as: Allocate • The names of options are shown as: connect • In a sample command line display, commands you should enter are shown as: this font • In a sample command line display, variables (words which you should replace with the appropriate value for your system) are shown as: this font Syntax Conventions Syntax statements that display options for a command look like this: COMMAND [object_name, [ {TRUE | FALSE} ] ] The following table explains the syntax conventions used in this guide. Table 1: Syntax conventions Symbol Convention () Include parentheses as part of the command. {} Braces indicate that you must choose at least one of the enclosed options. Do not type the braces when you type the option. [] Brackets indicate that you can choose one or more of the enclosed options, or none. Do not type the brackets when you type the options. | The vertical bar indicates that you can select only one of the options shown. Do not type the bar in your command. , The comma indicates that you can choose one or more of the options shown. Separate each choice by using a comma as part of the command. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX v
  • 11. How to Get Help DirectCONNECT for DB2/MVS Release 10.5 How to Get Help If you need help, the following Sybase resources are available: • Technical support • Professional services Technical Support Sybase Technical Support provides assistance to customers who have paid the applicable support fees, as defined in the Software License Agreement. You can reach Technical Support for all Sybase products by calling (800) 8SYBASE. Sybase ICD Technical Support Services Sybase InformationCONNECT Division (ICD) Technical Support provides various forms of assistance to our customers, including the following services: • Assist in identifying problems. • Offer a fix, if available. • Provide all levels of technical support on our products to customers, as needed. • Document software problems and enhancement suggestions in our customer support database. • Communicate status information on open problems. • Share information on new products or releases of existing products. In addition, Sybase ICD system engineers are available for technical assistance in various geographical territories. Contacting Sybase ICD Technical Support If you believe your problem is a DirectCONNECT problem, you may contact Sybase ICD Technical Support directly at (800) 423-8737. Hours are 5:00 AM to 6:30 PM, Monday through Friday, Mountain Standard or Daylight Savings Time (MST or MDT), except holidays. vi About This Book
  • 12. DirectCONNECT for DB2/MVS Release 10.5 How to Get Help Before you contact Sybase ICD Technical Support, complete these steps: 1. Thoroughly review the documentation, especially all troubleshooting sections. 2. Be prepared to generate a trace, if requested to do so by Technical Support, and fax it to (303) 413-4167 or upload it to our Bulletin Board. ® Note Outside the continental United States and Canada, obtain the correct telephone numbers from your sales representative and record them here for future reference:______________________________. InformationCONNECT Bulletin Board To use the Bulletin Board service (BBS): 1. Call (303) 413-4285. 2. Use parameters 8-1-N and a baud rate of 300-9600. InformationCONNECT Fax-on-Demand To use Fax-on-Demand: 1. Call (800) 423-8737. Outside the United States and Canada, call (303) 575-6132. 2. Select option 2 and follow the recorded instructions. CompuServe To access the Sybase ICD online information service: 1. Connect to CompuServe using the normal procedures for your site. 2. At any menu prompt, type: go icdtech DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX vii
  • 13. Questions About DirectCONNECT Documentation DirectCONNECT for DB2/MVS Release 10.5 Electronic Mail You can send electronic mail to this address: icdtech@sybase.com Professional Services Professional Services offers consulting and training programs to help you maximize the benefits of our products. For more information, call (303) 486-7700. ® Note Outside the continental United States and Canada, obtain the correct telephone numbers from your sales representative and record them here for future reference:______________________________. Questions About DirectCONNECT Documentation If you have questions, comments, or suggestions about documentation for this product, contact the Sybase ICD documentation group directly by electronic mail at: icd_doc@sybase.com Feel free to forward any information, comments, or questions about: • Missing, incorrect, or unclear information • Information you found particularly useful • Organization or style We will respond as promptly as possible by electronic mail. Your feedback helps us provide more accurate, detailed, and easy-to-use documentation. Please send comments about product features, functionality, or problems to your system engineer or Sybase ICD Technical Support. To order additional copies of DirectCONNECT documentation, see “Document Orders” on the disclaimer page following the title page. viii About This Book
  • 14. 1 Introduction 1. The Sybase DirectCONNECT Server installation program (sybinit) is an interactive installation program that you will use to install the DirectCONNECT Server. This chapter includes the following topics: • Introduction to Enterprise CONNECT 1-1 • About the Installation Program 1-4 • How to Get Started 1-4 • DirectCONNECT for DB2/MVS Directory Structure 1-5 • DirectCONNECT for DB2/MVS Hardware and Software Requirements 1-8 Introduction to Enterprise CONNECT Enterprise CONNECT products provide a common, enterprise-wide architecture that supports the development of distributed computing applications. Enterprise CONNECT products provide the following middleware services: • Distributed database access services • Transaction services • Mainframe integration • Data delivery • Object interfaces Following are brief descriptions of the Enterprise CONNECT components. DirectCONNECT for DB2/MVS DirectCONNECT for DB2/MVS is Open Server-based software that supports DB-Library, CT-Library, and Open Database Connectivity (ODBC) application programming interfaces (APIs). It serves as a fundamental building block for database middleware applications that provide a single standardized method for accessing non-Sybase data sources. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 1-1
  • 15. Introduction to Enterprise CONNECT DirectCONNECT for DB2/MVS Release 10.5 DirectCONNECT allows you to designate one or more servers, each identified by a unique server name. Each server can contain one or more services, with each service representing a unique named set of configuration properties. DirectCONNECT for DB2/MVS provides the following components for decision support and online transaction processing (OLTP) applications: • DirectCONNECT for DB2/MVS Access Service that provides access to DB2/MVS data • DirectCONNECT Transaction Router Service that provide access to remote transactions • DirectCONNECT Administrative Service that provide server- side systems management MainframeCONNECT for DB2/MVS-CICS MainframeCONNECT for DB2/MVS-CICS is mainframe software that works with DirectCONNECT for DB2/MVS to provide access to DB2 data, and performs the following functions: • Support full read-write, dynamic SQL access to DB2 data • Allow applications to use DB2 cursors for flexible and efficient results set processing • Permits the use of long-running transactions against DB2 • Provides access to mainframe transactions that use static SQL for DB2 access or access to virtually any MVS data source • Allows applications to use dynamic events to map dynamic SQL to a static DB2 plan Clients access MainframeCONNECT for DB2/MVS-CICS directly through a DirectCONNECT for DB2/MVS Access Service or a DirectCONNECT Transaction Router Service, or indirectly through OmniCONNECT or a Sybase SQL Server remote procedure call (RPC). Open ServerCONNECT Open ServerCONNECT is a programming environment that allows you to create mainframe transactions that are accessible to clients via DirectCONNECT. Open ServerCONNECT provides the following basic interfaces: 1-2 Introduction
  • 16. DirectCONNECT for DB2/MVS Release 10.5 Introduction to Enterprise CONNECT • Open Server, (the traditional Open Server environment) • Remote stored procedure (RSP), (the MDI-heritage programming environment) These transactions provide access to virtually any MVS data source and are used to perform a variety of functions, including: • Initiating mainframe batch jobs • Providing source data for data transfer operations • Providing data mapped to a table within OmniCONNECT, thus allowing results to be accessed or joined with data from other targets Clients access Open ServerCONNECT transactions directly through DirectCONNECT or indirectly by OmniCONNECT or a Sybase SQL Server RPC Open ClientCONNECT Open ClientCONNECT allows customers to create mainframe applications that access LAN data from a Sybase SQL Server or any other supported data source. Open ClientCONNECT uses the following APIs: • Open Client (the traditional Open Client environment) • Client Services Application (CSA), (the MDI-heritage programming environment) Open ClientCONNECT allows customers to treat the mainframe as just another node on a network. Open Client applications are used to provide referential integrity between mainframe and LAN data, initiating bulk data movements as part of nightly batch operations. DirectCONNECT Configuration Tool DirectCONNECT Configuration Tool is an Open Client-based graphical user interface (GUI) systems management product for administering data. It provides the following capabilities: • Remote start, stop, and configuration • Dynamic reconfiguration of services • Drag-and-drop service creation and copying DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 1-3
  • 17. How to Get Started DirectCONNECT for DB2/MVS Release 10.5 • Remote log filtering and down-loading • Heartbeat services Mainframe Client CONNECT Mainframe Client CONNECT is a LAN-based program that allows Open Client CONNECT mainframe applications to connect to LAN servers. It performs data and protocol translation between APPC LU6.2 or TCP/IP and the LAN network protocols. Mainframe Client CONNECT replaces the following former products: • Mainframe Client Gateway • Database Gateway Access Server How to Get Started If you are installing more than one product, you must run the applicable installation executable program that accompanies each product. To ensure the DirectCONNECT installation proceeds smoothly: • Read the Release Bulletin for the installation of DirectCONNECT for DB2/MVS for IBM RISC System/60000 AIX. • Confirm that your system meets the requirements for Open Client/Server listed in “DirectCONNECT for DB2/MVS Hardware and Software Requirements” on page 1-8. • Read Chapter 2, “Preparing for Installation”, to become familiar with the information that will be required prior to and during the actual installation. About the Installation Program The installation program, sybinit, performs the following functions: • Creates a directory structure, including an Open Server directory if one does not already exist. • Copies DirectCONNECT for DB2/MVS programs, utilities, and support files from distribution media to the appropriate directories. 1-4 Introduction
  • 18. DirectCONNECT for DB2/MVS Release 10.5 DirectCONNECT for DB2/MVS Directory Structure • Confirms that necessary system resources are present to install and support DirectCONNECT for DB2/MVS. • Confirms that installed components are compatible with existing DirectCONNECT for DB2/MVS and Open Server components. DirectCONNECT for DB2/MVS Directory Structure sybinit copies all DirectCONNECT for DB2/MVS components into the directory structure identified by the $SYBASE environment variable, as outlined in the following figure. $SYBASE lib work econnect bin bin codesets charsets lib ServerName install svclib locales cfg scripts locales log ServerName svclib cfg locales log ServerName... Figure 1-1: DirectCONNECT for DB2/MVS directory structure The shaded blocks represent Open Server subdirectories. Only the Open Server components necessary to support DirectCONNECT for DB2/MVS products are installed into this directory. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 1-5
  • 19. DirectCONNECT for DB2/MVS Directory Structure DirectCONNECT for DB2/MVS Release 10.5 These subdirectories are described in the following table. The econnect subdirectory contains directories for each DirectCONNECT Server that you install as well as common directories for use by all DirectCONNECT servers. Table 1-1: AIX Open Server directory Subdirectory Contents bin Open Server utility programs charsets Character sets and sort order localization files lib Open Server libraries install Install support programs locales Open Server localized message and text files scripts Scripts for the isql utility for creating database tables Criteria for Creating Directories During installation, sybinit checks the $SYBASE environment variable for an existing Sybase directory that was created for another Sybase product. For example, this could be a directory created for SQL Server or for OmniCONNECT. The following rules apply: • If sybinit locates a Sybase directory, it installs DirectCONNECT for DB2/MVS subdirectories under this directory. ® Note We do not recommend mixing multiple Sybase products in the same directory structure. • If sybinit cannot locate such a directory, it creates one. The program creates the directory structure necessary to install the product. • If sybinit detects a conflict between new and existing files, a warning message appears. At any point, you can cancel the installation. 1-6 Introduction
  • 20. DirectCONNECT for DB2/MVS Release 10.5 DirectCONNECT for DB2/MVS Directory Structure Directory Names When you start the DirectCONNECT Server, it uses the server name you supply to locate a particular subdirectory. Within the directory tree, each server name must be unique and identifies a server instance. Thus, each server has its own context, including separate message files, service libraries, and configuration files. A ServerName subdirectory is identified as follows: $SYBASE/econnect/ServerName where • econnect identifies the base of the Enterprise CONNECT family of products. • ServerName identifies a DirectCONNECT for DB2/MVS subdirectory tree. Only one econnect subdirectory can exist in a $SYBASE directory tree, but multiple DirectCONNECT Servers can exist within the econnect subdirectory. Within $SYBASE, all dependent components must have compatible Sybase revision levels. The common directories installed under econnect are outlined in the following table. Table 1-2: Common econnect subdirectories Subdirectory Contents lib Shared libraries work Work directory used internally by product bin Server executables codesets Files for code page conversions The subdirectories installed under the ServerName subdirectory are outlined in the following table. Table 1-3: Common server subdirectories Subdirectory Contents svclib Service libraries cfg Server and service library configuration files, plus the default service name redirection file DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 1-7
  • 21. DirectCONNECT for DB2/MVS Hardware and Software Requirements DirectCONNECT for DB2/MVS Release 10.5 Table 1-3: Common server subdirectories (continued) Subdirectory Contents locales U.S. English locales files used by server and service libraries log Log and trace files DirectCONNECT for DB2/MVS Hardware and Software Requirements DirectCONNECT for DB2/MVS is compatible with: • Open Server release 10.0.4 • SQL Server release 10.0.2 and higher • DB2 version 2 release 3 and higher • CICS 3.3 and higher, and PTF UN90057 for full functionality with the password expiration manager (PEM) feature To use DirectCONNECT for DB2/MVS with AIX, you must have, at a minimum, a RISC/6000 workstation with the system configuration shown in the following table. Table 1-4: System requirements Item Requirement CPU An IBM RISC System/6000. RAM A minimum of 32 MB of RAM to run AIX and any DirectCONNECT for DB2/MVS products. Storage A minimum of 24 MB, plus: • Space for the largest log file you expect to maintain • Space for the largest trace file you expect to accommodate • At least 500,000 bytes for each locale you plan to support Software The production release of AIX 4.1.x. SNA Server/6000 Version 3, Release 1.0 or newer. Additional A 1/4 inch or 8mm cartridge tape drive. hardware Network An interface card compatible with AIX. We support recommend a 32-bit card for best performance. 1-8 Introduction
  • 22. 2 Preparing for Installation 2. This chapter describes the tasks that you will perform in preparing for the installation of DirectCONNECT for DB2/MVS. The tasks are described in the following sections: • Before You Begin 2-1 • Preinstallation Checklist 2-2 • Preliminary Tasks 2-3 Before You Begin Before you begin the installation, complete the following tasks: • Read the Release Bulletin for the “Installation of DirectCONNECT for DB2/MVS for IBM RISC/6000 AIX”. The Release Bulletin provides product information that may not be included in the manuals, as well as information about known issues or problems. • If you are installing into an existing Sybase directory we recommend you make a backup copy of the current Sybase software. ® Note There is NO defined method for deinstalling this software. The only method for restoring your software to its previous version is through use of your backup copy. • Be sure to have the ability to log in to user sybase. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 2-1
  • 23. Preinstallation Checklist DIrectCONNECT for DB2/MVS Release 10.5 Preinstallation Checklist The following checklist ensures that the respective product components are installed prior to installation of DirectCONNECT for DB2/MVS: 1. Validate the AIX server is connected to the LAN and that network protocols are configured correctly. See your LAN Administrator documentation for instructions. 2. Define the LU6.2 or TCP/IP AIX server connection to the mainframe. See the DirectCONNECT for DB2/MVS Connectivity Guide for IBM RISC System/6000 AIX. 3. If you are using APPC, install and configure the SNA Server/6000. See the DirectCONNECT for DB2/MVS Connectivity Guide for IBM RISC System/6000 AIX. 4. Install MainframeCONNECT for DB2/MVS-CICS. Verify that AMD2 is running. Validate that MainframeCONNECT is connected to DB2. See the MainframeCONNECT for DB2/MVS-CICS Installation and Administration Guide. 5. Install and configure Open ServerCONNECT for CICS. See the MainframeCONNECT for DB2/MVS-CICS Installation and Administration Guide. 6. Install DirectCONNECT Configuration Tool. See the DirectCONNECT Configuration Tool Installation Guide for Microsoft Windows and Windows NT. 7. Verify your tape device is configured for a blocksize of 1024. If the blocksize is not 1024, reconfigure your tape device before loading the tape for your installation. 2-2 Preparing for Installation
  • 24. DIrectCONNECT for DB2/MVS Release 10.5 Preliminary Tasks Preliminary Tasks Determine and write your responses to the following, as you are prompted for this information during installation. Record the Tape Device Name Identify and record the tape device name for your operating system. 1. Determine the name of the tape device. 2. Record the full path and name of the tape device. Full path and name of the tape device __________________ Designate the Sybase Home Directory Determine the directory in which you want to install DirectCONNECT for DB2/MVS. If Sybase software was installed previously, Sybase recommends that you create a directory for this release, and not use the existing directory. If a directory does not exist, identify the name of a directory that you want to create. ® Note For DirectCONNECT, the directory names specified must NOT contain any upper case letters or any periods. 1. To create a new Sybase home directory: mkdir directoryname mkdir directoryname/install Record the name of the DirectCONNECT Directory name you have created. Directory Name ___________________________ 2. Set all the necessary environment variables: - $SYBASE indicates the path to the Sybase home directory - $LIBPATH is used by AIX to determine the shared library location DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 2-3
  • 25. Preliminary Tasks DIrectCONNECT for DB2/MVS Release 10.5 This ensures the variables are set correctly whenever you log in as a System Administrator. Use one of the following commands: • For Bourne shell: Add the following to the .profile file: export SYBASE=directoryname export LIBPATH=$SYBASE/lib:$SYBASE/econnect/lib Enter at the shell prompt: .profile • For C shell: Add the following to the .login or .cshrc file: setenv SYBASE directoryname setenv LIBPATH $SYBASE/lib:$SYBASE/econnect/lib At the shell prompt, enter either: source .login or source .cshrc Verify Installation of Previous Sybase Products When installing DirectCONNECT for DB2/MVS into an existing directory structure, be aware of any previously installed Sybase software and its version. Verify the following: ® Note We do not recommend mixing multiple Sybase products in the same directory structure. • Open Client/Open Server Version DirectCONNECT requires that you have the Open Client/ Server version as specified in the “DirectCONNECT for DB2/MVS Hardware and Software Requirements” in Chapter 1, “Introduction”. If you do not have this version determine whether you want to upgrade to the new version, included with DirectCONNECT for DB2/MVS—as it can affect other Sybase software. 2-4 Preparing for Installation
  • 26. DIrectCONNECT for DB2/MVS Release 10.5 Preliminary Tasks • DirectCONNECT Version If a previous version of DirectCONNECT is installed, determine whether you want to replace it. If you do not, you must install the new version under a different Sybase root directory. • DirectCONNECT Access Service Version If a previous version of DirectCONNECT Access Service for DB2/MVS is installed, determine whether you want to replace it. If you do not, you must install the new version into a different Sybase root directory or possibly under a new server Designate DirectCONNECT Server Record the name of the DirectCONNECT Server you want to create or update subject to the following restrictions: - The name must contain eight or fewer characters, but must contain at least one character. - The name must begin with a lowercase letter. - All subsequent characters must be letters, numerics (0-9), or the underscore (“_”) character. ® Note For DirectCONNECT, the server names specified must NOT contain any upper case letters or any periods. DirectCONNECT Server name ______________________ Designate DirectCONNECT Service(s) Record the name of the DirectCONNECT Service(s) you want to create or update subject to the following restrictions: - It should be unique within the DirectCONNECT Server. - It must contain 11 or fewer characters. - It must begin with a lowercase letter. All subsequent characters must be letters, numerics (0-9), or the underscore (“_”) character. DirectCONNECT Service name(s) ______________________ DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 2-5
  • 27. Preliminary Tasks DIrectCONNECT for DB2/MVS Release 10.5 Designate TCP/IP Port Number Record the TCP/IP port number that DirectConnect for DB2/MVS will use, or use the default port number provided during installation. TCP/IP port number _______________ . 2-6 Preparing for Installation
  • 28. 3 Installing aDirectCONNECT Server3. This chapter explains the procedure to install a DirectCONNECT Server or DirectCONNECT for DB2/MVS components. This chapter includes the following topics: • Before You Begin 3-1 • Tape Installation Instructions 3-2 • What To Do Next 3-6 • Troubleshooting 3-9 Before You Begin Before you begin the installation perform the following tasks: • Verify that your system meets the minimum hardware and software requirements listed in Chapter 1, “Introduction.” • Review Chapter 2, “Preparing for Installation.” x WARNING! If you plan to install DirectCONNECT into an existing directory containing other Sybase products, do not proceed with the installation until you stop all other Sybase software. This will prevent you from overlaying files that may be in use by another Sybase product. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 3-1
  • 29. Tape Installation Instructions DirectCONNECT for DB2/MVS Release 10.5 Tape Installation Instructions Perform the following steps to load your software from tape. Use the information you recorded in Chapter 2, “Preparing for Installation.” ® Note You may enter Ctrl C to stop the installation process at any time during the installation. 1. Log in as the user sybase. 2. Insert the tape into your tape drive. 3. Be sure to set the Sybase environment as previously described in “Designate the Sybase Home Directory” in Chapter 2, “Preparing for Installation”. Move to the Sybase root directory: cd $SYBASE/install 4. Load your first file from tape using the tape device identified in “Record the Tape Device Name” in Chapter 2, “Preparing for Installation”: tar -xvf tape device ® Note Verify your tape device is configured for a blocksize of 1024. Failure to set the blocksize will result in I/O errors reading device. 5. Start the install script, by entering: sybinit Following the “Welcome to DirectCONNECT Server setup” greeting, a message appears to remind you to create a backup of the existing Sybase software. ® Note Sybase recommends a backup if you are installing DirectCONNECT for DB2/MVS into an existing directory. 6. Choose y to continue or n to stop the installation, if you want to create a backup. 7. The system verifies that this is the correct operating system for this installation kit and that you have logged in as user sybase. 3-2 Installing a DirectCONNECT Server
  • 30. DirectCONNECT for DB2/MVS Release 10.5 Tape Installation Instructions A warning message advises you to stop running all versions of Sybase software if you have not already done so before continuing with the installation. 8. Choose y to continue or n to stop the installation. 9. Enter the name of your non-rewinding tape device as identified in “Record the Tape Device Name” in Chapter 2, “Preparing for Installation”, or press ENTER to choose the default. The program verifies the correct device name and will repeat the request until a correct device name is entered. (This may take a few moments to complete.) 10. A list of components being installed appears. 11. If the list contains the products you want to install, enter y to continue or enter n to stop the installation. 12. Enter the full name of the directory (no symbolic names) in which you want to install DirectCONNECT for DB2/MVS as recorded in “Designate the Sybase Home Directory” in Chapter 2, “Preparing for Installation”, or select the default by pressing ENTER. If a $SYBASE environment variable is already defined, sybinit uses it as the default directory. The system verifies: - A directory exists or was created, and the Sybase user has read and write permission. If not, the process terminates. - A previous version of DirectCONNECT exists and the version is different than the one being installed. If one exists, a message prompts you whether to replace the current version with the newer version. 13. Select y when requested to Install Management Components sybinit installs minimal Open Server files needed to support execution of Open Client/Open Server applications. You must select Management Components under the following conditions: - if not previously installed, for the DirectCONNECT Server to be able to run - to overwrite a previously installed DirectCONNECT version and the Open Client/Open Server version. 14. From the following, select each of the DirectCONNECT Access service components that you want to install. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 3-3
  • 31. Tape Installation Instructions DirectCONNECT for DB2/MVS Release 10.5 x WARNING! To avoid having to reinstall DirectCONNECT a second time, install all the Services that you are currently using including those services you will need in the future. - DB2 Access Service —For information about DirectCONNECT Access Service libraries and services, and configuration, see the DirectCONNECT for DB2/MVS Access Service Guide. - Transaction Router Service for LU6.2—For information about DirectCONNECT Transaction Router Service Libraries, and configuration, see the DirectCONNECT Transaction Router Service Guide. - Transaction Router Service for TCP/IP—For information about DirectCONNECT Transaction Router Service Libraries, and configuration, see the DirectCONNECT Transaction Router Service Guide. - Mainframe Client Connect—For information about MainframeCONNECT, see the MainframeCONNECT for DB2/MVS-CICS Installation and Administrative Guide. 15. If you are installing with an existing DirectCONNECT product, be sure to specify a server name that is unique to avoid conflict with any existing ones. Enter the full name of the DirectCONNECT Server, subject to the restrictions defined in “Designate DirectCONNECT Server” in Chapter 2, “Preparing for Installation”. The name you select is: - The name of the subdirectory tree for service libraries, configuration files, localized message files, and log files - The Master section name in the $SYBASE/interfaces file Verification of the server name occurs under the following conditions: - If the sybinit install program does not find the server name it creates a new server name. - If the install program finds the server name, it prompts you to update the existing server. 16. Select y, if you want to update the existing server Select n, if you do not want the existing server updated. This terminates the process. 3-4 Installing a DirectCONNECT Server
  • 32. DirectCONNECT for DB2/MVS Release 10.5 Tape Installation Instructions x WARNING! If a server is not designated the installation terminates. (A delay will occur while the installation proceeds.) 17. Choose y to configure a sample service within the db2.cfg file, or n to bypass configuring the sample service. 18. If you choose to configure a sample service, enter a service name within the guidelines defined in “Designate DirectCONNECT Service(s)” in Chapter 2, “Preparing for Installation” The name you select is used for the following: - The service section name in the access library configuration file (db2.cfg) - The section name in the $SYBASE/interfaces file 19. Respond to the prompt for a TCP/IP port number by selecting a valid port number recorded in “Designate TCP/IP Port Number” in Chapter 2, “Preparing for Installation”, or use the default port number (3180). (Installing DirectCONNECT is now completed.) 20. Choose whether to view the installation readme file by doing one of the following: - Enter y to see the readme file. - Enter n to exit. The file is located in the SYBASE/install directory. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 3-5
  • 33. What To Do Next DirectCONNECT for DB2/MVS Release 10.5 What To Do Next After you install DirectCONNECT for DB2/MVS, you must perform a number of steps to connect it with DB2, as well as with your other Sybase products. This section provides guidelines and references for performing these tasks. The tasks are divided into two groups: those completed in the AIX environment, referred to as “Server Tasks”, and those completed in your Windows environment, referred to as “Client Tasks”. Server Tasks The following procedures ensure that the AIX environment is properly connected to DB2 and to other Sybase products. Configure the Sample Service When sybinit creates a sample service, it adds the service to the access service library configuration file as an empty section and to the interfaces file as a Query section. To enable the service, you must perform the following steps: • Configure the properties in the configuration file (db2.cfg). The db2.cfg file is located in the $SYBASE/econnect/ServerName/cfg directory. You must assign valid values to all required configuration properties to provide client connection. For instructions on configuring specific access service properties, including instructions for adding a new service, see the DirectCONNECT for DB2/MVS Access Service Guide. • Set up the assigned service name in the service name redirection file (optional). ® Note If you overwrite a server that contains a sample service, but you do not overwrite the service; or if you overwrite the server and change the name of the service, sybinit does not remove the obsolete sample service sections from the interfaces file. You must make the changes manually. 3-6 Installing a DirectCONNECT Server
  • 34. DirectCONNECT for DB2/MVS Release 10.5 Client Tasks Test Mainframe Connectivity 1. Testing connectivity from the MVS mainframe to the AIX server depends on: - if you are using LU6.2, use the utility snaping. - If you are using TCP/IP, use the utility cicsping. Use of these utilities is defined in the “DirectCONNECT for DB2/MVS Connectivity Guide for IBM RISC System/6000 AIX” document. 2. Test connectivity between MainframeConnect and DB2 (login to DB2) using isql by entering: isql -Sservice_name -U{$SYBASE userid & password] Set Up Service Name Redirection This is an optional step. If you intend to use service name redirection, you must modify the default file, snrf.tbl or create a new redirection file. The snrf.tbl file is located in the $SYBASE/econnect/ServerName/cfg directory. For instructions on setting up and using the service name redirection feature, see the DirectCONNECT Server Administration Guide. Set Up Database Tables You can use the isql scripts in the $SYBASE/scripts subdirectory to set up PUBS and CSP tables for DB2. For guidelines, see Chapter 5, “Creating Database Tables.” Client Tasks The following outlined procedures ensure that the Windows 3.1, Windows 95, and Windows NT client environment is properly connected to the LAN and to the DirectCONNECT server(s). To set up the client, perform the following steps: DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 3-7
  • 35. Client Tasks DirectCONNECT for DB2/MVS Release 10.5 Configure your Client Connectivity Files using sqledit sqledit is a Windows program that you can use to add, edit, or delete entries in the sql.ini and libtcl.cfg files. 1. Configure your client sql.ini file. The service name and port number must match the entry for the DirectCONNECT Server. If you use service name redirection, the port number must match the port number entered or the default port number, and the service name must map through the redirection file to the DirectCONNECT Server. For additional information, refer to the DirectCONNECT Server Administration Guide. 2. Configure the libtcl.cfg configuration file, that contains information for each installed Net-Library driver. Use sqledit to open the libtcl.cfg file, to view a list of the drivers installed on your machine. You can view a description of any driver by selecting it from the list. Client applications use the information in this file, along with information in the sql.ini file, to connect to a server using the correct Net-Library DLL. To exit sqledit: From the active window, choose Done or Close. From the File menu, choose Exit. Verify Client Connectivity 1. Validate that the client is connected to the LAN and the protocols are configured correctly. For information, see the appropriate client network documentation. 2. Verify the connectivity from the client to the DirectCONNECT server using sybping. sybping tests (pings) the Net-Library-to- server connection across your network software and reports information about successful connections or failed connection attempts. sybping is a network diagnostic utility that you can use to verify that: Your Net-Library software is installed correctly You can connect to DirectCONNECT or Open Server 3-8 Installing a DirectCONNECT Server
  • 36. DirectCONNECT for DB2/MVS Release 10.5 Troubleshooting When you open sybping, you can access any installed DirectCONNECT Server, as well as any DirectCONNECT for DB2/MVS service. To exit sybping, choose Exit from the utility main menu. Set Up the DirectCONNECT ODBC Driver ODBC clients must use the DirectCONNECT ODBC driver to connect with DirectCONNECT Access Services. For instructions on setting up the driver, refer to Chapter 4, “Setting Up the ODBC Driver.” Install your application See the appropriate client application installation documentation. Troubleshooting If your system does not work properly after you install DirectCONNECT for DB2/MVS products, and if you already performed the connection steps listed previously, try the following: • Confirm the version number of Open Server software. DirectCONNECT is compatible with Open Server Release and SQL Server Release identified in Chapter 1, “DirectCONNECT for DB2/MVS Hardware and Software Requirements”. • Check the log and trace files in the server $SYBASE/econnect/server/log subdirectory for more information. The following are examples of messages that could occur: - Could not initialize Default Codeset Table: /usr/$SYBASE id & pswd/econnect/codesets 850.csc Indicates that the pathname is not defined correctly. Check for the possibility of the directory names in the path containing an uppercase letter or a period(.) and correct the directory name. - Error : 16029 Severity : 20 State: 0 OS Error: -1 : Failed to start any network listeners OS Error Text : <srv-lib> Indicates the specified port number is in use. Change the port number to one that is not in use and try again. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 3-9
  • 37. Troubleshooting DirectCONNECT for DB2/MVS Release 10.5 Refer to the DirectCONNECT Error Message guide for errors that occur. Contact ICD Technical Support for any further assistance as identified in “About This Book”. • If the server fails before the log files initialize, error messages are written to the console. If this occurs, see the DirectCONNECT Server Administration Guide for explanations of these “pre-log” messages. 3-10 Installing a DirectCONNECT Server
  • 38. 4 Setting Up the ODBC Driver 4. The DirectCONNECT Open Database Connectivity (ODBC) driver allows applications to access DB2 databases using SQL. With ODBC, you can develop, compile, and ship an application without targeting a specific data source. ODBC clients must use this driver to connect with DirectCONNECT for DB2/MVS Access Services. The driver supports DirectCONNECT for DB2/MVS clients in Microsoft Windows 16- and 32-bit environments. You must install Sybase Open Client-Library and Net-Library to gain access to DirectCONNECT for DB2/MVS target database objects. This chapter covers the following topics: • Configuring the Data Source 4-1 • Connecting to the Data Source 4-6 • Mapping Data Types 4-7 • ODBC Conformance Level 4-8 Configuring the Data Source To configure a DirectCONNECT for DB2/MVS data source, perform the following steps: 1. Start the ODBC Administrator by selecting the ODBC icon from the Windows 3.1, Windows 95 or Windows NT control panel. 2. Do one of the following: - If you are configuring an existing data source, select the source name and choose OK. - If you are configuring a new data source, choose Add to view the list of installed drivers, then select DirectCONNECT and choose OK. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 4-1
  • 39. Configuring the Data Source DirectCONNECT for DB2/MVS Release 10.5 3. Specify values for the data source using the information in the following table. Table 4-1: Required data source configuration properties Property Description DataSourceName A string that identifies the Sybase System 11 or DirectCONNECT for DB2/MVS data source configuration in the ODBC.ini file. Examples include “Accounting” or “Sys10-Serv1.” Description An optional long description of a data source name. Examples include “My Accounting Database” or “System 11 on Server number 1.” ServerName The name of the server containing the System 11 or DirectCONNECT for DB2/MVS tables that you want to access. Refer to Designate DirectCONNECT Server 2-5 4. Specify values for any optional properties that you require. The properties are listed in the following table. Table 4-2: Optional data source configuration properties Property Description ServerList The list of servers that appears in the logon dialog box. Use commas to separate the server names. DatabaseName The name of the database to which you want to connect by default. If you do not specify a value, the default is the database defined for each user. DatabaseList The databases that appear in the logon dialog box. Use commas to separate the database names. DefaultLogonID The default logon ID used to connect to your System 11 database. This ID is case-sensitive. A logon ID is required only if security is enabled for the database to which you are connecting. Your ODBC application can override this value, or you can override this value in the logon dialog box or the connection string. InterfacesFile The pathname of the interfaces file. The default is the normal Sybase interfaces file (sql.ini). Initialization A string of commands that execute when the data source String connection initializes. Use semicolons to separate multiple commands. 4-2 Setting Up the ODBC Driver
  • 40. DirectCONNECT for DB2/MVS Release 10.5 Configuring the Data Source Table 4-2: Optional data source configuration properties (continued) Property Description ModifySQL An instruction to the driver to convert a single- or two- Statement part table name to a three-part format for create table SQL statements. Valid values are: • 0 instructs the driver to treat all SQL statements as being in Passthrough transformation mode and to not modify them. • 1 instructs the driver to modify the SQL statements, including converting table names to three-part format and changing NULL and NOT NULL statements. Password A number that determines whether password encryption Encryption can be performed from the Open Client Library to the server. Valid values are: • 0 prevents encryption from being performed. • 1 allows encryption to be performed. Charset The name of a character set corresponding to a subdirectory in Sybase_rootcharsets. The default is the setting on the System 11 or DirectCONNECT Server. WorkstationID The workstation ID used by the client. Language The national language corresponding to a subdirectory in Sybase_rootlocales. The default is U.S. English. ApplicationName The name used by the System 11 or DirectCONNECT Server to identify your application. YieldProc A numeric value that determines whether you can work in other applications when the System 11 or DirectCONNECT Server is busy. Valid values are: • 0 (peek and dispatch) causes the driver to check the Microsoft Windows 3.1, Windows 95 or Windows NT message queue and send any messages to the appropriate application. • 1 (no yielding; the default) prevents you from working in other applications. • 3 (dispatch via Windows NT Yield function) gives control to the Windows NT kernel, which checks the message queue and sends messages to the appropriate applications. Sybase recommends that you use value 1. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 4-3
  • 41. Configuring the Data Source DirectCONNECT for DB2/MVS Release 10.5 Table 4-2: Optional data source configuration properties (continued) Property Description OptimizePrepare A value that determines whether stored procedures are created on the server for every call to SQLPrepare. Valid values are: • 0 causes stored procedures to be created for every call to SQLPrepare. This setting can decrease performance. • 1 causes the driver to create stored procedures only if the statement contains parameters. Otherwise, the statement is cached and executed directly at SQLExecute time. This is the initial default value. • 2 prevents the driver from creating stored procedures. ArraySize The number of rows the driver retrieves from the server for each fetch. This is not the number of rows given to the user. The default is 10 rows. SelectMethod A value that determines whether database cursors are used for select statements. Valid values are: • 0 allows database cursors to be used. This is the initial default. In some cases, performance degradation can occur when large numbers of sequential select statements execute because of the large amount of overhead associated with creating the cursors. • 1 allows select statements to execute directly without database cursors. The data source is limited to one active statement and one active connection. ReuseFailedCursor A value that determines whether the server attempts to reuse a cursor that contains an error. Valid values are: • 0 causes the server to deallocate a cursor that contains an error and force the application to start over. • 1 causes the server to attempt to reuse a cursor containing an error. This is the default value. 4-4 Setting Up the ODBC Driver
  • 42. DirectCONNECT for DB2/MVS Release 10.5 Configuring the Data Source Table 4-2: Optional data source configuration properties (continued) Property Description PacketSize A number that determines the number of bytes per network packet transferred from the database server to the client. The correct setting of this attribute can improve performance. Valid values are: • 0 directs the driver to use the default packet size as specified in the System 11 or DirectCONNECT Server configuration. This is the initial default configuration. • -1 directs the driver to compute the maximum allowable packet size on the first connect to the data source and save the value in the ODBC.ini file. • x (an integer from 1 to 10) directs the driver to set the packet size to x times 512 bytes. For example, a value of 6 sets the packet size at 6 times 512, or 3072 bytes. To use this connection attribute, you must configure the System 11 or DirectCONNECT Server for a maximum network packet size greater than or equal to the value of this property. The ODBC specification specifies a connect option sql_packet_size that offers this same functionality. To avoid conflicts with applications that can set both the connection string attribute and the ODBC connect option, both functions are defined as mutually exclusive. If PacketSize is specified, you receive the message “Driver Not Capable” if you attempt to call sql_packet_size. If you do not set PacketSize, the driver accepts application calls to sql_packet_size. Translate An instruction that displays the Select Translator dialog box, from which you can perform a data translation from one character set to another. Choose the INTERSOLV OEM ANSI translator to translate data from the IBM PC character set to the ANSI character set. 5. Choose OK to write these values to the ODBC.ini file. The values are now the default values when you connect to this data source. 6. To change the values, do one of the following: - Change the defaults by reconfiguring the data source. - Override the defaults by connecting to the data source using a connection string with alternate values. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 4-5
  • 43. Connecting to the Data Source DirectCONNECT for DB2/MVS Release 10.5 Connecting to the Data Source You can use either of two methods to connect to the data source: a logon dialog box or a connection string. Using a Logon Dialog Box Some ODBC applications display a Logon dialog box when you attempt to connect to a data source. In such cases, the data source name already is specified. To use the logon dialog box, enter the information shown in the following table. Table 4-3: Logon dialog box information Entry Instructions Server Name Enter the case-sensitive name of the server containing the System 10 or DirectCONNECT for DB2/MVS database tables you want to access, or select the name from the Server Name drop-down list, which displays the name you specified when you configured the data source. Login ID If required, enter your Login ID (case-sensitive). Password If required, enter your system password (case-sensitive). Database Enter the name of the database you want to access (case- sensitive), or select the name from the Database drop- down list, which displays the name you specified when you configured the data source. Using a Connection String If your application requires a connection string to connect to a data source, you must specify the data source name that tells the ODBC driver the ODBC.ini section to use for the default connection information. Optionally, you can specify attribute=value pairs in the connection string to override the ODBC.ini default values. The override values are not written to the ODBC.ini file. You can specify either long or short names in the connection string. The connection string has the following form: DSN=data_source_name{;attribute=value [;attribute=value];...} 4-6 Setting Up the ODBC Driver
  • 44. DirectCONNECT for DB2/MVS Release 10.5 Mapping Data Types An example of a DirectCONNECT for DB2/MVS connection string is as follows: DSN=SYBDC TABLES; SRVR=QESRVR;DB=PAYROLL;UID=JOHN;PWD=XYZZY Long and short names for each attribute are shown in the following table. Table 4-4: Connection string long and short names Attribute Long Name Short Name DataSourceName DSN ServerName SRVR LoginID UID Password PWD Database DB Language LANG Charset CS HostName HOST ApplicationName APP InterfacesFile IFILE ArraySize AS YieldProc YLD InitializationString IS ModifySQLStatement MSS Mapping Data Types You can map DirectCONNECT for DB2/MVS data types to standard ODBC data types using the lists in the following table. Table 4-5: DirectCONNECT for DB2/MVS and ODBC data types DirectCONNECT for DB2/MVS ODBC binary SQL_VARBINARY bit SQL_BIT char SQL_VARCHAR DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 4-7
  • 45. ODBC Conformance Level DirectCONNECT for DB2/MVS Release 10.5 Table 4-5: DirectCONNECT for DB2/MVS and ODBC data types DirectCONNECT for DB2/MVS ODBC datetime SQL_TIMESTAMP decimal SQL_DECIMAL float SQL_FLOAT image SQL_LONGVARBINARY int SQL_INTEGER money SQL_DECIMAL numeric SQL_NUMERIC real SQL_REAL smalldatetime SQL_TIMESTAMP smallint SQL_SMALLINT smallmoney SQL_DECIMAL sysname SQL_VARCHAR text SQL_LONGVARCHAR timestamp SQL_VARBINARY varbinary SQL_VARBINARY varchar SQL_VARCHAR ODBC Conformance Level The DirectCONNECT for DB2/MVS ODBC driver supports the minimum SQL grammar and the Core, Level 1, and Level 2 API functions in the following lists. Core Functions • SQLAllocConnect • SQLAllocEnv • SQLAllocStmt • SQLBindCol • SQLBindParameters • SQLCancel • SQLColAttributes 4-8 Setting Up the ODBC Driver
  • 46. DirectCONNECT for DB2/MVS Release 10.5 ODBC Conformance Level • SQLConnect • SQLDescribeCol • SQLDisconnect • SQLDrivers • SQLError • SQLExecDirect • SQLExecute • SQLFetch • SQLFreeConnect • SQLFreeEnv • SQLFreeStmt • SQLGetCursorName • SQLLNumResultsCols • SQLPrepare • SQLRowCount • SQLSetCursorName • SQLTransact Level 1 Functions • SQLColumns • SQLDriverConnect • SQLGetConnectOption • SQLGetData • SQLGetFunctions • SQLGetInfo • SQLGetStmtOption • SQLGetTypeInfo • SQLParamData • SQLPutData • SQLSetConnectOption • SQLSetStmtOptions • SQLSpecialColumns DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 4-9
  • 47. ODBC Conformance Level DirectCONNECT for DB2/MVS Release 10.5 • SQLStatistics • SQLTables Level 2 Functions • SQLBrowseConnect • SQLColumnPrivileges • SQLDataSources • SQLDescribeParam • SQLExtendedFetch (forward scrolling only) • SQLForeignKeys • SQLMoreResults • SQLNativeSql • SQLNumParams • SQLParamOptions • SQLPrimaryKeys • SQLProcedureColumns • SQLProcedures • SQLSetPos • SQLSetScrollOptions • SQLTablePrivileges 4-10 Setting Up the ODBC Driver
  • 48. 5 Creating Database Tables 5. This chapter explains how to run SQL scripts to set up database tables. The tables are necessary to use DB2 with DirectCONNECT for DB2/MVS. This chapter includes the following topics: SQL Scripts 5-1 Creating PUBS Tables 5-1 Creating CSP Tables 5-3 SQL Scripts Sybase provides SQL scripts that allow you to create a sample database and system tables on DB2. sybinit installs the scripts in the $SYBASE/scripts subdirectory. The scripts are as follows: • pubsdb2.sql is used to create sample PUBS tables that simulate the PUBS database provided with SQL Server. By installing PUBS tables on DB2, you can more easily test the transfer process between SQL Server and DB2. These tables are not required for DirectCONNECT for DB2/MVS setup, but we recommend installing them to assist Sybase Technical Support. • cspdb2.sql is used to create tables for Catalog Stored Procedures (CSPs). ® Note These tables are required for DirectCONNECT for DB2/MVS setup with DB2. Use the isql utility to run the scripts. We recommend that you complete all of these tasks from the AIX server before you attempt to install Open Client/DB-Library files on any client machines. Creating PUBS Tables PUBS is a sample database that contains tables you can use to test the transfer process between DB2 and SQL Server. Use the pubsdb2.sql script to create the tables by performing the following steps: DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 5-1
  • 49. Creating PUBS Tables DirectCONNECT for DB2/MVS Release 10.5 1. Start the DirectCONNECT Server. 2. Edit pubsdb2.sql to create the tables in the desired DB2 database and tablespace. For example, you can modify the script to say the one of the following: - IN databasename.tablespacename or - IN DATABASE databasename ® Note The user ID must have CREATE TABLE privileges in the specified databasename.tablespacename. 3. Run pubsdb2.sql by entering the following: isql -Uuserid -Ppassword -Sservice_name -ipubsdb2.sql where - isql starts the utility of the same name. - userid is a valid DB2 user ID with CREATE TABLE privileges. - password is a valid password for the DB2 userid you provide. - service_name is the DirectCONNECT Service name. The script drops any tables with the same names as the tables it creates. If no such tables exist, the DropTable command returns an error message. This does not prevent successful execution of the rest of the script. The script creates indexes for the remaining tables. 4. To verify that you successfully created the PUBS database in DB2: - login to DirectCONNECT, isql -Uuserid -Ppassword -Sservice_name - issue the following select statement against PUBS, select * from authors If you successfully created the PUBS database, DB2 returns data from the authors table. If you receive an error, run the pubsdb2.sql script again or review the log files. 5-2 Creating Database Tables
  • 50. DirectCONNECT for DB2/MVS Release 10.5 Creating CSP Tables For information about the transfer function, see the DirectCONNECT for DB2/MVS Access Service Guide. Creating CSP Tables The system tables described in the following table are required if you are using CSPs in DB2. Table 5-1: CSP tables CSP System Table Table Description sp_stored_procedures SYSPROCEDURES This table contains specific information about stored procedures created at your site. sp_sproc_columns SYSPROCCOLUMNS This table contains specific information about the arguments in the stored procedures created at your site. The Database Administrator maintains the information in each table. ® Note If you are upgrading from a previous version of the MDI Database Gateway and you previously populated these tables, save the table contents and use the information to populate the new tables created by cspdb2.sql. Use the cspdb2.sql script to create the tables by performing the following steps: 1. Start the DirectCONNECT Server. 2. Run cspdb2.sql by entering the following: isql -Uuserid -Ppassword -Sservice_name -icspdb2.sql where - isql starts the utility of the same name. - userid is a valid DB2 user ID with CREATE TABLE privileges. - password is a valid password for DB2. - service_name is the DirectCONNECT Service name. The script drops any tables with the same names as tables to be created. If no such tables exist, the DropTable command returns an error message. This does not prevent successful execution of the rest of the script. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX 5-3
  • 51. Creating CSP Tables DirectCONNECT for DB2/MVS Release 10.5 3. Log in to DirectCONNECT and issue a select statement against each table to verify that you successfully created each one: isql -Uuserid -Ppassword -Sservice_name Until you create CSPs, SYSPROCEDURES and SYSPROCCOLUMNS, each table contains column headings, but no rows. 4. Grant SELECT authorization to the following DB2 system tables for all CSP users: - SYSIBM.SYSCOLAUTH - SYSIBM.SYSCOLUMNS - SYSIBM.SYSDATABASE - SYSIBM.SYSFOREIGNKEYS - SYSIBM.SYSINDEXES - SYSIBM.SYSKEYS - SYSIBM.SYSRELS - SYSIBM.SYSSYNONYMS - SYSIBM.SYSTABAUTH - SYSIBM.SYSTABLES Although cspdb2.sql automatically grants SELECT authorization to PUBLIC for the tables it creates, you must grant authorization to these DB2 system tables. 5-4 Creating Database Tables
  • 52. Glossary access management A DirectCONNECT feature that provides connectivity to non-Sybase targets. access service The named set of properties, used with an access service library, to which clients connect. Each DirectCONNECT Server can have multiple services. ACSLIB (access service library) A service library that provides access to non-Sybase data contained in a database management system or other type of repository. Each such repository is called a “target.” Each access service library interacts with exactly one target and is named accordingly. See also service library. ADMLIB (administrative service library) A service library that provides remote management capabilities and server-side support. See also service library. AIX (Advanced Interactive Executive) The IBM implementation of the UNIX operating system. The RISC System 6000, among other workstations, runs the AIX operating system. API (application program interface) A functional interface, supplied by an operating system or other licensed program, that allows an application program to use specific data or functions of the operating system or the licensed program. APPC (advanced program-to-program communication) Hardware and software that characterize the LU6.2 architecture and its various implementations in products. See also LU6.2. AS/400 (Application System/400) A family of products designed to offer solutions for commercial data processing, office, and communications environments. Compare with OS/400. Bourne shell A standard command interpreter used in various versions of the UNIX operating system, including AIX. See also command interpreter. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX Glossary-1
  • 53. DirectCONNECT for DB2/MVS Release 10.5 character set A set of specific (usually standardized) characters with an encoding scheme that uniquely defines each character. ASCII is a common character set. child process In the AIX and OS/2 operating systems, a process, started by a parent process, that shares the resources of the parent. Compare with parent process. CICS (Customer Information Control System) An IBM licensed program that enables transactions entered at remote terminals to be processed concurrently by user-written application programs. client In client/server systems, the part of the system that sends requests to servers and processes the results of those requests. Compare with server. client application Software that is responsible for the user interface, including menus, data entry screens, and report formats. code page An assignment of graphic characters and control function meanings to all code points. collection In the AS/400 system, an object that consists of, and logically classifies, a set of objects, such as tables, views, and indexes. command interpreter A program that reads lines typed at the keyboard and interprets them as requests to execute other programs. The command interpreter in UNIX is called a “shell.” configuration set A section into which service library configuration files are divided. C shell A standard command interpreter used in various versions of the UNIX operating system, including AIX. See also command interpreter. DB2 (Database 2) An IBM relational database management system. Glossary-2
  • 54. DirectCONNECT for DB2/MVS Release 10.5 DB-Library A Sybase and Microsoft API that allows client applications to interact with ODS applications. See also API, ODS. DBMS (database management system) A computer-based system for defining, creating, manipulating, controlling, managing, and using databases. DirectCONNECT A Sybase Open Server application that provides access to non-Sybase data services. Each DirectCONNECT consists of a server and one or more service libraries and provides access to a specific data source. The name replaces “MDI Database Gateway” and “OmniSQL Access Module.” Compare with EnterpriseCONNECT. DirectCONNECT Configuration Tool A Sybase Windows application that provides remote management capabilities for DirectCONNECT products. These capabilities include starting, stopping, creating, and copying services. DirectCONNECT for AS/400 A Sybase LAN-based solution that gives client applications access to AS/400 data. It incorporates the functionality of the MDI Database Gateway and the Sybase Net- Library. DirectCONNECT for DB2/MVS A Sybase LAN-based solution that gives client applications access to mainframe data. It incorporates the functionality of the MDI Database Gateway and the Sybase Net-Library and includes LU6.2 and TCP/IP support. DirectCONNECT Server The component that provides general management and support functions (such as log file management) to service libraries. direct resolution A type of service name resolution that relies upon a client application specifying the exact name of the service to be used. See also service name resolution. Compare with service name redirection. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX Glossary-3
  • 55. DirectCONNECT for DB2/MVS Release 10.5 dll (dynamic link library) A file containing executable code and data bound to a program at load time or run time, rather than during linking. The code and data in a dynamic link library can be shared by several applications simultaneously. EnterpriseCONNECT The encompassing architecture upon which Sybase implements heterogeneous data integration. Compare with DirectCONNECT. environment variable A variable that describes how an operating system runs and the devices it recognizes. event log In Windows NT, the central point for all system and application error and information messages. globalization The combination of internationalization and localization. See also internationalization, localization. host The mainframe or other machine on which a database resides. In TCP/IP, this is any system that is associated with at least one Internet address. See also TCP/IP. interfaces file An operating system file that determines how the host client software connects to a Sybase product. The file must be available on each machine from which connections to DirectCONNECT or other Sybase products are made. internationalization The process of extracting locale-specific components from the source code and moving them into one or more separate modules, making the code culturally neutral so it may be localized for a specific culture. See also globalization. Compare with localization. IPX (Internetwork Packet Exchange) A Novell NetWare communications protocol that corresponds to the Transport and Network layers of the Open Systems Interconnection model. Compare with SPX. Glossary-4
  • 56. DirectCONNECT for DB2/MVS Release 10.5 iso_1 charset A base translation table that corresponds to the ASCII 0819 or the EBCDIC 0500 character sets. journal A system utility that records entries in the journal receiver when a change is made to the database file. It contains information about journal receivers and associated journal database files. See also journaling, journal receiver. journaling The process of recording changes made to the database in a journal receiver. Journaling allows the programmer to reconstruct a physical member by applying changes in the journal to a saved version of that member. See also journal, journal receiver. journal receiver In the AS/400 system, a system object that contains journal entries recorded when changes are made to data in database files or the access paths associated with the database files. See also journal, journaling. Korn shell A standard command interpreter used in various versions of the UNIX operating system, including AIX. See also command interpreter. library list A list that indicates the libraries to be searched and the search order. libtcl file A DirectCONNECT file containing a list of installed Net-Library drivers. Client applications use information in this file to connect to SQL Servers or Open Server applications. See also sql.ini. localization The process of preparing an extracted module for a target environment, in which messages are displayed and logged in the user’s language; numbers, money, dates, and time are represented using the user’s cultural convention; and documents are displayed in the user’s language. See also globalization. Compare with internationalization. logical unit A type of network-accessible unit that enables end users to gain access to network resources and communicate with each other. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX Glossary-5
  • 57. DirectCONNECT for DB2/MVS Release 10.5 LU6.2 (logical unit 6.2) A type of logical unit that supports general communication between programs in a distributed processing environment. See also APPC, logical unit. MainframeCONNECT for DB2/MVS-CICS A Sybase mainframe solution that provides dynamic access to DB2 data. It replaces the OmniSQL Access Module for DB2 and the functionality of the MDI Access Server. MVS (Multiple Virtual Storage) An IBM operating system that runs on most System/370 and System/390 mainframes. named pipes A mechanism for communicating data between two processes on the same machine or on a network. native library An OS/400 library, either created using the CRTLIB command, or already resident on an installed system. See also OS/400. Net-Gateway A Sybase product that provides communication between the mainframe and the LAN server. Replaced by Transaction Router Service. See also TRSLIB. Net-Library A Sybase product that lets PC applications become clients of SQL Server or Open Server. See also client, Open Server, SQL Server. Network ID In TCP/IP, that part of the Internet address that defines a network. The length of the network ID depends upon the type of network class. See also TCP/IP. ODBC (Open Database Connectivity) A Microsoft API that allows access to both relational and non-relational databases. See also API. ODS (Open Database Services) A Sybase product used for creating server applications that respond to DB-Library clients. See also DB-Library. Glossary-6
  • 58. DirectCONNECT for DB2/MVS Release 10.5 OmniCONNECT A variation of Sybase SQL Server that provides a Transact-SQL interface to external data sources, including host data files and tables in other database systems. The name replaces “OmniSQL Gateway” and “OmniSQL Server.” Open Client A Sybase product that provides customer applications, third-party products, and other SYBASE products with the interfaces required to communicate with Open Server and Open Server applications. Open Server A Sybase product that provides the tools and interfaces required to create a custom server. OS/2 (Operating System/2) A multitasking operating system for IBM-compatible personal computers. OS/400 The operating system for the IBM AS/400 computer. Compare with AS/400. parameter A variable that is given a constant value for a specified application and which may denote the application. Compare with property. parent process In the AIX and OS/2 operating systems, a process that creates other processes. Compare with child process. Partner Certification Reports Sybase publications that certify which third-party query and development tools work with Sybase products. property A setting for a server or service that defines the characteristics of the service, such as how events are logged or how datatypes are converted. Compare with parameter. protocol A set of rules that governs the behavior of computers communicating on a network. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX Glossary-7
  • 59. DirectCONNECT for DB2/MVS Release 10.5 qualified named pipes An ODS convention that allows software to communicate with any process running within a network, including other processes running on the same machine. See also ODS. Compare with named pipes. Registry The part of the Windows NT operating system that holds configuration information for a particular machine. Replication Server A Sybase SQL Server application that maintains replicated data and processes data transactions received from a data source. The source can be the primary database or another Replication Server. server A functional unit that provides shared services to workstations over a network. Compare with client. service A functionality available to DirectCONNECT applications. It may be thought of as the pairing of a service library and a set of specific configuration properties. service library A set of configuration properties that determine service functionality. Examples of service libraries include access service libraries, administrative service libraries, and transaction router service libraries. See also ACSLIB, ADMLIB, TRSLIB. service name redirection A type of service name resolution that allows a Systems Administrator to map alternative connections to services. See also service name resolution. Compare with direct resolution. service name resolution The mapping by the DirectCONNECT Server of an incoming service name to an actual service. See also direct resolution, service name redirection. SNA (Systems Network Architecture) An IBM proprietary plan for transmitting information units through networks and controlling network configuration and operation. Glossary-8
  • 60. DirectCONNECT for DB2/MVS Release 10.5 SNA Server A Microsoft communications package that provides SNA connectivity for Windows NT. SNRF (service name redirection file) The default name of the file used for the service name redirection feature. See also service name redirection. SPX (Sequenced Packet Exchange) A Novel NetWare communications protocol that corresponds with the Session layer of the Open Systems Interconnection model. Compare with IPX. sqledit A utility for creating and editing sql.ini files and file entries. See also sql.ini. sql.ini The interfaces file containing definitions for each DirectCONNECT Server to which a workstation can connect. See also interfaces file, libtcl file. SQL Server The server in the Sybase Client-Server architecture. It manages multiple databases and multiple users, tracks the actual location of data on disks, maintains mapping of logical data description to physical data storage, and maintains data and procedure caches in memory. stub In the AIX Network Computing System, a program module that transfers remote procedure calls and responses between a client and a server. Systems Administrator A user authorized to handle DirectCONNECT system administration, including creating user accounts, assigning permissions, and creating new databases. TCP/IP (Transmission Control Protocol/Internet Protocol) A set of communication protocols that supports peer-to-peer connectivity functions for both local and wide area networks. See also host. TRSLIB (transaction router service library) A service library that facilitates access to remote transactions, allowing customers to execute thousands of transactions from virtually any mainframe data source. See also service library. DirectCONNECT for DB2/MVS Installation Guide for RS/6000 AIX Glossary-9
  • 61. DirectCONNECT for DB2/MVS Release 10.5 Glossary-10
  • 62. DirectCONNECT for DB2/MVS Release 10.5 C list of common subdirectories 1-7 list of Open Server subdirectories 1-6 charsets subdirectory list of server subdirectories 1-7 as used in ODBC driver setup 4-3 Open Server subdirectories 1-5 Client Tasks 3-7 to 3-9 overview 1-1 Configure Client Connectivity readme 3-5 files 3-8 relationship between Sybase_root and DirectCONNECT ODBC Driver 3-9 econnect 1-7 Install client application 3-9 rules for installing subdirectories 1-6 Verify Client Connectivity 3-8 system requirements 1-8 Configure Client Connectivity files DirectCONNECT ODBC driver sqledit 3-8 ApplicationName configuration createtable SQL statement property 4-3 as used with ODBC driver setup 4-3 ArraySize configuration property 4-4 Creating database tables Charset configuration property 4-3 CSP tables 3-7, 5-3 to 5-4 DatabaseList configuration DropTable command and error property 4-2 messages 5-2, 5-3 DatabaseName configuration PUBS tables 5-1 to 5-3 property 4-2 SELECT authorization 5-4 DataSourceName configuration SQL scripts 5-1 property 4-2 cspdb2.sql SQL script DefaultLogonID configuration creating CSP tables with 5-3 property 4-2 explanation of 5-1 Description configuration how to run 5-3 property 4-2 InitializationString configuration D property 4-2 InterfacesFile configuration Database Tables property 4-2 CSP 3-7 Language configuration property 4-3 PUBS 3-7 ModifySQLStatements configuration DirectCONNECT Access service property 4-3 components OptimizePrepare configuration DB2 Access Service 3-4 property 4-4 installation 3-3 PacketSize configuration property 4-5 Mainframe Client Connect 3-4 PasswordEncryption configuration DirectCONNECT Configuration Tool property 4-3 overview 1-3 ReuseFailedCursor configuration preinstallation 2-2 property 4-4 DirectCONNECT for DB2/MVS SelectMethod configuration directory components 1-7 property 4-4 directory structure 1-5, 1-7 ServerList configuration property 4-2 hardware and software ServerName configuration requirements 1-8 property 4-2 illustration of installed directories 1-5 DirectCONNECT for DB2/MVS Installation Guide for RISC/6000 AIX Index-1
  • 63. DirectCONNECT for DB2/MVS Release 10.5 setup 3-9 L Translate configuration property 4-5 load tape WorkstationID configuration tape installation instructions 3-2 property 4-3 locales subdirectory YieldProc configuration property 4-3 as used in ODBC driver setup 4-3 DirectCONNECT Server name 3-4 log and trace files 3-9 directory names LU6.2 structure 1-7 preinstallation 2-2 Transaction Router 3-4 E econnect subdirectory M explanation of 1-6 Mainframe Client CONNECT EnterpriseCONNECT overview 1-4 overview 1-1 to 1-4 Mainframe Client Connect DirectCONNECT Access service H components 3-4 MainframeCONNECT for Hardware and software DB2/MVS-CICS requirements 1-8 overview 1-2 home directory name preinstallation 2-2 Bourne shell 2-4 C shell 2-4 installation instructions 3-3 O How to begin your installation 1-4 ODBC.ini file How to change ODBC driver configuring 4-2 configuration property values 4-5 overriding values when connecting to the data source 4-6 I ODBC Administrator how to start 4-1 Installation Instructions ODBC driver home directory name 3-3 changing configuration property Management Components 3-3 values 4-5 sample service 3-5 configuring the data source 4-1 to 4-5 TCP/IP port number 3-5 configuring the ODBC.ini file 4-2 Installing a DirectCONNECT Server connecting to the data source 4-6 to Before you Begin 3-1 4-7 Install Management Components 3-3 connecting to the data source using a install script connection string 4-6 to 4-7 sybinit 3-2 connecting to the data source using a isql utility logon dialog box 4-6 running SQL scripts with 5-1 core functions 4-8, 4-9 example of a connection string 4-7 Index-2
  • 64. DirectCONNECT for DB2/MVS Release 10.5 level 1 functions 4-9, 4-10 Open Server CONNECT level 2 functions 4-10 overview 1-2 list of connection string long and short Open ServerCONNECT names 4-7 preinstallation 2-2 list of ODBC data types 4-7 to 4-8 logon dialog box information 4-6 mapping data types 4-7 to 4-8 P ODBC conformance level 4-8 to 4-10 Preinstallation Checklist optional data source configuration AIX server connected to LAN 2-2 properties 4-2 to 4-5 DirectCONNECT Configuration overview 4-1 Tool 2-2 required data source configuration Install MainframeCONNECT 2-2 properties 4-2 install SNA Server/6000 2-2 starting the ODBC Administrator 4-1 LU6.2 connection to mainframe 2-2 Windows NT environments Open ServerCONNECT for CICS 2-2 supported 4-1 TCP/IP connection to mainframe 2-2 ODBC optional data source Preliminary Tasks configuration properties Deignate TCP/IP Port Number 2-6 ApplicationName 4-3 Designate DirectCONNECT ArraySize 4-4 server 2-5 Charset 4-3 Designate DirectCONNECT DatabaseList 4-2 service 2-5 DatabaseName 4-2 designate home directory 2-3 DefaultLogonID 4-2 designate tape device name 2-3 InitializationString 4-2 Verify Installation of previous InterfacesFile 4-2 products 2-4 Language 4-3 pubsdb2.sql SQL script ModifySQLStatement 4-3 creating PUBS tables with 5-2 OptimizePrepare 4-4 explanation of 5-1 PacketSize 4-5 how to run 5-2 PasswordEncryption 4-3 ReuseFailedCursor 4-4 SelectMethod 4-4 R ServerList 4-2 readme Translate 4-5 DirectCONNECT installation 3-5 WorkstationID 4-3 Rules for installing DirectCONNECT for YieldProc 4-3 DB2/MVS subdirectories 1-6 ODBC required data source configuration properties DataSourceName 4-2 S Description 4-2 ServerName 4-2 sample service Open Client CONNECT configure 3-6 overview 1-3 installation instructions 3-5 SELECT authorization DirectCONNECT for DB2/MVS Installation Guide for RISC/6000 AIX Index-3
  • 65. DirectCONNECT for DB2/MVS Release 10.5 list of tables for 5-4 port number 3-5 select statements preinstallation 2-2 as used with ODBC driver Test 3-7 SelectMethod 4-4 Transaction Router Service for ServerName subdirectory LU6.2 3-4 explanation of 1-7 Troubleshooting 3-9 Server Tasks Configure Sample Service 3-6 Database Tables 3-7 V Service Name Redirection 3-7 Verify Client Connectivity Service Name Redirection sybping 3-8 setup 3-7 SNA Server/6000 preinstallation 2-2 sql_packet_size as used with ODBC driver PacketSize configuration property 4-5 SQLExecute command as used with ODBC driver OptimizePrepare 4-4 SQLPrepare command as used with ODBC driver OptimizePrepare 4-4 stop installation Ctrl C 3-2 sybinit install script 3-2 sybinit installation program list of functions 1-4 sybping 3-8 SYSPROCCOLUMNS explanation of 5-3 SYSPROCEDURES explanation of 5-3 T tape device blocksize 3-2 name 2-3, 3-2, 3-3 Tape Installation Instructions load tape 3-2 TCP/IP designate port number 2-6 Index-4

×