Switch to standard view 
  Sybase logo
 
 
 



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.

 

Installation Checklist

Installation Steps

Installation Tasks

References

Mainframe and Connectivity Installation

(for additional information refer to the Connectivity and Target Installation topics in this chapter)

  1. Define SNA LU6.2 or TCP/IP configuration to allow the DirectConnect server to connect to the mainframe.
Install and configure TCP/IP or SNA. DirectConnect for MVS Connectivity Guide. For additional information refer to the appropriate vendor documentation.
  1. Install Open ClientConnect and Open ServerConnect Base Tape.
  • Install and configure the Open ServerConnect Base Tape to enable MainframeConnect and/or Open ServerConnect.
  • Install and configure the Open ClientConnect Base Tape to enable Open ClientConnect.
Open ClientConnect Installation and Administration Guide for DB2/MVS-CICS
Open ServerConnect Installation and Administration Guide for
DB2/MVS-CICS
  1. Install MainframeConnect
  Mainframe Connect Installation and Administration Guide for
DB2/MVS-CICS
  1. Verify that MainframeConnect is running properly and connected to DB2
Type AMD2 to test the Mainframe Connect transaction. Mainframe Connect Installation and Administration Guide for
DB2/MVS-CICS
  1. Install Open ServerConnect API
    (Install RSP libraries, if appropriate)
  Open ServerConnect Installation and Administration Guide for
DB2/MVS-CICS
  1. Install Open ClientConnect API
    (Install CSA libraries, if appropriate)
  Open ClientConnect Installation and Administration Guide for
DB2/MVS-CICS

DirectConnect Server Installation

(for additional information refer to DirectConnect Server Installation in this chapter)

 
  1. Install DirectConnect for MVS on a test machine.
  • Choose the option that allows installation of a sample access service.
  • Following your installation, make a copy of the sample service; keep the original unchanged for your reference.

DirectConnect for MVS Installation Guide (within the installation guide refer to the chapter for your platform: Windows NT, AIX, HP-UX, or Sun Solaris).

For additional installation instructions refer to: http://techinfo.sybase.com:80/css/
techinfo.nsf/DocID/ID=20470

  1. Test the Connectivity between the DirectConnect server and the MVS mainframe.
  • Use the cicsping or snaping utilities to verify your connectivity.
The cicsping and snaping utilities are distributed with the DirectConnect software. Instructions and a sample can be found in the DirectConnect for MVS Installation Guide.
  1. (Optional) If running on a Windows NT server, you may install DirectConnect Manager on the server.
  • Test connectivity using DirectConnect Manager
DirectConnect Manager for Microsoft Windows NT and Windows 95 Installation Guide.
  1. Configure one DirectConnect service.
    Configure the Server, the DB2 access service, the TRS access service, and the service library.
  • If you did not install DirectConnect Manager on the server, then configure the DirectConnect Server by editing its text files.
  • Alter the sample access service you copied previously with any required site-specific properties
DirectConnect Server Administration Guide
DirectConnect Access Service User's Guide
DirectConnect Transaction Router Service User's Guide
  1. Verify application connectivity between DirectConnect and the target.
Simulate a connection by using the isql utility on the DirectConnect server platform to perform this test. For example, select * from tablename  

Client Installation

(for additional information refer to the Client Installation topic, in this chapter)

  1. Test network connectivity to verify that the your workstation is connected to the LAN and the network protocol is configured correctly.
   
  1. Verify or install Open Client and the ODBC driver on your workstation.
  Open ClientConnect Installation and Administration Guide for DB2/MVS-CICS
  1. Use the sqledit utility on the client to ping the LAN server application.
   
  1. Verify application connectivity between the client and the mainframe. Use the isql utility on the client platform to perform this test.
Use the isql utility to connect to the DirectConnect server and test the connection through to the mainframe. For example, select * from tablename Open ClientConnect Installation and Administration Guide for
DB2/MVS-CICS
  1. Test your applications.
  1. Identify and resolve any error conditions.
  1. Follow your local procedures for placing the new services into production.

 

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:

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:

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:

The shipped library names are unique.

Installing Catalog Stored Procedures for TRS

If you plan to use TRS for DB2 access, you will need to install a new set of mainframe-based CSPs. These CSPs are included with MainframeConnect. Generally, we encourage you to use the DB2 Access Service for applications that use dynamic SQL for DB2 access.

Preserving customized messages

Customized messages are a part of the AMD2 message module, AMD2CAMX. If your site has added customized messages that are not just DB2 standard messages, preserve them before installation of MainframeConnect. You can add these messages to AMD2CAMX after installing this release.

Open ServerConnect Installation

Open ServerConnect is composed of two tapes:

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:

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:

The Transaction Router Services does the following:

Client Installation

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

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

To use your existing RSPs with full backward compatibility, there are no changes required to your RSP application code. However, you will need to re-link your existing RSPs with the new RSP stub libraries. Once you have re-linked with the new stub libraries, you can run the same RSP program within the same CICS region and access it through both MainframeConnect and the Access Server. This will allow you to use the products side-by-side in development, test, and production regions.

Two specific EBFs must be installed to enable this feature:

      • Open Server Connect v. 3.1 (EBF i0078) or later version
      • MainframeConnect v. 11.1 (EBF i0077) or later version


Back to Top
© Copyright 2010, Sybase Inc.