Feedback
Table Of Contents
Cisco Transaction Connection Commands
Cisco Transaction Connection Commands
Use the commands in this chapter to configure and monitor the Cisco Transaction Connection (CTRC) feature. Refer to the Cisco IOS Debug Command Reference for information about using debugging commands, including those available for CTRC. For CTRC configuration tasks and examples, refer to the "Configuring Cisco Transaction Connection" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide.
clear dbconn connection
To break a client connection to DB2, use the clear dbconn connection privileged EXEC command, specifying the ID of the connection you want to terminate.
clear dbconn connection connection-id
Syntax Description
Defaults
No default behavior or values.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example shows the client connection 786A7C being cleared:
clear dbconn connection 786A7CConnection 786A7C clearedRelated Commands
clear dbconn statistic
To clear a specific statistic or all CTRC statistics concerning communications with DB2, use the clear dbconn statistic privileged EXEC command.
clear dbconn statistic {chains | clientturnaround | connectionsdown | connectionsup | every | hostreceived | hostresponse | hostsent | maxconnections}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example clears the stored statistics for the number of bytes the current router has received from DB2 hosts:
clear dbconn statistic hostreceivedRelated 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
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example clears the specified CICS client connection number 62146088 and all its transactions:
clear txconn connection 62146088% Connection 62146088 clearedRelated Commands
Terminates a specified CICS transaction.
Displays a list of all of the CTRC connections of the router to CICS clients.
clear txconn statistic
To clear a specific statistic or all CTRC statistics concerning communications with CICS, use the clear txconn statistic privileged EXEC command.
clear txconn statistic {allocatetime | clientreceived | clientsent | clientturnaround | every | hostreceived | hostresponse | hostsent | maxconnections | maxtransactions | totalconnections | totaltransactions}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example clears the stored statistics for the number of bytes the current router has received from CICS clients:
clear txconn statistic clientreceivedRelated Commands
Displays information about the CTRC communications of the current router with CICS.
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
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 in privileged EXEC mode.
dbconn license license-key connections licensed-connections expiration-date yyyymmdd
no dbconn license
Syntax Description
Defaults
If the number of licensed connections is not specified, the license key must allow an unlimited number of licensed connections. If the expiration date is not specified, the license key must be for a permanent license.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 two conversations to CICS, or one to each. One license key is used for both CICS and DB2 communications, so you can use either the dbconn license command or the txconn license command to configure the CTRC router.
Examples
The following example shows the configuration of a CTRC router with a license that allows up to 4000 connections until January 1, 2005:
dbconn license 3C09A051320BAF020BFF45B3A2FF21D2 connections 4000 expiration-date 20050101Related 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-name
Syntax Description
Defaults
If tp-name is not specified, the default value is \x06301 (0x06F3F0F1 in EBCDIC).
Command Modes
Global configuration
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example shows the configuration of PEM support on a CTRC server named DB2BUDD:
dbconn pem DB2BUDD rlu MVSLU01 mode #INTERRelated Commands
dbconn ping
To determine whether CTRC servers are successfully connecting to DB2 host databases, use the dbconn ping EXEC command.
dbconn ping server-name [userid 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 the ping can succeed.
If no rdbname is specified, the relational database name configured for the CTRC 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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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). There is not a no form this command.
Examples
The following example illustrates using dbconn ping to verify the connection to the default database for the CTRC server BUDDY:
dbconn ping BUDDYRDB named DB2510 on database server BUDDY 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 process for APPC communications with 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 [idle-timeout minutes] [ipaddress ip-address] [keepalive attempts number] [keepalive interval seconds] [mode mode] [port port-number] [rdbname rdbname] [rlu remote-lu] [tpname tp-name] [window-size bytes] [wlm {off | on}]
no dbconn server server-name
Syntax Description
Defaults
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 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 keepalive attempt or a keepalive interval, the server makes up to three attempts to send an acknowledgment message every 120 seconds.
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 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 that is set to uppercase and truncated to eight characters. An RLU need not be qualified with a NET ID. 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 transaction program name, the default value is the architected DRDA TP name \x076DB.
If you do not specify a TCP receive window size, the default value is 4096 bytes.
The Workload Manager load balancing default is "inactive-enabled."
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. For each DB2 database system in your network, you can configure a CTRC server in the router configuration. Servers that are configured on the same router can share a port. CTRC txconn servers should use a different port.
Set keepalive attempts or keepalive interval to zero (0) to disable the keepalive messages.
Examples
The following example shows configuring a CTRC server named BUDDY to manage communications to a DB2 database named DB2510, using the IBMRDB APPC mode to allocate the conversation, and attempting five acknowledgment messages every 300 seconds:
dbconn server BUDDY rdbname DB2510 rlu STARW.BUDDY idle-timeout 20 keepalive attempts 5 keepalive interval 300 mode IBMRDBRelated Commands
dbconn tcpserver
To configure a CTRC server process to communicate with IP-enabled DB2 databases, use the dbconn tcpserver global configuration command. To disable a server and remove its configuration, use the no form of this command.
dbconn tcpserver server-name [idle-timeout minutes] [ip ip-address] [keepalive attempts number] [keepalive interval seconds] [port port-num] [rdbname rdbname] remote-hostname remote-hostname | remote-ip remote-ip-address [remote-keepalive attempts number] [remote-keepalive interval seconds] [remote-port remote-port] [window-size bytes] [wlm {off | on}]
no dbconn tcpserver server-name
Syntax Description
Defaults
If you do not specify an idle timeout period, the default value is zero for no timeout.
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 keepalive attempt or a keepalive interval, the server makes three attempts to send an acknowledgment message to the client every 120 seconds. If you do not specify a remote-keepalive attempt or a remote-keepalive interval, the server makes three attempts to send an acknowledgment message to the host ever 120 seconds.
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 a TCP/IP receive window size, the default value is 4096 bytes.
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 configuring a tcpserver named BUDDTCP to manage connections to a DB2 database named DB2510, attempting up to five keepalive messages to the client and to the host every 300 seconds:
dbconn tcpserver BUDDTCP keepalive attempts 5 keepalive interval 300 port 446 rdbname DB2510 remote-ip 198.147.235.39 remote-keepalive attempts 5 remote-keepalive interval 300 remote-port 446Related Commands
Determines whether or not CTRC servers are successfully connecting to DB2 host databases.
Displays information about CTRC servers configured for DB2 communications.
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 | userid 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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 BUDDY 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 6127D34Cconnection id: 6127D34Cconnection state: activeserver: BUDDYrdbname: DB2510userid: (none)client name:local ip-address: 198.147.235.2local port: 500client ip-address: 198.999.989.84client port: 4258connect time: 00:53:27idle time: 00:00:04 (client)bytes received from client: 30478bytes received from host: 318222client: licensed StarSQLTable 4 describes 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
No default behavior or values.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
This command produces the same results as the show txconn license command because CTRC licenses are shared between DB2 connections and CICS conversations.
Examples
The following is sample output for a CTRC router that is configured to allow up to 1000 connections until January 1, 2005:
Router> show dbconn licenseCTRC is licensed for 1000 connections, 756 connections in useExpires on 1-1-2005.Related Commands
Configures client licenses for CTRC connections to DB2 or CICS.
Displays the status of licenses used for CTRC.
Licenses a Cisco router for CTRC communications with CICS or DB2.
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
No default behavior or values.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following is sample output from the show dbconn ports command:
Router> show dbconn portsPort State446 listening447 listeningTable 5 describes significant fields shown in the display.
Table 5 show dbconn 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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 56SERVERB 446 0.0.0.0 SCU_DSNM enabled 24SERVERC 446 0.0.0.0 DSN4 enabled 19SERVERD 446 0.0.0.0 MKTG enabled 130SERVERE 446 0.0.0.0 ABBY enabled 76SERVERF 446 0.0.0.0 DB2510 enabled 320SERVERG 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 12SERVERK 446 0.0.0.0 DB2410 enabled 154SERVERL 446 0.0.0.0 SQLDS enabled 50SERVERM 446 0.0.0.0 STELLA disabled 0SERVERN 446 10.10.19.4 OAK enabled 2SERVERO 447 0.0.0.0 DB2510 enabled 237BUDDY 446 0.0.0.0 DB2510 enabled 756The following is sample output from the show dbconn server command where the 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.DSNV510mode: 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-enabledTable 6 describes significant fields shown in the display.
Related Commands
Displays the status of CTRC connections to DB2.
Displays information about CTRC ports used for DB2 communications.
show dbconn statistic
To display all CTRC statistics concerning communications with DB2, use the show dbconn statistic privileged EXEC command.
show dbconn statistic [kind {histogram | summary}] name {chains | clientturnaround | connectionsdown | connectionsup | dump | hostreceived | hostresponse | hostsent | latency | maxconnections}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Summary statistics are displayed by time period, where:
•
[24] indicates statistics for the hour currently in progress.
•
•
In the following example, at 3 a.m. the statistics for the current period are moved to [02], overwriting the old statistics for that period, and [24] is reset to 0:
At 2:59 a.m.:
[24]=228[00]=217 [01]=352 [02]=209 [03]=313 [04]=156 . . .Mid-1 am 1-2 a.m. 2-3 a.m. 3-4 a.m. 4-5 a.m. . . .02-24-2001 02-24-2001 02-24-2001 02-23-2001 02-23-2001 . . .At 3 a.m.:
[24]=0[00]=217 [01]=352 [02]=228 [03]=313 [04]=156 . . .Mid-1 am 1-2 a.m. 2-3 a.m. 3-4 a.m. 4-5 a.m. . . .02-24-2001 02-24-2001 02-24-2001 02-24-2001 02-23-2001 . . .Examples
The following command displays all the statistics relating to communications with DB2:
Router# show dbconn statistic name dumpThe following example shows the connectionsup statistic in histogram format.
Router# show dbconn statistic kind histogram name connectionsupNumber of Connections Created800 ^^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ | ^ ^| | | | || | | | || | | | | | | || | | | | | | | | ^| | | | | | | | | || | | | | | | | | |400 | | | | | | | | | || | | | | | | | | || | | | | | | | | | || | | | | | | | | | || | | | | | | | | | || | | | | | | | | | | || | | | | | | | | | | || | | | | | | | | | | |- - - - - - - - - - - - - - - - - - - - - - - -12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 *PM AMThe following example shows the connectionsup statistic in the default summary format.
Router# show dbconn statistic name connectionsupNumber of Connections Createdyesterday today today----hour--- ----PM---- ----AM---- ----PM----12:00-12:59 0 0 536 *01:00-01:59 726 002:00-02:59 718 003:00-03:59 597 004:00-04:59 549 005:00-05:59 607 006:00-06:59 298 007:00-07:59 162 508:00-08:59 3 70409:00-09:59 0 81710:00-10:59 0 72511:00-11:59 0 59824-hour total: 5636 (excludes hour in progress *)Related Commands
show dbconn wlm
To display information about a CTRC server that is configured to use Workload Manager for DB2 communications, use the show dbconn wlm EXEC command.
show dbconn wlm server-name
Syntax Description
server-name
Name of the CTRC server that is configured to use Workload Manager to manage DB2 communications.
Defaults
No default behavior or values.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
Following is sample output from the show dbconn wlm command for a TCP/IP-enabled DB2 server:
IP Port Weight Hits198.147.235.2 500 251 90198.147.235.2 501 182 64198.147.235.2 502 29 0Following is sample output from the show dbconn wlm command for a DB2 server in an SNA network:
RLU Weight HitsSTARW.DSNV510 500 230As each connection is established with DB2, CTRC obtains information from the Workload Manager subsystem to calculate the best route to use for the next connection. The fastest and most available connection is assigned the highest weight, and the Hits column shows how many times CTRC has used that route.
Related Commands
Displays the status of CTRC connections to DB2.
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 20 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)Table 7 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, a list of all CTRC destinations for the current router is displayed.
Command Modes
EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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
No default behavior or values.
Command Modes
EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 is sample output for a CTRC router that is licensed to allow up to 4990 connections for an unlimited time period:
Router> show txconn licenseCTRC is licensed for 4990 connections, 2850 licensed connections in useThis is a permanent licenseRelated Commands
Configures CTRC licenses for connections to DB2 or CICS.
Displays the status of CTRC licenses for DB2 communications.
Configures CTRC licenses for connections to CICS or DB2.
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 a value for the server-name argument is not specified, a list of all CICS communications routes for CTRC servers on the current router is displayed.
Command Modes
EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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> entry in the SERVER column indicates a global route that is used by all txconn servers on the router. A <default> entry 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 a value for the server-name argument is not specified, a list of the current router's CTRC servers that communicate with CICS is displayed.
Command Modes
EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example shows summary information about the CTRC servers for CICS communications that are available on the current router:
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 0You can specify the name of a particular txconn server to display detailed information about it, as shown in the following example for the CTRC server named CICSB.
Router> show txconn server CICSBserver: CICSBdestination: CICSBserver state: enabled (accepting connections)ip address: 0.0.0.0port: 1444client timeout: 0 (none)host timeout: 1 minutewindow size: 4096 bytesfold program name: onccsid: 273number of connections: 178number of transactions: 20client type: cicsIf this example had been for a Microsoft COMTI client, the client type value would be comti rather than cics. Table 8 describes the significant information shown for each server, in the order it appears.
Related Commands
show txconn statistic
To display information about the current router's CTRC communications with CICS, use the show txconn statistic EXEC command.
show txconn statistic [kind {histogram | 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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Summary statistics are displayed by time period, where:
•
•
•
In the following example, at 3 a.m. the statistics for the current period are moved to [02], overwriting the old statistics for that period, and [24] is reset to 0:
At 2:59 a.m.:
[24]=228[00]=217 [01]=352 [02]=209 [03]=313 [04]=156 . . .Mid-1 am 1-2 a.m. 2-3 a.m. 3-4 a.m. 4-5 a.m. . . .02-24-2001 02-24-2001 02-24-2001 02-23-2001 02-23-2001 . . .At 3 a.m.:
[24]=0[00]=217 [01]=352 [02]=228 [03]=313 [04]=156 . . .Mid-1 am 1-2 a.m. 2-3 a.m. 3-4 a.m. 4-5 a.m. . . .02-24-2001 02-24-2001 02-24-2001 02-24-2001 02-23-2001 . . .Examples
The following examples show histogram and summary displays of the clientreceived statistic.
Router> show txconn statistic 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 statistic 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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example shows information about all the CICS transactions being handled by the current router:
Router> show txconn transactionTransaction ID Server Conn ID State TP Name User ID-------------- ---------- ---------- --------- -------- --------6246ECD8 CICSB 62494598 receiving CPMI QAUSER62476188 CICSB 62494598 receiving CPMI QAUSER623130D4 CICSB 62494598 receiving CPMI QAUSER6229E88C CICSB 62494598 receiving CPMI QAUSERYou can specify a particular transaction ID to display details about it, as shown in the following example:
Router> show txconn transaction 6246ECD8transaction: 6246ECD8server: CICSBconnection id: 62494598state: receivingtp name: CPMIuser id:session 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: 0Table 9 describes the significant information shown for each transaction in the order it appears in the display.
.
Related Commands
txconn destination
To configure a CTRC destination, use the txconn destination global configuration command. To remove the 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
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
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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
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 license
Syntax Description
Defaults
If the number of licensed connections is not specified, the license key must allow an unlimited number of licensed connections. If the expiration date is not specified, the license key must be for a permanent license.
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.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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 two conversations to CICS, or one to each. One license key is used for both CICS and DB2 communications, so you can use either the dbconn license command or the txconn license command to configure the CTRC router.
Examples
The following example shows the configuration of a CTRC router with a license that allows up to 4000 connections until January 1, 2005:
txconn license 3C09A051320BAF020BFF45B3A2FF21D2 connections 4000 expiration-date 20050101Related Commands
Displays the status of CTRC licenses for DB2 communications.
show snasw node
Displays details and statistics of the SNASw operation.
Displays the status of licenses used for CTRC.
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
No default behavior or values.
Command Modes
EXEC
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
There is not a no form for this command.
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.001Elapsed time is noted in hours, minutes, seconds, and milliseconds.Related Commands
ping sna
Initiates an APPC session with a named destination LU to run the APING transaction program to check network integrity and timing characteristics.
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-id
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.0(5)XN
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0 T.
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
Displays a list of all CTRC routes defined for specified CICS transaction IDs, or displays the server routes of a particular CTRC server to CICS.
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 [access {cics | comti}] [ccsid number] [client-timeout minutes] [fold {on | off}] [host-timeout minutes] [ipaddress ip-address] [keepalive attempts number] [keepalive interval seconds] [port port-number] [target
{cics | ims-tm}] [window-size bytes]no txconn server server-name
Syntax 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 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 keepalive attempt or a keepalive interval, the server makes up to three attempts to send an acknowledgment message every 120 seconds.
If the port number is not configured, the server listens on port 1435.
If you do not specify a target, the server uses a default of cics.
If you do not specify a TCP/IP window size, the default value is 4096 bytes.
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. Set keepalive attempts or keepalive interval to zero (0) to disable the keepalive messages.
Examples
The following example shows the CTRC server newsvr being defined on the current router with the keepalive feature enabled to attempt five acknowledgment messages every 300 seconds:
txconn server newsvr destination GEN keepalive attempts 5 keepalive interval 300 port 1438Related Commands