Previous Topic: ODBC Driver ManagerNext Topic: Test Your Connection


Configure Your ODBC Client

You use the Microsoft ODBC Administrator to configure access to CA Datacom/DB. You must have Administrator access rights to create or modify any ODBC data source, including the default ODBC data source for CA Datacom.

To configure access to CA Datacom/DB

  1. Open the Data Sources (ODBC) applet under Control Panel/Administrator Tools.

    The ODBC Data Source Administrator window appears showing the User DSN tab. Click the System DSN tab.

    Note: This dialog can vary according to the version of ODBC or Windows installed on the workstation or application server. Use the Help provided by the ODBC Administrator.

  2. Click Add to create a new ODBC data source for use with CA Datacom Server.

    The Create New Data Source window appears.

    To edit the default CA Datacom data source defined during installation, double-click the CA Datacom entry in the System DSN tab and proceed with item 4.

  3. Double-click CA Datacom/DB in the list of installed drivers.

    The CA Datacom/DB ODBC Setup window appears.

  4. Complete the following fields in the DataSource Options section on the DataSource tab:
    Data Source

    Provides a standardized data source name or lets you specify a name.

    Description

    Provides a standardized description or lets you describe the new data source.

    Server

    Provides server names from the drop-down list in the Server field, which contains all the Datacom/Server ODBC defined data sources that are defined to the ODBC Driver Manager. If the appropriate server name is not shown on the drop-down list, over type the value to add a new entry. It must match the SERVERNAME= startup parameter in the CA Datacom Server mainframe component.

  5. Select CCI or TCP/IP (z/OS only) in the Connection Options section to specify the protocol to use with this workstation.

    If the PROTOCOL parameter in the mainframe component startup options is set to CCI, you must select CCI and you must have CAICCI-PC installed on the client.

    If the PROTOCOL parameter in the mainframe component startup options is set to BOTH, you can choose CCI or TCP/IP.

  6. Complete the following fields in the Connection Options section on the DataSource tab:
    Application

    Specifies the application name in the Application field as specified in the APPLID= parameter in the mainframe component startup JCL.

    System

    Specifies the CAICCI System ID of the mainframe environment in the System field to which the workstation is to connect when the data source is selected. This is the SYSID name specified in the CAICCI startup JCL.

    Note: if TCP/IP was selected as the desired communications protocol, use the System field as a token to uniquely identify the mainframe system where the Server mainframe component resides. It can be any character string that identifies the LPAR. However, since CAICCI is required for the Server mainframe component, we recommend that you use the SYSID name. This aids in switching between CCI and TCP/IP protocols if you choose to do so

    Host Name

    Specifies the IP address or DNS host name of the mainframe system you are connecting to. Host name may be specified for the CCI communication protocol. If specified, it overrides the Host name specified in the CCI Configuration dialog.

    If TCP/IP (z/OS only) is specified, then the host name, port number, and application must be present. The application name must match the applid specified in the server startup parameter.

    Port Number

    Specifies the port number of the connection used to communicate with the mainframe component.

    You can specify Port Number for a CCI connection. If specified, the port number in the ODBC data source overrides the port number specified in the CCI Configuration dialog allowing you to switch mainframe regions without changing the CCI configuration.

    Port Number is required If TCP/IP (z/OS only) is selected as the communication protocol, it must match the TCPIP_PORT specified in the Server mainframe component startup parameters.