Table Of Contents
Cisco Transaction Connection
Feature Overview
CTRC and CICS
CTRC and DB2
Benefits
Related Documents
Supported Platforms
Supported Standards, MIBs, and RFCs
Configuration Tasks
Configuring CICS on the Host
Configuring a CICS Client
Configuring DB2 on the Host
Configuring SNA Switching Services
Configuring a CTRC Destination (CICS)
Configuring a CTRC Server (CICS)
Configuring a CTRC Route (CICS)
Configuring a CTRC Server (DB2)
Configuring the CTRC License
Verifying SNA Connectivity
Verifying CTRC Configuration
Monitoring and Maintaining CTRC Communications with CICS
Command
|
Purpose
|
Router#show txconn server
|
Displays a list of CTRC servers for CICS communications for the current router.
|
Router#show txconn server server-name
|
Displays detailed status information for the specified CTRC server.
|
Router#show txconn connection [server server-name]
|
Displays a list of all CTRC connections to CICS clients from the current router or a particular server's CICS client connections.
|
Router#show txconn connection connection-id
|
Displays detailed status information for the specified CTRC connection to a CICS client.
|
Router#show txconn transaction [server server-name connection
connection-id]
|
Displays a list of the current router's CTRC transactions involving CICS, or the transactions of a particular server or CICS client connection.
|
Router#show txconn transaction transaction-id
|
Displays detailed status information for the specified CTRC transaction.
|
Router#show txconn route [server server-name]
|
Displays a list of CTRC routes to CICS for the current router or a particular server.
|
Router#show txconn destination
|
Displays a list of all the current router's CTRC destinations for CICS communications.
|
Router#show txconn destination destination-name
|
Displays detailed status information for the specified CTRC destination.
|
Router#clear txconn transaction transaction-id
|
Kills the specified CTRC transaction.
|
Router#clear txconn connection connection-id
|
Kills the specified CTRC connection to a CICS client and all associated transactions.
|
Router#clear txconn statistics [kind histogram | kind summary]
name {activeconnections | activetransactions | allocatetime |
clientreceived | clientsent | clientturnaround | dump |
hostreceived | hostresponse | hostsent | latency |
maxconnections | maxtransactions | totalconnections |
totaltransactions}
|
Clears specific statistics or all statistics related to CTRC communications with CICS.
|
Router#debug txconn {appc | config | data | event | tcp |
|
Enables debugging of CTRC communications with CICS.
|
|
Displays current status of debugging for the router.
|
Router#show txconn license or show dbconn license
|
Shows the status of the CTRC license.
|
Router#txconn ping destination-name
|
Verifies connectivity with a specific CICS destination.
|
Router#show txconn statistics [kind histogram | kind summary]
name {activeconnections | activetransactions | allocatetime |
clientreceived | clientsent | clientturnaround | dump |
hostreceived | hostresponse | hostsent | latency |
maxconnections | maxtransactions | totalconnections |
totaltransactions}
|
Displays statistics related to CTRC communications with CICS.
|
Monitoring and Maintaining CTRC Communications with DB2
Command
|
Purpose
|
Router#show dbconn server
|
Displays a summary of information about each CTRC server configured to communicate with DB2.
|
Router#show dbconn server server-name
|
Displays a detailed status of the specified CTRC server for DB2 communications.
|
Router#show dbconn connection
|
Displays the status of each CTRC connection to DB2.
|
Router#show dbconn connection connection-id
|
Displays a detailed status of the specified CTRC connection to DB2.
|
Router#show dbconn connection server server-name
|
Displays the status of CTRC connections to DB2 for the specified server.
|
Router#show dbconn connection user userid
|
Displays the status of a user connected to the CTRC for DB2 communications.
|
Router#show dbconn connection rdbname rdb-name
|
Displays a status of each connection to DB2 that matches the specified RDB name.
|
|
Displays information on all ports through which CTRC servers are accepting connections to DB2.
|
Router#show dbconn license or show txconn license
|
Displays the status of the CTRC license for both DB2 and CICS.
|
Router#clear dbconn connection connection-id
|
Breaks the specified client connection to the server.
|
Router#dbconn ping server-name [rdbname rdbname]
[userid userid] [password password]
|
Connects to the DB2 relational database on the IBM system for troubleshooting.
|
Router#debug dbconn {appc | config | drda | event | tcp | all}
|
Enables debugging of CTRC communications with DB2.
|
|
Displays current status of debugging for CTRC.
|
Router#show dbconn statistics
[chains|clientturnaround|connectionsdown|connectionsup|dump|
hostreceived|hostresponse|hostsent|latency|max connections]
|
Displays current statistics related to CTRC communications with DB2.
|
Router#clear dbconn statistics
[chains|clientturnaround|connectionsdown|connectionsup|dump|h
ostreceived|hostresponse|hostsent|latency|max connections]
|
Clears statistics related to CTRC communications with DB2.
|
Configuration Examples
CTRC Servers with IP Addresses Configuration Example (DB2)
CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 1 (DB2)
CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 2 (DB2)
Server Selection by IP Addresses, RDB Names, and Ports Configuration Example (DB2)
CTRC with CIP and DB2 on VTAM Configuration Example (DB2)
CTRC Servers Using Token Ring to a LEN Configuration Example
(CICS and DB2)
CTRC Servers with IP Addresses, Routes, and Multi-Valued Destinations Configuration Example (CICS)
Command Reference
clear dbconn connection
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
clear txconn connection
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
clear txconn statistics
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
clear dbconn statistics
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
clear txconn transaction
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
dbconn license
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
dbconn pem
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
dbconn ping
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
dbconn server
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
dbconn tcpserver
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show dbconn connection
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show dbconn license
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show dbconn ports
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show dbconn server
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show dbconn statistics
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show dbconn wlm
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn connection
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn destination
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn license
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
show txconn route
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn server
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn statistics
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
show txconn transaction
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
txconn destination
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
txconn license
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
txconn ping
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
txconn route
Syntax Description
Defaults
Command Modes
Command History
Examples
Related Commands
txconn server
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Examples
Related Commands
Debug Commands
debug dbconn all
Syntax Description
Defaults
Command History
Examples
Related Commands
debug dbconn appc
Syntax Description
Defaults
Command History
Examples
Related Commands
debug dbconn config
Syntax Description
Defaults
Command History
Examples
Related Commands
debug dbconn drda
Syntax Description
Defaults
Command History
Examples
Related Commands
debug dbconn event
Syntax Description
Defaults
Command History
Examples
Related Commands
debug dbconn tcp
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn all
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn appc
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn config
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn data
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn event
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn tcp
Syntax Description
Defaults
Command History
Examples
Related Commands
debug txconn timer
Syntax Description
Defaults
Command History
Examples
Related Commands
Error Messages
Glossary
Cisco Transaction Connection
This feature module describes the Cisco Transaction Connection (CTRC) software feature. It includes information on the benefits of using CTRC, supported platforms, configuration instructions, commands, error messages, and additional information about CTRC.
This document contains the following sections:
•
Feature Overview
•CTRC and CICS
•CTRC and DB2
•Benefits
•Related Documents
•Supported Platforms
•Supported Standards, MIBs, and RFCs
•Configuration Tasks
•Elapsed time was 00:00:00Monitoring and Maintaining CTRC
•Configuration Examples
•Command Reference
•Debug Commands
•Error Messages
•Glossary
Feature Overview
The Cisco Transaction Connection (CTRC) software feature provides the following functionality:
•CTRC allows Cisco routers to use the intersystem communication (ISC) protocol to provide a gateway between Customer Information Control System (CICS) clients (also known as common clients) running under Windows or UNIX on Transmission Control Protocol/Internet Protocol (TCP/IP) networks and CICS online transaction monitoring systems on IBM hosts.
•CTRC supports two interfaces to common clients: the Extended Call Interface (ECI), which lets non-CICS client programs call CICS transactions, and the Extended Presentation Interface (EPI), which lets distributed applications call CICS transactions that were originally accessed via 3270 terminals.
•CTRC supports the ability to configure routes for CICS transaction. Each transaction can be routed to a specific CICS region.
•In addition to its CICS-related functionality, CTRC includes the feature previously known as Cisco Database Connection (CDBC), which allows Cisco routers to use IBM's distributed relational database architecture (DRDA) protocol to provide a gateway between client workstations running ODBC-compliant applications on TCP/IP networks and IBM DB2 databases on Systems Network Architecture (SNA) networks. ODBC (Open Database Connectivity) is a call-level interface developed by Microsoft Corporation that allows a single application to access database management systems from different vendors using a single interface. SNA is a large, complex, feature-rich network architecture developed by IBM.
•CTRC adds support for TCP/IP passthrough, allowing the use of a TCP/IP network, rather than a SNA network, between a Cisco router and a DB2 database if the database version supports direct TCP/IP access.
•To match functionality provided in DRDA over TCP/IP, CTRC adds support for Password Expiration Management (PEM) in SNA networks where PEM is supported.
CTRC and CICS
When a router is configured to use CTRC for communications with CICS systems, the router converts ISC packets over TCP/IP to ISC packets over Advanced Program-to-Program Communications (APPC LU6.2) and then routes them to the appropriate CICS region. CTRC converts CICS client messages received via TCP/IP to SNA messages and uses Cisco SNA Switching Services to transmit them to the host.
CTRC runs as a TCP/IP daemon on the router, accepting ISC client connections over TCP/IP. When a client connects to a CICS region on an IBM mainframe host, CTRC allocates an APPC conversation over SNA to an IBM server and acts as a gateway between ISC over TCP/IP and ISC over APPC.
illustrates how CTRC lets CICS client applications on TCP/IP networks interact with CICS transaction monitoring systems on IBM hosts.
Figure 1 Cisco Router Configured with the CTRC Feature for CICS Communications
CTRC and DB2
CTRC enables Cisco routers to implement IBM's DRDA over TCP/IP. The Cisco router with CTRC exists in the TCP/IP network, and clients use a CTRC IP address and port on the router to connect to the IBM host system that exists in either an SNA network or a TCP/IP network.
When CTRC is appropriately configured on a router, client-based ODBC applications can connect to the following IBM D2 relational databases:
•DB2 for OS/390 (MVS)
•DB2 for Virtual Machine (VM) (SQL/DS)
•DB2 for Virtual Storage Extended (VSE) (SQL/DS)
•DB2 for OS/400
•DB2 Universal Database (UNIX, Windows, OS/2)
For an SNA host connection, the router with CTRC converts DRDA packets over TCP/IP to DRDA packets over (APPC LU 6.2) and then routes them to DB2 databases. CTRC runs as a TCP/IP daemon on the router, accepting DRDA client connections over TCP/IP. When a client connects to the database on an IBM mainframe host, CTRC allocates an APPC conversation over SNA to an IBM server, and acts as a gateway between DRDA over TCP/IP and DRDA over APPC.
illustrates how the Cisco router configured with the CTRC feature enables the exchange of database information between ODBC client applications running DRDA in a TCP/IP network and a DRDA-based IBM system that accesses DB2 relational data.
Figure 2 Cisco Router Configured with the CTRC Feature for DB2 Communications (SNA Host Network)
For a TCP/IP host connection, the router with CTRC routes the DRDA packets over TCP/IP without protocol changes. To use this TCP/IP passthrough feature of CTRC, the host database version must support direct TCP/IP access. illustrates such a configuration.
Figure 3 Cisco Router Configured with the CTRC Feature for DB2 Communications (TCP/IP Host Network)
When configured for DB2 communications on a router, the CTRC feature enables desktop applications to access data in remote databases located on IBM hosts. CTRC receives database access messages from the client over a TCP/IP link. CTRC either converts the messages to SNA and transmits them to the host using APPC services provided by the Cisco SNA Switching Services, or routes the client messages to the TCP/IP-enabled host without protocol changes.
Benefits
Cisco Transaction Connection (CTRC) provides TCP/IP end-users and servers with fast, reliable, and secure access to IBM DB2 databases using the Systems Network Architecture (SNA) protocol. CTRC, a cost-effective software and router solution based on Cisco IOS software, replaces expensive and hard to manage UNIX and NT gateways for database access.
CTRC lets Windows or UNIX client applications call CICS transactions without requiring changes to the client or host software. CTRC provides improved performance, lower cost of ownership, and greater reliability than existing solutions from other vendors.
In addition, CTRC provides Cisco 7200 and 7500 series routers with the functionality previously available in CDBC, which gives ODBC client applications access to data in DB2 databases.
Related Documents
For information related to this feature, refer to the following document:
•Cisco IOS Release 12.0(5)XN SNA Switching Services
•Revealed! CICS Transaction Gateway with More CICS Clients Unmasked
(IBM publication SG24-5277)
See Chapter 15.4 (Configuration for VTAM & CICS TS for OS/390 when connecting with Microsoft SNA Server)
•CICS Transaction Server for OS/390 V1R2 CICS Intercommunication Guide
(IBM publication SC33-1695)
•DRDA Connectivity Guide
(IBM publication SC26-4783)
•Distributed Relational Database Architecture (DRDA)
(Open Group publication C812, ISBN 1-85912-295-7)
Supported Platforms
•Cisco 7200 series routers
•Cisco 7500 series routers
Supported Standards, MIBs, and RFCs
MIBs
•CISCO-DATABASE-CONNECTION
•CISCO-TRANSACTION-CONNECTION
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Standards
No new or modified MIBs are supported by this feature.
Configuration Tasks
CTRC can be configured for use with CICS, with DB2, or both. Both CICS and DB2 configurations require Cisco SNA Switching Services. A few basic instructions for configuring SNA Switching Services are included in the following sections. For more extensive information, consult the SNA Switching Services documentation.
Note CTRC commands related to communications with CICS contain the word txconn. CTRC commands related to communications with DB2 contain the word dbconn. With the exception of commands related to licensing, dbconn and txconn commands act independently of each other and are discussed separately in this document. To configure CTRC for use with both CICS and DB2, complete all the configuration tasks listed below. To configure CTRC for use with CICS only, complete all the configuration tasks except those marked (DB2). To configure CTRC for use with DB2 only, complete all the configuration tasks except those marked (CICS). See the "Configuration Examples" section of this document for additional information.
Perform the following tasks to configure CTRC, in the order that they are listed here:
•Configuring CICS on the Host
•Configuring a CICS Client
•Configuring DB2 on the Host
•Configuring SNA Switching Services
•Configuring a CTRC Destination (CICS)
•Configuring a CTRC Server (CICS)
•Configuring a CTRC Route (CICS)
•Configuring a CTRC Server (DB2)
•Configuring the CTRC License
•Verifying SNA Connectivity
•Verifying CTRC Configuration
Configuring CICS on the Host
If you plan to use CTRC to communicate with CICS, you must configure CICS for APPC connections. Refer to the "Related Documents" section for additional information.
To configure CICS on the host, complete the following tasks:
•In VTAM, define the PU and LU for the Cisco router that will run CTRC.
•Choose a mode name that will be used by both the Cisco router and VTAM, such as #INTER, and make a note of it.
•Make a note of the VTAM APPLID value. You will need this value in later steps.
•In the CICS System Initialization Table (SIT), set ISC to YES, and set APPLID to the VTAM APPLID value.
•In CEDA (a CICS resource definition transaction), create a SNA Connection Definition with a unique four-character name (such as CTRC). Set NETNAME to the router's LU name (control point name). Set the following additional values:
—Accessmethod: VTAM
—Protocol: APPC
—Attachsec: Verify
•Also in CEDA, create sessions related to the Connection Definition. Set the mode name to the value you chose earlier.
•Make sure that your CICS system includes a DFHCNV table for data conversion between ASCII and EBCDIC. If this table is not present, attempts to install and use CTRC may encounter APPC errors on the host that report failure to transform data received from the remote system. A DFHCNV table may contain lines such as are shown below. For more information about DFHCNV tables, see your CICS documentation.
PRINT NOGEN
DFHCNV TYPE=INITIAL,SRVERCP=037,CLINTCP=437
DFHCNV TYPE=FINAL
END DFHCNVBA
The "Configuration Examples" section of this document illustrates many of the host configuration tasks described above.
Configuring a CICS Client
To use IBM's CICS Common Client application with CTRC, complete the following tasks:
•Install the CICS client. You do not need to install TCP62.
•Edit the file CICSCLI\BIN\CICSLI.INI as follows:
•If you want to use multiple servers, increase the value of MaxServers from its default value of 1.
•Create one or more server descriptions, supplying the following information and making a note:
Server = Server name
Protocol = TCPIP
NetName = Host name or IP address for the CTRC router
Port = TCP/IP port number for the CTRC router (specify 0 to use the default of 1435)
•Include the following driver statement:
Driver = TCPIP
Drivername = CCLWNTIP
Configuring DB2 on the Host
For information about preparing a DB2 system to receive communications from CTRC, see the CTRC Planning Guide available from StarQuest Software, Inc.:
StarQuest Software, Inc.
1288 Ninth Street
Berkeley, CA 94710-1501
1-800-763-0050 in the US and Canada
1-510-528-2900 Worldwide, ask for extension 170
1-510-528-2986 FAX
sales@starquest.com
Configuring SNA Switching Services
To configure basic SNA Switching Services, complete the following steps:
Step
|
Command
|
Purpose
|
1
|
Router#snasw cpname netid.cpname [hostname]
[ip-address interface-name]
|
Defines a SNA Switching Services control point name.
|
2
|
Router#snasw port portname [hpr-ip | vdlc
vring mac mac-address] [interfacename]
[conntype nohpr | len | dyncplen]
[dlus-required] [hpr-sap hpr-sap-value]
[max-links link-limit-value] [sap sap-value]
[vnname virtual-node-name] [nostart]
|
Associates a SNA Switching Services port with an interface.
|
3
|
Router#snasw link linkname port portname [rmac
mac-address | ip-dest ip-address] [rsap
sap-value] [nns] [nostart]
|
Associates a SNA Switching Services link with a SNA Switching Services port.1
|
Note For a LEN level connection between SNA Switching Services and the host, you will also need to configure the snasw location configuration command for the specific resource names to be contacted on the host. Do not define locations if APPN connectivity is being used between SNA Switching Services and the host.
For additional information about configuring SNA Switching Services, consult the SNA Switching Services documentation.
Configuring a CTRC Destination (CICS)
To configure CTRC to communicate with CICS, the first step is to configure a CTRC destination. If you do not need to communicate with CICS, skip to the "Configuring a CTRC Server (DB2)" section. A CTRC destination is ordinarily a single CICS system defined in terms of its remote LU name and APPC mode. Use the following global configuration command to configure a destination:
Command
|
Purpose
|
Router(config)#txconn destination destination-name
rlu rlu-name mode mode-name
|
Specifies a CICS system with which CTRC will communicate.
|
For load-sharing purposes, the txconn destination command can be repeated with the same destination name but new remote LU and mode values to assign more than one CICS system or region to a single CTRC destination name. If a CTRC destination is configured in this way, the CTRC server sends traffic to the destination's defined CICS regions on a rotating basis. A Cisco router can be configured to communicate with multiple CTRC destinations, whether each of those destinations is defined as an individual pair of remote LU and mode values or as a set of such values.
Configuring a CTRC Server (CICS)
After you have configured a CICS destination, you can configure a CTRC server process that will handle communications with that CICS system. Additional CTRC servers can be configured on the same router for communications with other CICS destinations. Use the following global configuration command to configure a CTRC server process to communicate with CICS:
Command
|
Purpose
|
Router(config)#txconn server server-name
destination destination-name [ipaddress ip-address]
[port port-number] [client-timeout minutes]
[host-timeout minutes] [window-size bytes] [fold [off|on]]
|
Configures a CTRC server process for communicating with CICS. Note that if you do not supply a port number, CTRC uses the default value of 1435.
|
When a client attempts to connect to a CTRC server for CICS, the server's port and IP address determine whether that connection is accepted or not. By default, the CTRC server port for CICS client communications is 1435. You can create multiple CTRC txconn and dbconn server processes on one router.
Configuring a CTRC Route (CICS)
After you have configured one or more destinations and server processes for communicating with CICS, you have the option of explicitly configuring CTRC routes that will direct traffic to the appropriate destination based on a transaction ID. If you do not explicitly configure CTRC routes, the CTRC server routes traffic to its own default destination. To configure a CTRC route, use the following global configuration command:
Command
|
Purpose
|
Router(config)#txconn route [server server-name] tranid
transaction-id destination destination-name
|
Configures a particular route for traffic with the specified transaction ID.
|
Configuring a CTRC Server (DB2)
To configure a CTRC server process for communications with DB2, use the following command in global configuration mode:
Command
|
Purpose
|
Router(config)#dbconn server server-name [ipaddress
ip-address] [port port-number] [rdbname rdbname] [rlu
remote-lu] [mode mode] [tpname tp-name] [idle-timeout
minutes] [window-size bytes][wlm [off|on]]
|
Configures a CTRC server for communications with DB2.
|
When a client attempts to connect to a CTRC server for DB2, the server's port, IP address, and remote database name (RDB name) determine if that connection is accepted. By default, the CTRC server port for client requests for DB2 communications is 446. You can create multiple CTRC dbconn and txconn server processes on one router.
Configuring the CTRC License
An unlicensed installation of CTRC allows you to use up to two DB2 connections, two CICS conversations, or one DB2 connection and one CICS conversation for testing purposes. For communications with DB2, CTRC checks the number of connections against the licensed number of users. For communications with CICS, CTRC checks the number of concurrent and queued conversations. To use additional connections or conversations, you must configure the CTRC license. One license key is used for both CICS and DB2 communications.
To obtain your CTRC license key, use the show config | include cpname command to determine the SNA Switching Services cpname for the router you will be licensing. (The CTRC license key is locked to one node and is based on the cpname.) Next, contact your Cisco representative, request a CTRC license key, and provide the cpname value. You should receive information about the number of connections you are licensing along with the license key. If the key is temporary, you should also receive information about the expiration date. After obtaining your license key, use either of the following global configuration commands to configure the CTRC license:
Command
|
Purpose
|
Router(config)#dbconn license license-key
connections licensed-connections
[expiration-date yyyymmdd]
|
Configures a CTRC license key for DB2 or CICS.
|
Router(config)#txconn license license-key
[connections licensed-connections]
[expiration-date yyyymmdd]
|
Configures a CTRC license key for CICS or DB2.
|
Verifying SNA Connectivity
To verify that you have SNA connectivity between the router and each host system, complete the following task:
•Use the ping sna command, specifying the mode and the remote LU name:
ping sna -m IBMRDB STARW.BUDDY
Verifying CTRC Configuration
To verify the CTRC configuration, complete the following tasks:
Step 1 If you did not configure CTRC for communications with CICS, go to Step 6.
Step 2 If you configured CTRC for communications with CICS, enter the show txconn destination command in EXEC or privileged EXEC mode. Make sure that any CICS destinations you configured are listed with the RLU and mode values you specified.
Router>show txconn destination
----------------- ------------------ ----------- --------
Step 3 Enter the show txconn server command. Make sure that any CTRC servers you defined for communications with CICS are listed with the configuration values you specified.
Router>show txconn server
Server Port IP Address Dest State NumConn
---------- ----- ------------ --------- --------- -------
CICSB 1435 0.0.0.0 CICSB enabled 1
CICSB&C 1436 0.0.0.0 GEN enabled 0
CICSC 1434 0.0.0.0 CICSC enabled 0
GUAVA 1437 0.0.0.0 GUAVA enabled 0
If necessary, use the show txconn server server-name form of the command to display more information for an individual server.
Router>show txconn server CICSB
server state: enabled (accepting connections)
number of transactions: 2
Step 4 If you defined any routes for specific transaction IDs to take to CICS destinations, enter the show txconn route command. Make sure that any CTRC routes you defined are listed with the configuration values you specified. A <default> in the SERVER column indicates a global route that is used by all txconn servers on the router. A <default> in the TRANID column indicates the default route for the listed txconn server.
Server TranID Destination
----------------- ----------------- ----------------
Step 5 If you did not configure CTRC communications with DB2, go to Step 7.
Step 6 If you configured CTRC for communications with DB2, enter the show dbconn server command. Make sure that the servers you defined are listed with the configuration values you specified. If necessary, use the show dbconn server server-name form of the command to display more information for an individual server.
Router>show dbconn server
Server Port IPAddress RDBName State NumConn
SERVERA 446 0.0.0.0 MATTY enabled 0
SERVERB 446 0.0.0.0 SCU_DSNM enabled 4
SERVERC 446 0.0.0.0 DSN4 enabled 0
SERVERD 446 0.0.0.0 MKTG enabled 0
SERVERE 446 0.0.0.0 ABBY enabled 6
SERVERF 446 0.0.0.0 DB2510 enabled 0
SERVERG 446 0.0.0.0 ELLE enabled 3
SERVERH 446 0.0.0.0 SUNSET enabled 0
SERVERI 446 0.0.0.0 NELL enabled 1
SERVERJ 446 198.989.999.32 SAMPLE enabled 0
SERVERK 446 0.0.0.0 DB2410 enabled 0
SERVERL 446 0.0.0.0 SQLDS enabled 0
SERVERM 446 0.0.0.0 STELLA enabled 1
SERVERN 446 10.10.19.4 OAK enabled 2
SERVERO 447 0.0.0.0 DB2510 enabled 0
Router>show dbconn server BUDDY
server state: enabled (accepting connections)
database server name: (unknown)
database product id: (unknown)
Step 7 Enter either the show dbconn license command or the show txconn license command. Make sure that the reported number of licensed connections matches the number you purchased.
Router>show txconn license
CTRC is licensed for 4990 connections, 20 licensed connections in use
This is a permanent license
Router>show dbconn license
CTRC is licensed for 1000 connections, no licensed connections in use
Step 8 For each CICS destination you displayed in Step 1, enter the txconn ping command to verify that the router can communicate with that destination.
Trying CICSB CICSB:IBMRDB
Destination CICSB successfully contacted!
Elapsed time was 00:00:00.600
Step 9 For each dbconn server you displayed in Step 6, enter the dbconn ping command to verify that the router can communicate with the DB2 systems associated with that server.
RDB named DB2510 on database server successfully contacted!
Elapsed time was 00:00:00Monitoring and Maintaining CTRC
This section describes commands used to monitor and maintain CTRC. Commands for CICS communications and DB2 communications are shown separately.
Monitoring and Maintaining CTRC Communications with CICS
Command
|
Purpose
|
Router#show txconn server
|
Displays a list of CTRC servers for CICS communications for the current router.
|
Router#show txconn server server-name
|
Displays detailed status information for the specified CTRC server.
|
Router#show txconn connection [server server-name]
|
Displays a list of all CTRC connections to CICS clients from the current router or a particular server's CICS client connections.
|
Router#show txconn connection connection-id
|
Displays detailed status information for the specified CTRC connection to a CICS client.
|
Router#show txconn transaction [server server-name connection
connection-id]
|
Displays a list of the current router's CTRC transactions involving CICS, or the transactions of a particular server or CICS client connection.
|
Router#show txconn transaction transaction-id
|
Displays detailed status information for the specified CTRC transaction.
|
Router#show txconn route [server server-name]
|
Displays a list of CTRC routes to CICS for the current router or a particular server.
|
Router#show txconn destination
|
Displays a list of all the current router's CTRC destinations for CICS communications.
|
Router#show txconn destination destination-name
|
Displays detailed status information for the specified CTRC destination.
|
Router#clear txconn transaction transaction-id
|
Kills the specified CTRC transaction.
|
Router#clear txconn connection connection-id
|
Kills the specified CTRC connection to a CICS client and all associated transactions.
|
Router#clear txconn statistics [kind histogram | kind summary]
name {activeconnections | activetransactions | allocatetime |
clientreceived | clientsent | clientturnaround | dump |
hostreceived | hostresponse | hostsent | latency |
maxconnections | maxtransactions | totalconnections |
totaltransactions}
|
Clears specific statistics or all statistics related to CTRC communications with CICS.
|
Router#debug txconn {appc | config | data | event | tcp |
|
Enables debugging of CTRC communications with CICS.
|
|
Displays current status of debugging for the router.
|
Router#show txconn license or show dbconn license
|
Shows the status of the CTRC license.
|
Router#txconn ping destination-name
|
Verifies connectivity with a specific CICS destination.
|
Router#show txconn statistics [kind histogram | kind summary]
name {activeconnections | activetransactions | allocatetime |
clientreceived | clientsent | clientturnaround | dump |
hostreceived | hostresponse | hostsent | latency |
maxconnections | maxtransactions | totalconnections |
totaltransactions}
|
Displays statistics related to CTRC communications with CICS.
|
Monitoring and Maintaining CTRC Communications with DB2
Command
|
Purpose
|
Router#show dbconn server
|
Displays a summary of information about each CTRC server configured to communicate with DB2.
|
Router#show dbconn server server-name
|
Displays a detailed status of the specified CTRC server for DB2 communications.
|
Router#show dbconn connection
|
Displays the status of each CTRC connection to DB2.
|
Router#show dbconn connection connection-id
|
Displays a detailed status of the specified CTRC connection to DB2.
|
Router#show dbconn connection server server-name
|
Displays the status of CTRC connections to DB2 for the specified server.
|
Router#show dbconn connection user userid
|
Displays the status of a user connected to the CTRC for DB2 communications.
|
Router#show dbconn connection rdbname rdb-name
|
Displays a status of each connection to DB2 that matches the specified RDB name.
|
|
Displays information on all ports through which CTRC servers are accepting connections to DB2.
|
Router#show dbconn license or show txconn license
|
Displays the status of the CTRC license for both DB2 and CICS.
|
Router#clear dbconn connection connection-id
|
Breaks the specified client connection to the server.
|
Router#dbconn ping server-name [rdbname rdbname]
[userid userid] [password password]
|
Connects to the DB2 relational database on the IBM system for troubleshooting.
|
Router#debug dbconn {appc | config | drda | event | tcp | all}
|
Enables debugging of CTRC communications with DB2.
|
|
Displays current status of debugging for CTRC.
|
Router#show dbconn statistics
[chains|clientturnaround|connectionsdown|connectionsup|dump|
hostreceived|hostresponse|hostsent|latency|max connections]
|
Displays current statistics related to CTRC communications with DB2.
|
Router#clear dbconn statistics
[chains|clientturnaround|connectionsdown|connectionsup|dump|h
ostreceived|hostresponse|hostsent|latency|max connections]
|
Clears statistics related to CTRC communications with DB2.
|
Configuration Examples
The following sections provide CTRC configuration examples:
•CTRC Servers with IP Addresses Configuration Example (DB2)
•CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 1 (DB2)
•CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 2 (DB2)
•Server Selection by IP Addresses, RDB Names, and Ports Configuration Example (DB2)
•CTRC with CIP and DB2 on VTAM Configuration Example (DB2)
•CTRC Servers Using Token Ring to a LEN Configuration Example (CICS and DB2)
•CTRC Servers with IP Addresses, Routes, and Multi-Valued Destinations Configuration Example (CICS)
CTRC Servers with IP Addresses Configuration Example (DB2)
shows a CTRC configuration where the CTRC servers are configured to listen on port 446 (by default) for IP addresses specified for these servers in the router's configuration for CTRC. When an ODBC client attempts to make a connection to DB2, a CTRC server accepts the connection if the IP address specified in its configuration matches the IP address to which the client wants to connect.
In this illustration, Servers A and B are configured with IP addresses 172.0.10.2 and 172.0.45.3. Servers A and B accept any connection that targets their IP addresses. Server C accepts any connection that targets any IP address of router on the target port of 446 and an RDB name of IOWA.
Figure 4 CTRC Servers' Configuration with IP Addresses (for DB2 Communications)
The following are the commands that configure servers Server A, Server B, and Server C in the Cisco router:
dbconn server SERVERA ip-address 172.0.10.2 rdbname nevada
dbconn server SERVERB ip-address 172.0.45.3
dbconn server SERVERC rdbname iowa
CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 1 (DB2)
When a client request comes in for a server, and multiple servers are configured in the router, the three configured attributes of IP address, RDB name, and port determine which server is chosen for the connection. When a server is selected for a connection, the client remain
