Downloads |
Table Of Contents
Supported Standards, MIBs, and RFCs
Configuring SNA Switching Services
Configuring a CTRC Destination (CICS)
Configuring a CTRC Server (CICS)
Configuring a CTRC Route (CICS)
Configuring a CTRC Server (DB2)
Monitoring and Maintaining CTRC Communications with CICS
Monitoring and Maintaining CTRC Communications with DB2
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)
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:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The Cisco Transaction Connection (CTRC) software feature provides the following functionality:
•
•
•
•
•
•
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:
•
•
•
•
•
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:
•
•
(IBM publication SG24-5277)
See Chapter 15.4 (Configuration for VTAM & CICS TS for OS/390 when connecting with Microsoft SNA Server)•
(IBM publication SC33-1695)•
(IBM publication SC26-4783)•
(Open Group publication C812, ISBN 1-85912-295-7)Supported Platforms
•
•
Supported Standards, MIBs, and RFCs
MIBs
•
•
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
Perform the following tasks to configure CTRC, in the order that they are listed here:
•
•
•
•
•
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:
•
•
•
•
•
—Accessmethod: VTAM
—Protocol: APPC
—Attachsec: Verify•
•
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:
•
•
•
•
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)•
Driver = TCPIP
Drivername = CCLWNTIPConfiguring 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-15011-800-763-0050 in the US and Canada
1-510-528-2900 Worldwide, ask for extension 170
1-510-528-2986 FAXsales@starquest.com
Configuring SNA Switching Services
To configure basic SNA Switching Services, complete the following steps:
1
Defines a SNA Switching Services control point name.
2
Associates a SNA Switching Services port with an interface.
3
Associates a SNA Switching Services link with a SNA Switching Services port.1
1 If the partner node is initiating the connection, a link definition is not necessary. It is built dynamically when the partner node initiates the connection. Links are typically defined for upstream connectivity.
Note
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:
rlu rlu-name mode mode-nameSpecifies 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:
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:
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:
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:
Verifying SNA Connectivity
To verify that you have SNA connectivity between the router and each host system, complete the following task:
•
ping sna -m IBMRDB STARW.BUDDY
Verifying CTRC Configuration
To verify the CTRC configuration, complete the following tasks:
Step 1
Step 2
Router>show txconn destinationName Remote LU Mode Hits----------------- ------------------ ----------- --------CICSB CICSB IBMRDB 31GEN CICSB IBMRDB 50CICSC IBMRDB 51GUAVA GUAVA IBMRDB 0CICSC CICSC IBMRDB 7Step 3
Router>show txconn serverServer Port IP Address Dest State NumConn---------- ----- ------------ --------- --------- -------CICSB 1435 0.0.0.0 CICSB enabled 1CICSB&C 1436 0.0.0.0 GEN enabled 0CICSC 1434 0.0.0.0 CICSC enabled 0GUAVA 1437 0.0.0.0 GUAVA enabled 0If necessary, use the show txconn server server-name form of the command to display more information for an individual server.
Router>show txconn server CICSBserver: CICSBdestination: CICSBserver state: enabled (accepting connections)ip address: 0.0.0.0port: 1435client timeout: 0 (none)host timeout: 0 (none)window size: 4096 bytesfold program name: onnumber of connections: 1number of transactions: 2Step 4
Router>show txconn routeServer TranID Destination----------------- ----------------- ----------------CICSC <default> CICSCCICSB <default> CICSBCICSB&C <default> GENGUAVA <default> GUAVA<default> CPMI CICSCCICSB CPMI CICSBStep 5
Step 6
Router>show dbconn serverServer Port IPAddress RDBName State NumConnSERVERA 446 0.0.0.0 MATTY enabled 0SERVERB 446 0.0.0.0 SCU_DSNM enabled 4SERVERC 446 0.0.0.0 DSN4 enabled 0SERVERD 446 0.0.0.0 MKTG enabled 0SERVERE 446 0.0.0.0 ABBY enabled 6SERVERF 446 0.0.0.0 DB2510 enabled 0SERVERG 446 0.0.0.0 ELLE enabled 3SERVERH 446 0.0.0.0 SUNSET enabled 0SERVERI 446 0.0.0.0 NELL enabled 1SERVERJ 446 198.989.999.32 SAMPLE enabled 0SERVERK 446 0.0.0.0 DB2410 enabled 0SERVERL 446 0.0.0.0 SQLDS enabled 0SERVERM 446 0.0.0.0 STELLA enabled 1SERVERN 446 10.10.19.4 OAK enabled 2SERVERO 447 0.0.0.0 DB2510 enabled 0Router>show dbconn server BUDDYserver: BUDDYserver state: enabled (accepting connections)ip-address: 0.0.0.0port: 446rdbname: DB2510connection type: SNArlu: STARW.DSNV50mode: IBMRDBtpname: \x076DBidle-timeout: 0 (none)window-size: 4096 bytesdatabase server name: (unknown)database product id: (unknown)PEM: not configurednumber of connections: 0RDB server: activeWLM: inactive-enabledStep 7
Router>show txconn licenseCTRC is licensed for 4990 connections, 20 licensed connections in useThis is a permanent licenseRouter>show dbconn licenseCTRC is licensed for 1000 connections, no licensed connections in useExpires on 1-1-2001.Step 8
Router>txconn ping CICSBTrying CICSB CICSB:IBMRDBDestination CICSB successfully contacted!Elapsed time was 00:00:00.600Step 9
Router>dbconn ping BUDDY......RDB named DB2510 on database server successfully contacted!Elapsed time was 00:00:00Monitoring and Maintaining CTRCThis 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
Monitoring and Maintaining CTRC Communications with DB2
Configuration Examples
The following sections provide CTRC configuration examples:
•
•
•
•
•
•
•
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 nevadadbconn server SERVERB ip-address 172.0.45.3dbconn server SERVERC rdbname iowaCTRC 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 remains associated with that server for the duration of that connection. The APPC attributes configured for that server are used to connect to the IBM system. If a server is unconfigured while active connections exist, the active connections with that server will break.
Only one CTRC server can be configured with a unique combination of IP address, port, and RDB name. If a situation arises where multiple servers in a router meet the criteria for accepting a client connection, the CTRC server that meets the most specific criteria accepts the connection. For example, in Servers A and B are listening on port 446 for client connections that match their IP address of 161.55.122.80. Server A is configured to accept RDB name NEVADA and Server B is configured to accept any RDB name. A client connecting to port 446 for RDB name NEVADA matches the criteria for both servers. In this situation, Server A is selected to accept the connection because its configuration includes a specific RDB name NEVADA as compared to Server B whose configuration accepts any RDB name.
Figure 5 CTRC Server Configuration with IP Address and RDB Name Defined
CTRC Servers with IP Addresses, RDB Names, and Ports Configuration Example 2 (DB2)
The IP address and port specified for a server in a router's configuration also determines which server accepts a connection. For example, Server C is configured to listen on any local IP address on port 446 and RDB name IOWA. Server D is configured to listen for IP address 145.56.180.34 on port 446 and RDB name IOWA. When a client attempts to connect to IP address 145.56.180.34 on port 446 for RDB name IOWA, both servers meet the criteria in accepting the connection. In this case, CTRC selects a connection based on the IP address first, then the port, and finally, the RDB name.
Server Selection by IP Addresses, RDB Names, and Ports Configuration Example (DB2)
If multiple servers in a router meet the criteria for accepting a client connection, the CTRC server that meets the most specific criteria accepts the connection. In , the Cisco router contains four server configurations. All four servers listen for client connections on port 446 by default. Both Servers A and B are configured with the same IP address, 161.55.122.80. Servers A and C are configured to accept RDB name NEVADA. Servers B and D are configured to accept any RDB name.
If a client connects to IP address 161.55.122.80 on port 446 and sends RDB name NEVADA in the DRDA data stream, all four servers match the criteria for accepting the client connection. However, Server A will be selected to accept the connection because it meets the most specific criteria for IP address, RDB name, and port. If Server A was not configured, Server B would be the second choice because it meets the criteria for the IP address and port. The IP address specified in a server always has precedence when matching a connection to a server.
Figure 6 CTRC Server Configurations with IP Addresses, RDB Names, and Default Port
The following is the configuration for Servers A, B, C, and D in the Cisco router:
hostname routera!enable password alliedbconn server SERVERA ip-address 161.55.122.80 rdbname NEVADAdbconn server SERVERB ip-address 161.55.122.80dbconn server SERVERC rdbname NEVADAdbconn server SERVERDCTRC with CIP and DB2 on VTAM Configuration Example (DB2)
illustrates a Cisco router with a Channel Interface Processor (CIP) that is configured with CTRC. The CIP is networked and connected to VTAM on the mainframe. DB2 is configured on VTAM.
Figure 7 Cisco Router with CIP and Connection to DB2 on VTAM
The configuration in uses router commands to configure SNA Switching Services over CIP and CSNA via SRB. The following three pages of this document show the configuration in more detail. Note that the source-bridge ring-group of 100 matches the source bridge of 10 2 100 for interface Channel 13/2 to enable SNA Switching Services to run over SRB. In addition, the destination LAN address used by the snasw link station BUDDY corresponds to the virtual MAC address used by the adapter for Channel 13/2.
In the VTAM host definitions, the variable CONNTYPE=APPN is optional but recommended if you use APPN in your SNA environment. If CP to CP is set to YES and CONNTYPE is set to APPN, this configuration enables the Cisco router to establish CP-to-CP sessions with VTAM. By allowing CP-to-CP sessions, you gain the benefit of APPN's dynamic features such as the availability of directory and topology for locating resources and calculating optimal routes.
In this example, the router smoke is attached to the host BUDDY using a CIP processor.
Note
VTAM Partner PU and LU Definition
SMOKEPB PU ADDR=01, XIDBLK=05D, XIDNUM=00501, XCPNAME=SMOKE, XANS=CONT, XDISCNT=NO, XIRETRY=NO, XISTATUS=ACTIVE, XPUTYPE=2, XSECNET=NO, XMAXDATA=521, XMAXOUT=7, XMAXPATH=1, XUSSTAB=USSS, XMODETAB=ISTINCLM, XDLOGMOD=IBMRDB, XCONNTYPE=APPN***SMOKE LU LOCADDR=00, INDEPENDENT LU XDLOGMOD=IBMRDBVTAM APPLID for DB2
DSNV510 APPL APPC=YES, X00006012AUTH=ACQ, X00007012AUTOSES=1, X00008012DMINWNL=1024, X00009012DMINWNR=1024, X00009112DSESLIM=2048, X00009212EAS=65535, X00009312MODETAB=ISTINCLM, X00009412SECACPT=CONV, X00009512SRBEXIT=YES, X00009612VERIFY=NONE, X00009712VPACING=1, X00009812SYNCLVL=SYNCPT, X00009912ATNLOSS=ALL 00010012Cisco IOS Configuration
!source-bridge ring-group 100!interface Ethernet2/1mac-address 4200.0000.0501ip address 198.147.235.11 255.255.255.128no ip directed-broadcastno ip mroute-cache!interface Channel3/0ip address 192.168.1.1 255.255.255.0no ip directed-broadcastno keepalivechannel-protocol S4claw 0100 22 192.168.1.2 BUDDY CIPTCP TCPIP TCPIPcsna 0100 20!interface Channel3/2no ip addressno ip directed-broadcastno keepalivelan TokenRing 1source-bridge 10 2 100adapter 1 4000.0123.9999!interface Virtual-TokenRing0mac-address 4000.2222.3333source-bridge 50 1 100source-bridge spanning!snasw cpname STARW.SMOKEsnasw port SRB Virtual-TokenRing0snasw link BUDDY port SRB rmac 4000.0123.9999!dbconn server DB2BUDD rdbname DB2510 rlu STARW.DSNV510 mode IBMRDB!ip default-gateway 198.147.235.12ip classlessCTRC Servers Using Token Ring to a LEN Configuration Example
(CICS and DB2)This section provides a configuration example for a router named smoke, beginning with the VTAM definition for the router, which is the same as for the previous example.
The router is connected to the host via Token Ring. The control point name of the host is BUDDY; its Token Ring MAC address is 4000.0200.0448.
The host is configured as a Subarea Node (APPN LEN); if a host is configured as an APPN Network Node, the snasw location statements are unnecessary.
shows a CTRC configuration for communication with DB2 and CICS.
Figure 8 CTRC Configuration for Communication with DB2 and CICS
VTAM Partner PU and LU Definition
RouterPB PU ADDR=01, XIDBLK=05D, XIDNUM=00501, XCPNAME=SMOKE, XANS=CONT, XDISCNT=NO, XIRETRY=NO, XISTATUS=ACTIVE, XPUTYPE=2, XSECNET=NO, XMAXDATA=521, XMAXOUT=7, XMAXPATH=1, XUSSTAB=USSS, XMODETAB=ISTINCLM, XDLOGMOD=IBMRDB, XCONNTYPE=APPN***SMOKE LU LOCADDR=00, INDEPENDENT LU XDLOGMOD=IBMRDBVTAM APPLID for DB2
DSNV510 APPL APPC=YES, X00006012AUTH=ACQ, X00007012AUTOSES=1, X00008012DMINWNL=1024, X00009012DMINWNR=1024, X00009112DSESLIM=2048, X00009212EAS=65535, X00009312MODETAB=ISTINCLM, X00009412SECACPT=CONV, X00009512SRBEXIT=YES, X00009612VERIFY=NONE, X00009712VPACING=1, X00009812SYNCLVL=SYNCPT, X00009912ATNLOSS=ALL 00010012VTAM APPLID for CICS
CICSAPPL VBUILD TYPE=APPL 00010001******************************************************** 00010000* CICS APPL DEFINITION FOR LU62 CLIENT/SERVER SUPPORT 00020000******************************************************** 00030000CICSB APPL AUTH=(ACQ,SPO,PASS,VPACE), XMODETAB=ISTINCLM, XVPACING=0,EAS=100,PARSESS=YES, XAPPC=NO, XSONSCIP=YES, XACBNAME=STARCICSCisco IOS Configuration
!source-bridge ring-group 100!!interface TokenRing0/1mac-address 4000.1111.0501ip address 198.147.235.196 255.255.255.224no ip directed-broadcastno ip mroute-cacheearly-token-releasering-speed 16multiring all!interface Ethernet2/1mac-address 4200.0000.0501ip address 198.147.235.11 255.255.255.128no ip directed-broadcastno ip mroute-cache!!snasw cpname STARW.SMOKEsnasw port TR0 TokenRing0/1snasw link BUDDY port TR0 rmac 4000.0200.0448snasw location STARW.DSNV510 owning-cp STARW.BUDDYsnasw location STARW.CICSB owning-cp STARW.BUDDY!dbconn server DB2BUDD rdbname DB2510 rlu STARW.DSNV510 mode IBMRDB!txconn destination DESTBUDD rlu STARW.CICSB mode IBMRDBtxconn server CICSBUDD destination DESTBUDD port 1435ip default-gateway 198.147.235.12ip classlessCTRC Servers with IP Addresses, Routes, and Multi-Valued Destinations Configuration Example (CICS)
shows a CTRC configuration that includes multiple CTRC servers, routes, default and non-default ports, and one multi-valued CTRC destination.
Figure 9 CTRC Configuration with IP Addresses, Routes, and Multiple CICS Destinations
In , a single router is configured to run three CTRC servers for communication with CICS. These txconn servers are shown as CTRC server A, CTRC server C, and CTRC server D. Server A listens on the default port, 1435, for all of the router's IP addresses. Server C listens on port 1436 for IP address 191.9.200.8. Server D listens on port 1436 for IP address 191.9.200.37.
Server A is configured to communicate with two logical destinations. If a client communication has the value of TEST for its transaction ID (TRANID), server A sends it to logical Destination B. This is a multi-valued destination that allows communication with two CICS systems, system B (with RLU B and mode B) and system X (with RLU X and mode X). Transactions are allocated to these two destination systems on a round-robin basis.
If a client communication for server A does not have a value of TEST for TRANID, server A sends it to Destination A, which corresponds to CICS system A (with RLU A and mode A).
Server C is also configured to communicate with two logical destinations. If server C receives a client communication that has the value of TEST2 for its transaction ID, server C sends it to logical Destination D, which corresponds to CICS system D (with RLU D and mode D). Server C sends client communications with other transaction IDs to logical Destination C (CICS system C, with RLU C and mode C).
Server D is configured to send client communications to logical Destination D. This example illustrates the following CTRC configuration principles:
•
•
•
•
•
Command Reference
This section documents all non-debug commands used with the CTRC feature. Some of these commands were previously used with the CDBC feature, which CTRC replaces. Other commands are new with the introduction of CTRC.
•
•
•
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
clear dbconn connection
To break a client connection to DB2, use the clear dbconn connection privileged EXEC command.
clear dbconn connection connection-id
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following example shows the client connection 786A7C being cleared:
clear dbconn connection 786A7CConnection 786A7C clearedRelated Commands
clear txconn connection
To clear a CTRC connection to a CICS client and all associated transactions, use the clear txconn connection privileged EXEC command.
clear txconn connection connection-id
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the specified CICS client connection number 62146088 and all its transactions:
clear txconn connection 62146088% Connection 62146088 clearedRelated Commands
clear txconn transaction
Kills a specific CICS transaction.
show txconn connection
Displays information about CTRC connections to CICS.
clear txconn statistics
To clear a specified CTRC statistic concerning communications with CICS, or to clear all such statistics, use the clear txconn statistics privileged EXEC command.
clear txconn statistics {allocatetime | clientreceived | clientsent | clientturnaround | every | hostreceived | hostresponse | hostsent | maxconnections | maxtransactions | totalconnections | totaltransactions}
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the stored statistics for the number of bytes the current router has received from CICS clients:
clear txconn statistics clientreceivedRelated Commands
show txconn statistics
Displays statistics related to CTRC communications with CICS.
clear dbconn statistics
To clear all CTRC statistics concerning communications with DB2, use the clear debconn statistics privileged EXEC command.
clear dbconn statistics {chains | clientturnaround | connectionsdown| connectionsup|dump| hostreceived|hostresponse|hostsent|latency|maxconnections}
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the stored statistics for the number of bytes the current router has received from DB2 clients:
clear dbconn statistics clientreceivedRelated Commands
show dbconn statistics
Displays statistics related to CTRC communications with DB2.
clear txconn transaction
To terminate a specified CICS transaction, use the clear txconn transaction privileged EXEC command. This command terminates the conversation with the host and returns DEALLOC_ABEND_PROG to the client.
clear txconn transaction transaction-id
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the CICS transaction number 621FC8E0
clear txconn transaction 621FC8E0% Transaction 621FC8E0 clearedRelated Commands
dbconn license
To configure client licenses for CTRC connections to DB2 or CICS, use the dbconn license global configuration command. To remove the licenses, use the no form of this command.
dbconn license license-key [connections licensed-connections] [expiration-date yyyymmdd]
no dbconn licenseSyntax Description
Defaults
If the number of licensed connections is not specified, the license key must be generated for an unlimited number of licensed connections. If the expiration date is not specified, the license key must be permanent.
Command Modes
Global configuration
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Usage Guidelines
Licenses are required for all CTRC installations. For testing and evaluation purposes, unlicensed CTRC installations allow you to establish two connections to DB2 or CICS. Licenses are shared between CTRC connections to DB2 and CTRC connections to CICS. If you have already configured licenses for CTRC connections to CICS, you do not need to configure licenses for DB2, and vice versa.
Examples
The following example shows a permanent CTRC license for unlimited connections being configured:
dbconn license 8C09A496420BAF020BFF74B8A2FF24D2Related Commands
dbconn pem
To configure password expiration management (PEM) support for connections to DB2, use the dbconn pem global configuration command. To remove PEM support, use the no form of this command.
dbconn pem server server-name rlu rlu-name mode mode-name [tpname tp-name]
no dbconn pem server server-nameSyntax Description
Defaults
If tp-name is not specified, the default value is \x06301 (0x06F3F0F1 in EBCDIC).
Command Modes
Global configuration
Command History
Examples
The following example shows the configuration of PEM support:
dbconn pem GAZELLE rlu STARW.GAZELLE mode #INTERRelated Commands
show dbconn server
Displays information about CTRC servers for DB2 communications
dbconn ping
To determine whether or not CTRC servers are successfully connecting to DB2 host databases, use the dbconn ping EXEC command.
dbconn ping server-name [user user-id] [password password] [rdbname rdbname]
Syntax Description
Defaults
If no user ID is specified, the ping connection is made without APPC security. The DB2 system's security settings determine whether or not the ping can succeed.
If no rdbname is specified, the relational database name configured for the server is used.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Usage Guidelines
This command can be used for CTRC servers that communicate with DB2 over either SNA or TCP/IP (dbconn servers and dbconn tcpservers).
Examples
The following example shows an attempt to verify the connection to the default database for the CTRC server canopus:
dbconn ping canopusRDB named NEVADA on database server CANOPUS successfully contacted!Database server product id is QSQ03020, DB2 for OS/400 V3R2Elapsed time was 00:00:00Related Commands
dbconn server
To configure a CTRC server for communications to DB2, use the dbconn server global configuration command. To disable the server and remove its configuration, use the no form of this command.
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}]
no dbconn server server-nameSyntax Description
Defaults
If you do not specify an IP address, the current server can handle DB2 connectivity requests sent to any IP address on the local router.
If you do not specify a port number, the current server uses the default value of 446.
If you do not specify an rdbname, the server is configured to serve any remote database.
If you do not specify a remote LU, the default is the configured server name which is set to uppercase and truncated to eight characters. An RLU need not be qualified with a NETID. If you omit the NET ID, the NET ID of the router's SNA Switching Services control point is used to fully qualify the LU name.
If you do not specify an APPC mode, the default value is #INTER. If you specify a mode that does not already exist, CTRC will create it.
If you do not specify an APPC transaction program name, the default value is the architected DRDA TP name \x076DB.
If you do not specify an idle timeout, client connections can continue regardless of how long they have been idle.
If you do not specify a TCP receive window size, the default value is 4 K (4096 bytes).
Command Modes
Global configuration
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Usage Guidelines
You can configure more than one CTRC server per router for communications with DB2 or CICS. There is no limit on the number of CTRC servers. For each DB2 database system in your network, you can configure a CTRC server in the router configuration. CTRC dbconn servers that are configured on the same router can share a port. CTRC txconn servers should use a different port.
Examples
The following example shows the configuration of a CTRC server that will communicate with DB2:
dbconn server coffee rdbname COFFEE rlu PARIS.COFFEE idle-timeout 20 window-size 16Related Commands
dbconn tcpserver
To configure a CTRC server to communicate with IP-enabled DB2 databases, use the dbconn tcpserver global configuration command. To disable such a server and remove its configuration, use the no form of this command.
dbconn tcpserver server-name [ip ip-address] [port port-num] [rdbname rdbname]
remote-ip remote-ip-address [remote-port remote-port] [idle-timeout time-in-minutes]
[window-size size-in-bytes]no dbconn tcpserver server-name
Syntax Description
Defaults
If you do not specify an IP address for the tcpserver, it can receive requests on any IP address configured for the router.
If you do not specify a port for the tcpserver, the default port is 446.
If you do not specify a remote database name for the DB2 system, the tcpserver can communicate with any rdbname.
If you do not specify a port for the remote DB2 system, the tcpserver uses the default value of 446.
If you do not specify an idle timeout period, the default value is zero for no timeout.
If you do not specify a TCP/IP receive window size, the default value is 4096 bytes (4 K).
Command Modes
Global configuration
Command History
Usage Guidelines
Configure a separate tcpserver for each DB2 system IP address. A dbconn server and a dbconn tcpserver can share the same port.
Examples
The following example shows the configuration of a tcpserver:
Router(config)#dbconn tcpserver TCPSERVER ip 0.0.0.0 port 446 rdbname GAZELLEremote-ip 123.456.1.2 remote-port 446Related Commands
show dbconn connection
To display the status of CTRC connections to DB2, use the show dbconn connection EXEC command.
show dbconn connection [connection-id | server server-name | user user-id |
rdbname rdb-name]Syntax Description
Defaults
If you do not specify any arguments, this command displays information for all CTRC connections to DB2 on the current router.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following is sample output from the show dbconn connection command:
Router>show dbconn connectionID Server Userid ClientIPAddress Connect Idle6127E428 SERVERA ALLIE 198.999.989.36 00:01:26 00:01:126127D34C SERVERB BRIAN 198.999.989.84 00:00:48 00:00:41The following is sample output from the show dbconn connection command for a specified connection:
Router>show dbconn connection 62586780connection id: 62586780connection state: activeserver: QAMELTCPrdbname: MELBAuserid: QAUSERclient name: QAMELBAlocal ip-address: 198.147.235.2local port: 500client ip-address: 198.147.235.88client port: 4258connect time: 00:53:27idle time: 00:00:04 (client)bytes received from client: 30478bytes received from host: 318222client: licensed StarSQLdescribes significant fields shown in the display.
Related Commands
show dbconn license
To display the status of CTRC licenses for DB2 communications, use the show dbconn license EXEC command.
show dbconn license
Syntax Description
This command has no arguments or keywords
Defaults
None.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Usage Guidelines
This command produces the same results as show txconn license because licenses are shared.
Examples
The following is sample output from the show dbconn license command for a router that is using a temporary license key:
Router>show dbconn licenseCTRC is licensed for 1000 connections, no licensed connections in useExpires on 1-1-2001.Related Commands
show dbconn ports
To display information about ports that CTRC is using for communications to DB2, use the show dbconn ports EXEC command.
show dbconn ports
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following is sample output from the show dbconn ports command:
Router>show dbconn portsPort State446 listening447 listeningdescribes significant fields shown in the display.
Table 2 Show Database Connection Ports Field Descriptions
Port
Port number.
State
Listening or disabled status.
Related Commands
show dbconn server
To display information about CTRC servers configured for DB2 communications, use the show dbconn server EXEC command.
show dbconn server [server-name]
Syntax Description
Defaults
If no server name is specified, this command displays information for all CTRC servers configured for DB2 communications on the current router.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following is sample output from the show dbconn server command:
Router>show dbconn serverServer Port IPAddress RDBName State NumConnSERVERA 446 0.0.0.0 MATTY enabled 0SERVERB 446 0.0.0.0 SCU_DSNM enabled 4SERVERC 446 0.0.0.0 DSN4 enabled 0SERVERD 446 0.0.0.0 MKTG enabled 0SERVERE 446 0.0.0.0 ABBY enabled 6SERVERF 446 0.0.0.0 DB2510 enabled 0SERVERG 446 0.0.0.0 ELLE enabled 3SERVERH 446 0.0.0.0 SUNSET enabled 0SERVERI 446 0.0.0.0 NELL enabled 1SERVERJ 446 198.989.999.32 SAMPLE enabled 0SERVERK 446 0.0.0.0 DB2410 enabled 0SERVERL 446 0.0.0.0 SQLDS enabled 0SERVERM 446 0.0.0.0 STELLA enabled 1SERVERN 446 10.10.19.4 OAK enabled 2SERVERO 447 0.0.0.0 DB2510 enabled 0The following is sample output from the show dbconn server command where the database server BUDDY is specified:
Router>show dbconn server BUDDYserver: BUDDYserver state: enabled (accepting connections)ip-address: 0.0.0.0port: 446rdbname: DB2510connection type: SNArlu: STARW.DSNV50mode: IBMRDBtpname: \x076DBidle-timeout: 0 (none)window-size: 4096 bytesdatabase server name: (unknown)database product id: (unknown)PEM: not configurednumber of connections: 0RDB server: activeWLM: inactive-enableddescribes significant fields shown in the display.
Related Commands
show dbconn connection
Displays information about CTRC connections to DB2.
show dbconn ports
Displays information about CTRC ports used for DB2 communications.
show dbconn statistics
To show all CTRC statistics concerning communications with DB2, use the show debconn statistics privileged EXEC command.
show dbconn statistics {chains | clientturnaround | connectionsdown| connectionsup|dump| hostreceived|hostresponse|hostsent|latency|maxconnections}
Syntax Description
Defaults
None.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the stored statistics for the number of bytes the current router has received from DB2 clients:
clear dbconn statistics clientreceivedRelated Commands
show dbconn statistics
Displays statistics related to CTRC communications with DB2.
show dbconn wlm
To display information about CTRC servers configured for DB2 communications using Workload Manager, use the show dbconn wlm EXEC command.
show dbconn wlm [server-name]
Syntax Description
Defaults
If no server name is specified, this command displays information for all CTRC servers configured for DB2 communications with Workload Manager on the current router.
Command Modes
EXEC
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following is sample output from the show dbconn wlm command:
IP Port Weight Hits198.147.235.2 500 1 0198.147.235.2 501 2 0198.147.235.2 502 3 0Related Commands
show dbconn connection
Displays information about CTRC connections to DB2.
show dbconn ports
Displays information about CTRC ports used for DB2 communications.
show txconn connection
To display a list of all of the router's CTRC connections to CICS clients, a list of a specified CTRC server's connections to CICS clients, or detailed status information for a specific CTRC connection to a CICS client, use the show txconn connection EXEC command.
show txconn connection [connection-id | server server-name]
Syntax Description
Defaults
If neither connection-id nor server-name are specified, a list of all of the current router's CTRC connections to CICS clients is displayed.
Command Modes
EXEC
Command History
Examples
The following example displays information about a CICS client connections for the current router:
Router>show txconn connectionServer ConnID State #Transact. IP Address Port Bytes---------------- ---------- --------- ---------- --------------- ----- --------CICSB 6241464C receiving 2 198.147.235.88 1365 2.89KAMELIA 625443BC receiving 0 198.147.235.88 1371 15.60KThe following example displays information about a specified CICS client connection:
Router>show txconn connection 6241464Cconnection: 6241464Cserver: CICSBstate: receivingtransactions: 2ip address: 198.147.235.88port: 1365total transactions: 20connect timestamp: 06:04:26idle time: 06:17:34total bytes received: 2963total bytes sent: 28121 (2.89K)idle timeout: 0 (none)describes significant fields shown in the display.
Related Commands
show txconn destination
To display a list of all of the current router's CICS destinations for CTRC, or to display detailed status information for a specified CTRC CICS destination, use the show txconn destination EXEC command.
show txconn destination [destination-name]
Syntax Description
destination-name
(Optional) CTRC destination for which to display detailed status information. A destination is defined by a unique remote LU and mode pair.
Defaults
If destination-name is omitted, displays a list of all CTRC destinations for the current router.
Command Modes
EXEC
Command History
Examples
The following examples show the CTRC destinations for CICS communications that are available on the current router and information specifically about the destination GEN:
Router>show txconn destinationName Remote LU Mode Hits----------------- ------------------ ----------- --------CICSB CICSB IBMRDB 31GEN CICSB IBMRDB 50CICSC IBMRDB 51GUAVA GUAVA IBMRDB 0CICSC CICSC IBMRDB 7Router>show txconn destination GENName Remote LU Mode Hits----------------- ------------------ ----------- --------GEN CICSB IBMRDB 50CICSC IBMRDB 51The HITS column displays the number of times the router has routed transactions or pings to each destination since the last time the router was started up.
Related Commands
show txconn license
To show the status of licenses used for CTRC, use the show txconn license EXEC command.
show txconn license
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC
Command History
Usage Guidelines
This command produces the same result as the show dbconn license command because CTRC licenses are shared between DB2 connections and CICS conversations.
Examples
The following example shows license information for CICS communications being displayed on the current router:
Router>show txconn licenseCTRC is licensed for 4990 connections, 20 licensed connections in useThis is a permanent licenseRelated Commands
show txconn route
To display a list of all CTRC routes defined for specified CICS transaction IDs, or to display a particular CTRC server's routes to CICS, use the show txconn route EXEC command.
show txconn route [server server-name]
Syntax Description
server server-name
(Optional) Server for which you wish to display routing information. If not specified, a list of all CICS communications routes for CTRC servers on the current router is displayed.
Defaults
If server-name is not specified, a list of all CICS communications routes for CTRC servers on the current router is displayed.
Command Modes
EXEC
Command History
Examples
The following examples show information about all the CTRC routes to CICS that are available on the current router and information about the route for CTRC server CICSB&C. 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.
Router>show txconn routeServer TranID Destination----------------- ----------------- ----------------CICSC <default> CICSCCICSB <default> CICSBCICSB&C <default> GENGUAVA <default> GUAVA<default> CPMI CICSCCICSB CPMI CICSBRouter>show txconn route CICSB&CServer TranID Destination----------------- ----------------- ----------------CICSB&C <default> GENRelated Commands
show txconn server
To display information about the current router's CTRC servers for CICS communications, or to display detailed status information for a single CTRC server, use the show txconn server EXEC command.
show txconn server [server-name]
Syntax Description
server-name
(Optional) CTRC server for which to display detailed status information. When omitted, a list of CTRC servers is displayed.
Defaults
When server-name is not specified, a list of the current router's CTRC servers that communicate with CICS is displayed.
Command Modes
EXEC
Command History
Examples
The following examples show summary information about the CTRC servers for CICS communications that are available on the current router and more detailed information about the CTRC server CICSB:
Router>show txconn serverServer Port IP Address Dest State NumConn--------- ----- ------------ ---------- -------- -------AMELIA 1436 0.0.0.0 AMELIA enabled 0CICSB 1444 0.0.0.0 CICSB enabled 0CICSC 1434 0.0.0.0 CICSC enabled 0TEST 1446 0.0.0.0 CICSC enabled 0Router>show txconn server TESTserver: TESTdestination: CICSBserver state: enabled (accepting connections)ip address: 0.0.0.0port: 1437client timeout: 0 (none)host timeout: 0 (none)window size: 4096 bytesfold program name: onccsid: 273number of connections: 1number of transactions: 2describes significant fields shown in the display.
Related Commands
show txconn statistics
To display information about the current router's CTRC communications with CICS, use the show txconn statistics EXEC command.
show txconn statistics [kind histogram | kind summary] name {activeconnections | activetransactions | allocatetime | clientreceived | clientsent | clientturnaround | dump | hostreceived | hostresponse | hostsent | latency | maxconnections | maxtransactions | totalconnections | totaltransactions}
Syntax Description
Defaults
If the kind of statistics display is not specified, summary is used.
Command Modes
EXEC
Command History
Examples
The following examples show histogram and summary displays of the clientreceived statistic.
Router>show txconn statistics kind histogram name clientreceivedNumber of Bytes Received from Clients18.82MB ^^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ | ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^| | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | |9.41MB | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | ^| | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | || | | | | | | | | | | | | | | | | | | | | | | |0 - - - - - - - - - - - - - - - - - - - - - - - -7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 *PM AMRouter>show txconn statistics name clientreceivedNumber of Bytes Received from Clientsyesterday yesterday today----hour--- ----AM---- ----PM---- ----AM----12:00-12:59 19728481 1972729901:00-01:59 19732711 1972729902:00-02:59 19722903 1972738203:00-03:59 19728398 1973169504:00-04:59 19729497 1972620005:00-05:59 19730596 1973389306:00-06:59 19722986 1970861607:00-07:59 0 19734992 8736034 *08:00-08:59 19726283 1972510109:00-09:59 19725101 1972839810:00-10:59 19726283 1972738211:00-11:59 19729497 1973059624-hour total: 453731589 (excludes hour in progress *)Related Commands
show txconn transaction
To display a list of all the current router's CTRC transactions with CICS, a specified CTRC server's transactions, or a specified CICS client connection's transactions, use the show txconn transaction EXEC command.
show txconn transaction [server server-name | connection connection-id | transaction-id]
Syntax Description
Defaults
If no arguments are specified, all the CICS transactions for the current router are listed.
Command Modes
EXEC
Command History
Examples
The following two examples display general information about CICS transactions being handled by the current router and detailed information about a specified CICS transaction, respectively:
Router>show txconn transactionTransaction ID Server Conn ID State TP Name User ID-------------- ---------- ---------- --------- -------- --------6246ECD8 QATIM 62494598 receiving CPMI QAUSER62476188 QATIM 62494598 receiving CPMI QAUSER623130D4 QATIM 62494598 receiving CPMI QAUSER6229E88C QATIM 62494598 receiving CPMI QAUSERRouter>show txconn transaction 6246ECD8transaction: 6246ECD8server: QATIMconnection id: 62494598state: receivingtp name: CPMIuser id: QAUSERsession RU address (OAF+DAF): 6idle time: 1788--- Transaction Totals ---number of transactions executed: 1number of bytes received from client: 1099number of bytes received from host: 0describes significant fields shown in the display.
Related Commands
txconn destination
To configure a CTRC destination, use the txconn destination global configuration command. To remove configuration for a txconn destination, use the no form of this command.
txconn destination destination-name rlu rlu-name mode mode-name
no txconn destination destination-name [rlu rlu-name mode mode-name]Syntax Description
Defaults
No defaults exist for the txconn destination command. However, the remote LU name of the host and the APPC mode name are optional for the no form of the command. If you omit them, CTRC removes the configuration for all routing targets defined for the destination. If you use rlu rlu-name mode mode-name to specify a particular routing target within a destination that has multiple targets, the configuration is removed only for the specified target.
Command Modes
Global configuration
Command History
Examples
The following example shows the CTRC destination newdest being defined on the current router:
txconn destination newdest rlu CICSB mode IBMRDBA second pair of rlu and mode values could be assigned to this same logical destination, to allow load sharing between the two destination CICS systems:
txconn destination newdest rlu CICSC mode IBMRDBRelated Commands
show snasw mode
Displays information about predefined SNA Switching Services modes.
show txconn destination
Displays information about CICS destinations for CTRC.
txconn license
To license a Cisco router for CTRC communications with CICS or DB2, use the txconn license global configuration command. To remove the license, use the no form of this command.
txconn license license-key [connections licensed-connections] [expiration-date yyyymmdd]
no txconn licenseSyntax Description
Defaults
If the number of licensed connections is not specified, the license key must be generated for an unlimited number of licensed connections. If the expiration date is not specified, the license key must be permanent.
Command Modes
Global configuration
Command History
Usage Guidelines
Licenses are required for all CTRC installations. Within CTRC, a common pool of node-linked licenses is used for communications with both DB2 and CICS. Therefore, if you have already configured licenses for CTRC connections to DB2, you do not need to configure licenses for CICS. The txconn license command provides exactly the same functionality as dbconn license.
For testing and evaluation purposes, unlicensed CTRC installations allow you to establish two connections to DB2 or two conversations with CICS.
Examples
The following example shows a CTRC license being configured for communications with CICS:
txconn license 8C09A496420BAF020BFF74B8A2FF24D2Related Commands
txconn ping
To test communications between the CTRC router and a CTRC destination (a host defined by a pair of RLU and mode values), use the txconn ping EXEC command.
txconn ping destination-name
Syntax Description
Defaults
None.
Command Modes
EXEC
Command History
Examples
The following example shows communications being tested between the current router and the CTRC destination GEN. Note that GEN is a destination that has two RLU-Mode pairs defined, and that the txconn ping command automatically tests connections to both:
txconn ping GENTrying GEN CICSC:IBMRDBDestination GEN successfully contacted!Elapsed time was 00:00:01.001Trying GEN CICSB:IBMRDBDestination GEN successfully contacted!Elapsed time was 00:00:01.001
Elapsed time is noted in hours, minutes, seconds, and milliseconds.Related Commands
txconn route
To configure a CTRC route that will transmit specified transactions to a particular CICS destination, use the txconn route global configuration command. To remove the configuration of a CTRC route, use the no form of this command.
txconn route [server server-name] tranid transaction-id destination destination-name
no txconn route [server server-name] tranid transaction-idSyntax Description
Defaults
None.
Command Modes
Global configuration
Command History
Examples
The following example shows a CTRC route to destination GEN being defined on the current router for transaction ID PNG1:
txconn route server newsvr tranid PNG1 destination GENRelated Commands
txconn server
To configure a CTRC server for communications with CICS, use the txconn server global configuration command. To disable a CTRC server, use the no form of this command.
txconn server server-name destination destination-name [ccsid number]
[ipaddress ip-address] [port port-number] [client-timeout minutes] [host-timeout minutes] [window-size bytes] [fold on|off]
no txconn server server-nameSyntax Description
Defaults
If the CTRC server's IP address is not configured, the server accepts connections for any IP address that is configured for the router.
If the port number is not configured, the server listens on port 1435.
If you do not specify a client timeout, CICS client connections can continue regardless of how long they have been idle.
If you do not specify a host timeout, host connections can continue regardless of how long they have been idle.
If you do not specify a TCP/IP window size, the default value is 4096 bytes (4 K).
Command Modes
Global configuration
Command History
Usage Guidelines
You can configure more than one CTRC server per router for communications with DB2 or CICS. There is no limit on the number of CTRC servers. However, be sure that CTRC txconn servers and CTRC dbconn servers are configured to use different ports, and that each txconn server is configured to use a unique combination of port number and IP address, or a unique port number with no IP address.
Examples
The following example shows the CTRC server newsvr being defined on the current router:
txconn server newsvr destination GEN port 1438Related Commands
show txconn destination
Displays information about CICS destinations for CTRC.
show txconn server
Displays information about CTRC servers that communicate with CICS.
Debug Commands
This section documents debugging commands used with the CTRC feature. Some of these commands were previously used with the Cisco Database Connection feature (CDBC), which CTRC replaces. Other commands are new with the introduction of CTRC.
debug dbconn all
Use the debug dbconn all privileged EXEC command to turn on all debug flags for CTRC communications with DB2. These flags include appc, config, drda, event, and tcp. Use the no form of this command to disable all debugging output.
[no] debug dbconn all
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
See the examples provided for the debug dbconn appc, debug dbconn config, debug dbconn drda, debug dbconn event, and debug dbconn tcp commands.
Related Commands
debug dbconn appc
Use the debug dbconn privileged EXEC command to display APPC-related trace or error messages for communications with DB2. Use the no form of this command to disable debugging output.
[no] debug dbconn appc
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following example shows APPC debugging output using the debug dbconn appc command:
01:18:05: DBCONN-APPC-622ADF38: Verb block =01:18:05: DBCONN-APPC-622ADF38: 0001 0200 0300 0000 0400 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 0000 00FC 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 0000 0000 0840 0007 0000 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 7BC9 D5E3 C5D9 4040 07F6 C4C2 4040 404001:18:05: DBCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-622ADF38: 4040 4040 4040 4040 0000 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-622ADF38: 00E2 E3C1 D9E6 4BC7 C1E9 C5D3 D3C5 404001:18:05: DBCONN-APPC-622ADF38: 4040 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: Verb block =01:18:05: DBCONN-APPC-621E5730: 0001 0200 0300 0000 0400 0000 0000 000001:18:05: DBCONN-APPC-621E5730: 0000 00FD 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: 0000 0000 0840 0007 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: C9C2 D4D9 C4C2 4040 07F6 C4C2 4040 404001:18:05: DBCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: DBCONN-APPC-621E5730: 4040 4040 4040 4040 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: DBCONN-APPC-621E5730: 00E2 E3C1 D9E6 4BE2 E3C5 D3D3 C140 404001:18:05: DBCONN-APPC-621E5730: 4040 0000 0000 0000 0000 0000Related Commands
debug dbconn config
Use the debug dbconn config privileged EXEC command to display trace or error messages for CTRC configuration and control blocks for DB2 communications. Use the no form of this command to disable debugging output.
[no] debug dbconn config
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following example shows output from the debug dbconn config command when SNA Switching Services is not available:
01:21:05: DBCONN-CONFIG: server 6231CA1C takes connection 621E12CC01:21:05: %CTRC-3-SNASWNOTSTARTED: SNASW is not started -- unable to connect toremote database.01:21:05: %CTRC-3-SNASWNOTSTARTED: SNASW is not started -- unable to connect toremote database.01:21:05: DBCONN-CONFIG: server 6231BA6C releases connection 62138E5001:21:05: DBCONN-CONFIG: deleting connection 62138E5001:21:05: DBCONN-CONFIG: server 6231CA1C releases connection 621E12CC01:21:05: DBCONN-CONFIG: deleting connection 621E12CC01:21:05: DBCONN-CONFIG: listen 6231BB88 received ping reply - ping failed.01:21:05: DBCONN-CONFIG: listen 62324FE8 received ping reply - ping failed.01:21:19: %CTRC-3-SNASWSTOPPED: SNASW was stopped -- existing connections have been closed.01:21:20: DBCONN-CONFIG: listen 62171740 received alarm msgRelated Commands
debug dbconn drda
Use the debug dbconn drda privileged EXEC command to display error messages and stream traces for DRDA. Use the no form of this command to disable debugging output.
[no] debug dbconn drda
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following example displays output from the debug dbconn drda command:
Router#debug dbconn drda*Jun 30 16:09:32.363: DBCONN-DRDA-62008300: DSS X'006CD0410001', length 108, in chain, REQDSS, correlator 1*Jun 30 16:09:32.363: DBCONN-DRDA-62008300: OBJECT X'00661041', length 98, code point X'1041'*Jun 30 16:09:32.363: DBCONN-DRDA-62008300: OBJECT X'0020115E' in COLLECTION X'1041', length 28, code point X'115E'*Jun 30 16:09:32.363: DBCONN-DRDA-62008300: OBJECT X'000C116D' in COLLECTION X'1041', length 8, code point X'116D'*Jun 30 16:09:32.363: DBCONN-DRDA-62008300: OBJECT X'0013115A' in COLLECTION X'1041', length 15, code point X'115A' (skipping...)Related Commands
debug dbconn event
Use the debug dbconn event privileged EXEC command to display trace or error messages for CTRC events related to DB2 communications. Use the no form of this command to disable debugging output.
[no] debug dbconn event
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following examples display output from the debug dbconn event command in a variety of situations. A normal trace for the debug dbconn event displays as follows:
Router#debug dbconn eventDBCONN-EVENT: Dispatch to 60FD6C00, from 0, msg 60F754CC, msgid 6468 'dh',buffer 0.DBCONN-EVENT: [*] Post to 61134240(cn), from 60EC5470(tc), msg 611419E4,msgid 0x6372 'cr', buffer 612BF68C.DBCONN-EVENT: Flush events called for pto 61182742, pfrom 61239837.DBCONN-EVENT: Event discarded: to 61182742 (cn), from 61239837(ap), msg61339273, msgid 0x6372 'cr' buffer 0.DBCONN-EVENT: == Send to 1234abcd, from 22938acd, msg 72618394, msgid0x6372 'cr', buffer 0.If the following messages are displayed, contact Cisco technical support personnel:
DBCONN-TCPFSM-1234abcd: Cannot occur in state 2 on input 6363 ('cc')DBCONN-APPCFSM-1234abcd: Cannot occur in state 3 on input 6363 ('cc')Related Commands
debug dbconn tcp
Use the debug dbconn tcp privileged EXEC command to display error messages and traces for TCP. Use the no form of this command to disable debugging output.
[no] debug dbconn tcp
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the dbconn subsystem.
Command History
11.3(2)T
This command was introduced.
12.0(5)XN
Command moved from CDBC feature to CTRC feature.
Examples
The following example displays output from the debug dbconn tcp command:
Router#debug dbconn tcpDBCONN-TCP-63528473: tcpdriver_passive_open returned NULLDBCONN-TCP-63528473: (no memory) tcp_reset(63829482) returns 4DBCONN-TCP: tcp_accept(74625348,&error) returns tcb 63829482, error 4DBCONN-TCP: (no memory) tcp_reset(63829482) returns 4DBCONN-TCP-63528473: (open) tcp_create returns 63829482, error = 4DBCONN-TCP-63528473: tcb_connect(63829482,1.2.3.4,2010) returns 4DBCONN-TCP-63528473: (open error) tcp_reset(63829482) returns 4DBCONN-TCP-63528473: tcp_create returns 63829482, error = 4DBCONN-TCP-63528473: tcb_bind(63829482,0.0.0.0,2001) returns 4DBCONN-TCP-63528473: tcp_listen(63829482,,) returns 4DBCONN-TCP-63528473: (errors) Calling tcp_close (63829482)Related Commands
debug txconn all
Use the debug txconn all privileged EXEC command to turn on all debug flags for CTRC communications with CICS. These flags include appc, config, data, event, tcp, and timer. Use the no form of this command to disable all debugging output.
[no] debug txconn all
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows the immediate output of the debug txconn all command. For examples of specific debugging messages, see the examples provided for the debug txconn appc, debug txconn config, debug txconn data, debug txconn event, debug txconn tcp, and debug txconn timer commands.
Router#debug txconn allAll possible TXConn debugging has been turned onRelated Commands
debug txconn appc
Use the debug txconn privileged EXEC command to display APPC-related trace or error messages for communications with CICS. Use the no form of this command to disable debugging output.
[no] debug txconn appc
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows APPC debugging output from the debug txconn appc command:
01:18:05: TXCONN-APPC-622ADF38: Verb block =01:18:05: TXCONN-APPC-622ADF38: 0001 0200 0300 0000 0400 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 0000 00FC 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 0000 0000 0840 0007 0000 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 7BC9 D5E3 C5D9 4040 07F6 C4C2 4040 404001:18:05: TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-622ADF38: 4040 4040 4040 4040 0000 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-622ADF38: 00E2 E3C1 D9E6 4BC7 C1E9 C5D3 D3C5 404001:18:05: TXCONN-APPC-622ADF38: 4040 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: Verb block =01:18:05: TXCONN-APPC-621E5730: 0001 0200 0300 0000 0400 0000 0000 000001:18:05: TXCONN-APPC-621E5730: 0000 00FD 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: 0000 0000 0840 0007 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: C9C2 D4D9 C4C2 4040 07F6 C4C2 4040 404001:18:05: TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 404001:18:05: TXCONN-APPC-621E5730: 4040 4040 4040 4040 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: 0000 0000 0000 0000 0000 0000 0000 000001:18:05: TXCONN-APPC-621E5730: 00E2 E3C1 D9E6 4BE2 E3C5 D3D3 C140 404001:18:05: TXCONN-APPC-621E5730: 4040 0000 0000 0000 0000 0000Related Commands
debug txconn config
Use the debug txconn config privileged EXEC command to display trace or error messages for CTRC configuration and control blocks for CICS communications. Use the no form of this command to disable debugging output.
[no] debug txconn config
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows output for the debug dbconn config command:
Router#debug txconn config22:11:37: TXCONN-CONFIG: deleting transaction 61FCE41422:11:37: TXCONN-CONFIG: deleting connection 61FB5CB022:11:37: TXCONN-CONFIG: server 62105D6C releases connection 61FB5CB022:11:44: TXCONN-CONFIG: new connection 61FB64A022:11:44: TXCONN-CONFIG: server 6210CEB4 takes connection 61FB64A022:11:44: TXCONN-CONFIG: new transaction 61E44B9C22:11:48: TXCONN-CONFIG: deleting transaction 61E44B9C22:11:53: TXCONN-CONFIG: new transaction 61E44B9C22:11:54: TXCONN-CONFIG: deleting transaction 61E44B9CRelated Commands
debug txconn data
To display a hexadecimal dump of CICS client and host data being handled by CTRC, plus information about certain CTRC internal operations, use the debug txconn data privileged EXEC command. Use the no form of this command to disable the debugging output.
[no] debug txconn data
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows selected output from the debug txconn data command when a connection is established, data is received from the client via TCP/IP, data is sent to the client, and then the connection is closed.
Router#debug txconn dataTXConn DATA debugging is on00:04:50: TXConn(62197464) Created00:04:50: TXConn(62197464) State(0) MsgID(0) -> nextState(1)00:04:50: TXConn(62197464) Client->0000 003A 0000 0002 000B 90A000:04:50: TXConn(62197464) Received LL 58 for session(0 0 2).00:06:27: TXConn(62197464) Client<-0000 0036 0000 0003 000B 8001 0707 086400:06:53: TXConn(62175024) DeletedThe following lines show output when data is sent to the host:
00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) LL(58) FMH5(0) CEBI(0)00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) State(0) MsgID(7844) -> nextState(1)00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) conversationType(mapped) syncLevel(1) sec(0)00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) TPName CCIN00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) apDataLength(32) GDSID(12FF)00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) ->Host 0000 0008 03F4 F3F7 0000 0008 0401 0000The following lines show output when data is received from the host:
00:05:01: TXTrans(id:62197910 conn:62197464 addr:2) <-Host 0092 12FF 0000 000C 0102 0000 0000 0002The following lines show CTRC generating an FMH7 error message indicating that a CICS transaction has failed at the host or has been cleared by a router administrator:
00:06:27: TXTrans(id:6219853C conn:62197464 addr:3) Generating FMH7.00:06:27: %TXCONN-3-TXEXCEPTION: Error occurred from transaction 3 of client 157.151.241.10 connected to server CICSC, exception type is 9The following line shows CTRC responding to an FMH7 error message sent by the CICS client program:
00:07:11: TXTrans(id:62197910 conn:62197464 addr:2) Generating FMH7 +RSP.Related Commands
debug txconn event
Use the debug txconn event privileged EXEC command to display trace or error messages for CTRC events related to CICS communications. Use the no form of this command to disable debugging output.
[no] debug txconn event
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows output for the debug txconn event command:
Router#debug txconn eventTXConn event debugging is onRouter#22:15:08: TXCONN-EVENT: [*] Post to 62146464(cn), from 6211E744(tc), msg61FC6170, msgid 0x6372 'cr', buffer 6211289C.22:15:08: TXCONN-EVENT: Dispatch to 62146464, from 6211E744, msg 61FC6170,msgid 6372 'cr', buffer 6211289C.22:15:08: TXCONN-EVENT: [*] Post to 61E44BA0(sn), from 62146464(cn), msg621164D0, msgid 0x7844 'xD', buffer 0.22:15:08: TXCONN-EVENT: [*] Post to 6211E744(tc), from 62146464(cn), msg61FC6170, msgid 0x6347 'cG', buffer 0.22:15:08: TXCONN-EVENT: Dispatch to 61E44BA0, from 62146464, msg 621164D0,msgid 7844 'xD', buffer 0.22:15:08: TXCONN-EVENT: Dispatch to 6211E744, from 62146464, msg 61FC6170,msgid 6347 'cG', buffer 0.22:15:08: TXCONN-EVENT: [*] Post to 62146464(cn), from 6211E744(tc), msg61FC6170, msgid 0x6372 'cr', buffer 6211289C.22:15:08: TXCONN-EVENT: Dispatch to 62146464, from 6211E744, msg 61FC6170,msgid 6372 'cr', buffer 6211289C.22:15:08: TXCONN-EVENT: [*] Post to 61E44BA0(sn), from 62146464(cn), msg61FBFBF4, msgid 0x7844 'xD', buffer 0.22:15:08: TXCONN-EVENT: [*] Post to 6211E744(tc), from 62146464(cn), msg61FC6170, msgid 0x6347 'cG', buffer 0.22:15:08: TXCONN-EVENT: Dispatch to 61E44BA0, from 62146464, msg 61FBFBF4,msgid 7844 'xD', buffer 0.22:15:08: TXCONN-EVENT: [*] Post to 61FC6394(ap), from 61E44BA0(sn), msg621164D0, msgid 0x634F 'cO', buffer 0.22:15:08: TXCONN-EVENT: Dispatch to 6211E744, from 62146464, msg 61FC6170,msgid 6347 'cG', buffer 0.Related Commands
debug txconn tcp
Use the debug txconn tcp privileged EXEC command to display error messages and traces for TCP. Use the no form of this command to disable debugging output.
[no] debug txconn tcp
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example displays output from the debug txconn tcp command:
Router#debug txconn tcpTXCONN-TCP-63528473: tcpdriver_passive_open returned NULLTXCONN-TCP-63528473: (no memory) tcp_reset(63829482) returns 4TXCONN-TCP: tcp_accept(74625348,&error) returns tcb 63829482, error 4TXCONN-TCP: (no memory) tcp_reset(63829482) returns 4TXCONN-TCP-63528473: (open) tcp_create returns 63829482, error = 4TXCONN-TCP-63528473: tcb_connect(63829482,1.2.3.4,2010) returns 4TXCONN-TCP-63528473: (open error) tcp_reset(63829482) returns 4TXCONN-TCP-63528473: tcp_create returns 63829482, error = 4TXCONN-TCP-63528473: tcb_bind(63829482,0.0.0.0,2001) returns 4TXCONN-TCP-63528473: tcp_listen(63829482,,) returns 4TXCONN-TCP-63528473: (errors) Calling tcp_close (63829482)Related Commands
debug txconn timer
To display performance information regarding CTRC communications with CICS, use the debug txconn timer privileged EXEC command. Use the no form of this command to disable the debugging output.
[no] debug txconn timer
Syntax Description
This command has no arguments or keywords.
Defaults
By default, debugging is not enabled for the txconn subsystem.
Command History
Examples
The following example shows turnaround time and host response time in milliseconds for a CICS transaction requested through CTRC. Turnaround time is measured from when CTRC receives the first request packet for the transaction until CTRC sends the last response packet of the transaction to the client. Host response time is measured from when CTRC sends the last request packet for a transaction to the host until CTRC receives the first response packet from the host for that transaction.
Router#debug txconn timerTXConn timer debugging is on00:04:14: TXTrans(id:622F4350 conn:62175024 addr:1) Turnaround Time = 4536(msec) HostResponseTime = 120(msec)Related Commands
Error Messages
Error Message%CTRC-3-APPCVERB: Unexpected APPC error: opcode [hex], primary code [hex], secondary code [hex]Explanation An unexpected APPC error occurred. CTRC uses APPC API calls to SNASw to communicate with the remote host. Opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.
Recommended Action This message usually indicates a problem in the SNA network. Use the dbconn ping command to test connectivity to a remote database server. Use the txconn ping command to test connectivity to a remote CICS system. If the ping fails, check the status of the SNA link to the remote host with the show snasw link command. If the link is active then stop and start the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call the Cisco TAC and provide the representative with the gathered information. If possible, also provide the output of the debug dbconn appc command (for a database connection) or the debug txconn appc command (for a CICS connection), and an SNA line trace between the router and the remote host for the period during which this message appeared.
Error Message%CTRC-3-SNASWNOTSTARTED: SNASW is not started -- unable to connect to remote host.Explanation A client connected to a CTRC server, but CTRC was unable to connect out to the remote host because SNASw is not started. CTRC uses SNASw to connect to the remote host. You must start SNASw before CTRC clients attempt to connect.
Recommended Action Start SNASw and retry the client connection.
Error Message%CTRC-3-SNASWSTOPPED: SNASW was stopped -- existing connections have been closed.Explanation SNASw was stopped while CTRC connections were open. Stopping SNASw caused all open SNA connections to the remote host to be lost. As a result, all client connections were disconnected. You should not stop SNASw while there are open CTRC connections.
Recommended Action Restart SNASw. Disconnected clients must reconnect.
Error Message%TXCONN-3-BADLICENSEKEY: Bad license key configured for Transaction Connection.Explanation The license key configured with the txconn license configuration command is not valid.
Recommended Action Check that the license key was entered correctly in the txconn license configuration command. Refer to the txconn feature documentation for information on how to obtain a valid license key.
Error Message%TXCONN-3-BADMODE: Unknown mode '[chars]' configured for server [chars]Explanation The mode configured for the txconn server was rejected by the remote host.
Recommended Action Contact your SNA network administrator to determine the correct name of the mode to use to connect to the remote host.
Error Message%TXCONN-3-BADRLU: Bad remote LU '[chars]' configured for server [chars]Explanation The remote LU configured for the txconn server is incorrect.
Recommended Action Contact your SNA network administrator to determine the correct name of the remote LU for the remote host. Be sure to check that the SNA network name is correct as well as the LU name.
Error Message%TXCONN-3-INVALIDTRANS: Bad Transaction ID, flushing out request for client [int] connected server [chars], killing connection.Explanation Bad input stream.
Recommended Action This is an informational message. No action is required.
Error Message%TXCONN-3-NOSESSION: Out of resource, cannot create transaction for client [int] connected server [chars], killing connection.Explanation The router is out of memory.
Recommended Action This is an informational message. No action is required.
Error Message%TXCONN-5-CONNIDLETIMEOUT: Client [int] connected to server [chars] has timed out after %TE.Explanation The client was idle for too long, and the idle timeout configured for the txconn server expired.
Recommended Action This is an informational message only. No action is required.
Error Message%TXCONN-5-SECFAIL: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The userid or password passed in by the client were rejected by the remote host.
Recommended Action This is an informational message only. No action is required.
Error Message%TXCONN-5-TARGETDOWN: CICS server [chars] has become unavailable. Recovery is in progress.Explanation A CICS server for a configured destination has become unavailable. All client connections to this server will be rejected until it becomes available again.
Recommended Action This is an informational message only. No action is required.
Error Message%TXCONN-5-TARGETUP: CICS server [chars] is now available.Explanation A CICS server that was previously unavailable has become available. All client connections to this server will now be accepted.
Recommended Action This is an informational message only. No action is required.
Error Message%TXCONN-5-TRANSIDLETIMEOUT: Transaction [hex] of Client [int] connected to server [chars] has timed out after %TE.Explanation The transaction was idle for too long, and the idle timeout configured for the txconn server expired.
Recommended Action This is an informational message only. No action is required.
Error Message%TXCONN-3-TXEXCEPTION: Error occurred from transaction [hex] of client [int] connected to server [chars], exception type is [dec]Explanation An unexpected transaction error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call the Cisco TAC, and provide the representative with the gathered information. If possible, also provide the output of the debug txconn data command and an SNA line trace between the router and the remote database server for the period during which this message appeared.
Error Message%TXCONN-3-UNEXPECTEDREQ: Unexpected client data, flushing out the request for client [int] connected server [chars].Explanation Bad input stream.
Recommended Action This is an informational message. No action is required.
Glossary
"See cross references". For example: Advanced Program-to-Program Communications—See APPC.
APPC—Advanced Program-to-Program Communications. An implementation of the SNA/SDLC LU6.2 protocol that allows interconnected systems to communicate and share the processing of programs.
APPN—Advanced Peer-to-Peer Networking. An extension to SNA featuring greater distributed network control that avoids critical hierarchical dependencies, thereby isolating the effects of single points of failure. APPN also features dynamic exchange of network topology information to foster ease of connection, reconfiguration, and adaptive route selection, dynamic definition of network resources, and automated resource registration and directory lookup.
CDBC—Cisco Database Connection. Prior to the introduction of CTRC, CDBC provided ODBC client applications with access to data in DB2 databases.
CEDA—A CICS-supplied transaction that lets you update the CICS system definition or define resources for your CICS system while the system is running.
CICS—IBM's Customer Information Control System. An online transaction monitoring system. Available versions include CICS for OS/390, CICS/ESA, CICS/400, and TXSeries.
CTRC—Cisco Transaction Connection. Router software that provides ODBC client applications with connectivity to DB2 databases, and that provides CICS client applications with connectivity to CICS transaction monitoring systems.
DB2—IBM relational database management system. Available versions include DB2 for MVS/ESA, DB2 for OS/400, DB2 Parallel Edition, and DB2 for VSE and VM.
DDM—Distributed Data Management Architecture. An IBM architected data management interface used for data interchange among like or unlike systems. DRDA is based on DDM, describing the content of and restrictions on DDM flows related to relational database management.
DRDA—Distributed Relational Database Architecture. A connection protocol for distributed relational database processing that is used by IBM's relational database products.
ECI—external call interface. Allows a non-CICS client program to call a CICS transaction. The client application communicates with the program in the CICS server using a COMMAREA.
EPI—extended presentation interface. Interface suitable for distributed applications that call CICS transactions that were originally accessed via 3270 terminals.
ISC—intersystem communication protocol. Used to interconnect CICS with other CICS and IMS regions. ISC protocol is also used by IBM Common Client and Microsoft COMTI client software to communicate with CICS and IMS. ISC protocol supports transaction routing, function shipping, and distributed program link. Of these three functions, CTRC implements transaction routing and distributed program link.
ODBC—Open Database Connectivity. 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—Systems Network Architecture. A large, complex, feature-rich network architecture developed by IBM.
SNA Switching Services—Cisco software that replaces Cisco's APPN offering. SNA Switching Services is an enhancement to the original IBM SNA architecture. It handles session establishment between peer nodes, dynamic transparent route calculation, and traffic prioritization for APPC traffic.
TCP/IP—Transmission Control Protocol/Internet Protocol. Common name for the suite of protocols developed by the U.S. Department of Defense in the 1970s to support the construction of worldwide internetworks. TCP and IP are the two best-known protocols in the suite.
Workload Manager —The purpose of workload management is to balance the available system resources to meet the demands of S/390 subsystems work managers such as DB2 in response to incoming work requests.
