CTRC Client Setup

This chapter includes information for setting up clients for access to DB2 and CICS.

Setting Up DB2 DRDA Client Connections

To configure a connection between a DRDA-based Client and a DB2 database, you must define a data source to the ODBC driver. For each DB2 database that will be accessed, you need to specify the following data source information to configure the ODBC driver to use the CTRC router:

Relational database (RDB) name of the DB2 database you want to access. This value must match the rdbname that you specify with the dbconn server command to configure the CTRC router for communicating with DB2. The RDB name also much match the DDF location defined on the DB2 host (see the "DDF Record in BSDS" section).
Router's hostname or the IP address of the interface that will accept the connection requests.
Port number on which the CTRC router is listening for connection requests. The default is 446.

The procedures for configuring a data source are specific to the client implementation. Refer to the documentation for your DRDA client for details.

Setting up the CICS Client

CTRC supports the IBM CICS Universal Client, IBM TXSeries running as clients, and Microsoft COMTI clients. These clients connect to the Cisco router via TCP/IP.

Setting Up CICS Universal Client Connections

To set up the CICS Universal Client, perform the following tasks:

Step 1 Install the Universal Client for your platform.

Step 2 Choose TCP/IP as your network connection.

Step 3 To have the Universal Client connect to your CTRC server, add an entry in the Server section of the CICSCLI.INI file to define the CTRC server. The following example entry defines a router named CTRCBOX; substitute the LU name of your router for CTRCBOX:

Server = CTRCBOX

Description = TCP/IP Server  
Protocol = TCPIP
NetName = CTRCBOX
Port = 1435

Step 4 If necessary, stop and restart the Universal Client to have the changes take effect and connect to the CTRC server.

If you have multiple servers configured in CICSCLI.INI, some applications might display a list of servers from which to choose. If security is turned on in CICS, a user/password dialog box might appear after selecting a CICS Server.

If you have specified UseDfltUser=NO and AttachSec=Verify in your APPC Connection definition on CICS, a userid and password will be required to use the CICS Terminal. If you are using ECI, pass the userid and password using a command such as:

cicscli /c=ctrcbox /u=p390 /p=p390

The CICS Terminal status line displays the virtual terminal name. When you enter a command on the terminal (for example, CEOT), you will see the SYSID and APPLID of the CICS system to which you are connected.

To connect through multiple connections, increase the MaxServers value in the client section of the CICSCLI.INI file from the default of 1.

Setting Up TXSeries as a CTRC Client

To connect a machine running TXSeries to another CICS host through a CTRC connection, you must create the following CICS resource definitions:

Listener Definition
Communications Definition
Program Definition for each remote program you want to use

You use the cicsadd command to add CICS resource definitions on TXSeries, specifying the values appropriate for your definition in place of the variables shown in italic in the following command syntax.

cicsadd -c className[-r regionName] [-P | -B] [-f fileName] [-m 
modelId] resourceName [attributeName=attributeValue ...]

To use the CTRC router, the value for the resourceName in the Communications Definition (CD) must be the same as the attributeValue specified for the RemoteSysId attribute in the Program Definition. The ListenerName specified in the CD must match the name of the Listener Definition. For example, issuing the following command creates a Communications Definition for the CTRC router with a resourceName of CTRC and a ListenerName of TCP.

cicsadd -c cd -r TX6000 -B CTRC ResourceDescription="Connection thru 
CTRC" ConnectionType=cics_tcp ListenerName=TCP OutboundUserIds=sent 
RemoteCodePageTR="IBM-037" RemoteNetworkName="CICSB" 
RemoteSysSecurity=trusted RemoteTCPAddress="ctrcbox" 
RemoteTCPPort=1435 RemoteLUName="CTRCBOX"

To use a remote program named PNG1, the Program Definition for PNG1 must set the RemoteSysId attribute to CTRC, as shown in the following command:

cicsadd -c pd -r TX6000 -B PNG1 ResourceDescription="eciPing back end" 
RemoteSysId=CTRC RemoteName=PNG1 RSLKey=public

You specify the protocol that the CICS client will use in the Listener Definition. For example, to allow the TXSeries client to connect to the CICS region specified in the previous example commands, TX6000, add a Listener Definition for TCP/IP as shown in the following command.

cicsadd -c ld -r TX6000 -B TCP ResourceDescription="TCP/IP Listener" 
Protocol=TCP

Refer to the IBM TXSeries CICS documentation for more information about specifying CICS resource definitions on TXSeries:

Setting Up COMTI Client Connections

When a COMTI application is built using Microsoft's COMTI Component Builder, it must be defined with the following information to provide remote access to CICS:

"CICS and IMS via TCP/IP" as the remote environment type
"CICS" as the target environment
"MS Link" as the server mode

For the COMTI client to access CICS using the CTRC router, you must define CTRC as a TCP Remote Environment. Use Miscrosoft's COMTI Manager to define the remote environment with the following values:

Select "CICS and IMS using TCP/IP" as the remote environment type
Specify the IP address and TCP port address as configured on the CTRC router
Specify a name and comment for the new remote environment

Refer to the Microsoft COM Transaction Integrator Online Guide for details about setting up and using COMTI.