• Installation Steps
• Connectivity
• Target Installation
• DirectConnect Server Installation
• Client Installation
• Coexistence

Installation Steps

All installation guides include a set of detailed installation checklists for the respective product components and should be referenced. Following is one possible scenario for installing DirectConnect that you may use as an end-to-end checklist.

It identifies the major steps for installing DirectConnect, the required tasks, reference sections within this document, and identifies the product documents that are available.

Connectivity

The new architecture supports SNA LU6.2, IBM TCP/IP and Interlink TCP/IP connectivity between the LAN and the mainframe.

Target Installation

In the new architecture, MVS-CICS installation may involve from one to three possible product installations:

• Open ServerConnect for CICS
• Open ClientConnect for CICS
• MainframeConnect for DB2/MVS-CICS

You do not need to install all three products unless you require the functionality provided by each. Each product is self-contained.

Database Gateway customers must install both MainframeConnect for DB2 and Open ServerConnect API to support backward compatible execution of Remote Stored Procedures (RSPs) in the new architecture. Open ClientConnect API is required to support Client Services Applications (CSAs).

MainframeConnect for DB2/MVS-CICS Installation

MainframeConnect is composed of two libraries:

• MainframeConnect Library
• Open ServerConnect CICS Base Tape Library

The first tape provides DB2 access; the second tape provides LAN-to-mainframe connectivity. When installed, these libraries provide everything required to provide connectivity between the DirectConnect and DB2/MVS.

The default transaction name for MainframeConnect release 11.7 is AMD2. The previous products used the following default names:

• MDI for MDI Access Server
• SYRT for OmniSQL Access Module for DB2/MVS-CICS

The shipped library names are unique.

Installing Catalog Stored Procedures for TRS

Open ServerConnect Installation

Open ServerConnect is composed of two tapes:

• Open ServerConnect API Library
• Open ServerConnect CICS Base Tape Library

The first tape provides the Open ServerConnect API (RSPs and RPCs) while the second tape provides the connectivity libraries. These libraries provide everything required for connectivity between the DirectConnect and Open Server applications.

Open ClientConnect Installation

Open ClientConnect is composed of two libraries:

• Open ClientConnect API Library
• Open ClientConnect CICS Base Tape Library

The first tape provides the Open ClientConnectAPI (CSAs) and the second the connectivity. These libraries are required to provide connectivity between MVS-CICS Open Client applications and LAN data sources. If SNA LU6.2 connectivity is employed, then Mainframe Client Connect must also be installed.

DirectConnect Server Installation

DirectConnect Environment

DirectConnect consists of a server and one or more service libraries. The server provides the framework for the service libraries to operate. Each Access Service library accesses data from a particular target database, such as AS/400, DB2, Informix, ODBC, and others. The Transaction Router Service library provides high-performance RPC routing to MVS, MVS/CICS and MVS/IMS environments.

A given DirectConnect service library can be used to create any number of services for access to target data and applications. A "service" is analogous to a Database Gateway or Net Gateway "instance", in that it provides a specific configuration for access to a target. Different services may transform datatypes differently, use different networks, or communicate to different target machines. However, unlike an "instance", a "service" is not a physical server, it is not a separate executable, it does not require a separate process or thread, and it does not listen on a specific network port. The DirectConnect server performs the physical functions of a server for every service you decide to configure.

An Access Service does the following:

• Provides configurable access to a target
• Transforms SQL
• Supports remote procedure calls (RPCs)
• Transfers data between targets
• Supports catalog stored procedures (CSPs) and system stored procedures received from OmniConnect and/or ODBC drivers

The Transaction Router Services does the following:

• Provides configurable access to a target
• Passes SQL to DB2-compliant targets (DB2/MVS and InfoHub)
• Executes mainframe applications on MVS, MVS/CICS and/or MVS/IMS
• Supports catalog stored procedures (CSPs) and system stored procedures received from OmniConnect

Client Installation

Several elements may be required to enable client access to DirectConnect:

• Open Client installation (required)
• DirectConnect ODBC Driver installation (optional)
• DirectConnect Manager installation (optional)

Open Client installation

Sybase Open Client software provides connectivity from client platforms to the DirectConnect server platform. The environment requirements of Open Client make it easy to deploy and maintain. Open Client requires a specific directory structure and specific file locations, environment variables and paths.

 

On a given workstation, you must install Sybase Open Client Client-Library and Net-Library before installing the DirectConnect ODBC driver.

DirectConnect ODBC Driver Installation

Currently, the DirectConnect ODBC Driver allows ODBC applications to Connect to DirectConnect access services and TRS. The driver is a Level 3 ODBC driver and supports Microsoft Windows 32-bit environments. To-date, access services exist for the following targets:

• AS/400
• DB2/MVS
• Informix
• Microsoft SQL/Server
• Anywhere (ODBC)

 

On a given workstation, you must install Sybase Open Client Client-Library and Net-Library before installing the DirectConnect ODBC driver.

DirectConnect Manager installation

Installation of DirectConnect Manager is optional, but highly recommended. DirectConnect Manager prevents common configuration errors and provides built-in help to assist with configuration. It is a 16-bit Windows-compatible GUI application that can run on Windows95 and Windows NT machines.

Install DirectConnect Manager after you install the DirectConnect but before you finish configuring DirectConnect.

The installation process itself will let you create sample services and these should be customized for your environment using Configuration Manager.

Coexistence

Our customers typically like to install old and new products side-by-side in test environments as they work through the process of migration. Minimizing the differences between installation of old and new products as much as possible aids trouble-shooting efforts and allows side-by-side comparisons between the products. To help you with both of these efforts this section will review various issues with product coexistence.

Gateways

You can easily setup older gateways and DirectConnect products on the same LAN server for testing. The gateways can share common communications configurations (the same remote and partner LU, for example) with the older products, which should help you with your testing. Gateway coexistence issues usually involve proper setup of configuration files and accommodating different server connectivity libraries.

DirectConnect & Database Gateway, v. 2.05

You should install the DirectConnect under a dedicted unique parent directory. The parent directory is the SYBASE variable value. For example, if the default directory is MDIMSV25, then the Sybase variable should be SYBASE=drive:\DC117. DirectConnect files can then be installed within the \econnect sub-directory beneath the Sybase parent directory. The resulting directory structure for the DirectConnect files, might be drive:DC117\econnect\ etc. The DirectConnect will use the Open Server libraries installed in DC117 and the ini file in DC117\ini.

DirectConnect & Database Gateway, v 2.03.x and later

Other versions of the Database Gateway were built on the Microsoft ODS infrastructure—not Open Server. Therefore, you can easily install DirectConnect and Database Gateway on the same machine as the older gateways, by using separate directory structures.

Mainframe

MainframeConnect, Open Server Connect, Open Client Connect and the Access Server 2.03.x or 2.05.x) can exist in the same CICS region. You will want to be careful about CSP and RSP coexistence.

RSP coexistence