Configuring Client Connectivity to ECDA

Use dsedit to verify that the client environment is connected correctly to the local area network (LAN) and to the DirectConnect server.

Prerequisites

Be sure that both the DirectConnect server and the access services are running.

Task

Tip: If you verified the ECDA access service using isql, you have already created an entry in the sql.ini file on that machine.

Use dsedit to verify that the ECDA service name and port number match the entry for the access service.

Note: Use the access service name, not the DirectConnect server name.

If you use service name redirection for the server name, see the Enterprise Connect Data Access and Mainframe Connect Server Administration Guide.
Configure the libtcl.cfg configuration file that contains information for each installed Net-Library driver.
Use dsedit 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 sql.ini, to connect to a DirectConnect server using the correct file.