cc/td/doc/product/software/ios113ed/113t
hometocprevnextglossaryfeedbacksearchhelp

Table of Contents

Cisco Database Connection

Description

Prerequisites

Platforms

Configuration Tasks

Configuration Examples

Command Reference

Debug Commands

Supported MIBs

Error Messages

Cisco Database Connection

Description

The Cisco Database Connection feature enables Cisco routers to implement IBM's distributed relational database architecture (DRDA) level 3 over TCP/IP. The Cisco router with Database Connection exists in the TCP/IP network, and clients use the Database Connection IP address and port on the router to connect to the IBM host system that exists in the SNA network.

When Database Connection is configured on a router, client-based Open Database Connectivity (ODBC) applications can connect to IBM's family of IBM D2 relational databases which include:

The router with Database Connection converts DRDA packets over TCP/IP to DRDA packets over APPC (LU 6.2) and then routes them to DB2 databases. Database Connection 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, Database Connection allocates an APPC conversation over SNA to an IBM server, and acts as a gateway between DRDA over TCP/IP and DRDA over APPC.

Figure 1 illustrates how the Cisco router configured with Database Connection 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 1: Cisco Router Configured with the Database Connection Feature



When configured on a router, the Database Connection feature enables desktop applications to access data in remote databases located on IBM hosts. Database Connection receives database access messages from the client over a TCP/IP link. Database Connection converts the messages to SNA and transmits them to the host using APPC services provided by the Cisco IOS APPN software.

Figure 2 shows a user working with a spreadsheet application on a PC and accessing database information from a remote relational database management system (RDBMS) on an IBM host. When the user seeks data from the RDBMS system on the IBM host, the spreadsheet application sends SQL statements to the remote host system and retrieves the data.


Figure 2: StarSQL PC client User Accesses Database Information from Mainframe



Benefits

The Database Connection feature offers the following benefits:

List of Terms

Application requester--Client in the DRDA protocol.

Application server--Server in the DRDA protocol.

DB2--IBM relational database management system.

Distributed Data Management (DDM)--IBM-architected data management interface used for data interchange between like or unlike systems. DRDA is based on DDM.

Distributed relational database architecture (DRDA)--A Connection protocol for distributed relational database processing that is used by IBM's relational database products.

Open database connectivity (ODBC)--A standard programming language interface used to connect to a variety of data sources.

Remote relational database management systems(RDBMS)--A relational database allows the definition of data structures, storage, and retrieval options, and integrity constraints. In such a database, the data and relations between them are organized in tables. A table is a collection of records and each record in a table contains the same fields. Certain fields may be designated as keys, which means that searches for specific values of that field will use indexing to speed them up. Records in different tables may be linked if they have the same value in one particular field in each table.

Prerequisites

To use the Database Connection feature, make sure the following prerequisites must be met:

The following DB2 software packages are supported:

Platforms

The Database Connection feature is supported on the following platforms and is available in the specified Cisco IOS Release software images:

Configuration Tasks

To configure the Database Connection feature on a Cisco router, perform the tasks in the following sections:

Define an APPN Control Point

An APPN control point definition is required to use APPN and the Database Connection feature. This definition adds the fully qualified control point name for the node, which is a combination of a network identifier and a control point name. The network identifier must be the same as other network nodes in the APPN subnetwork attached to this node. The control point name identifies this node uniquely within the particular subnetwork.

To define an APPN control point, perform the following task in global configuration mode: 

Task Command
Define an APPN control point. appn control-point netid.cpname

Performing this task takes you from global configuration mode into APPN control point configuration mode.

Define an APPN Port

An APPN port definition is required for Database Connection and is used to associate APPN capabilities with a specific interface that APPN will use. Each interface that will be used for APPN communications requires an APPN port definition statement. A port can be associated with a specific interface by performing the following task in global configuration mode:

Task Command
Define an APPN port associated with a interface. appn port portname interface

Define an APPN Link Station

Defining an APPN link station is optional for the Database Connection feature. A link station is a representation of the connection or potential connection to another node. In many cases, if the partner node is initiating the connection, a link station definition is not necessary. It will be built dynamically when the partner node initiates the connection. You must define a link station if you want this node to initiate APPN connections with other nodes. In addition, you may define a link station to specify attributes of an APPN connection regardless of which node initiates the connection.

To define an APPN logical link, perform the following task in global configuration mode:

Task Command
Define an APPN logical link. appn link-station linkname

Performing this task takes you from global configuration mode into APPN link station configuration mode. From the APPN link station configuration mode, you must associate the link station with an APPN port that it will use by performing the following task.

Task Command
Associate a link station with the APPN port that it will use. port portname

Define an APPN Mode

Defining the APPN mode is required for the Database Connection feature. An APPN mode definition is used by a network node to associate a mode name received on an APPN search or session request with a class of service known to this node. Most APPN nodes will supply the class of service to their network node server, so mode definition may not be required in many APPN networks. However, if this node is providing network node services to an end node that does not supply a class of service, or this node is providing network node services for a LEN node, mode definitions may be required for each mode that is used by the partner node.

Cisco provides standard predefined mode definitions for modes that are commonly used in an APPN network. The predefined mode names are the blank mode, #BATCH, #BATCHSC, #INTER, #INTERSC, CPSVCMG, and SNASVCMG. You can change a predefined mode or define a new mode. To define an APPN mode, perform the following task in global configuration mode:

Task Command
Define an APPN mode. appn mode modename

Performing this task takes you from global configuration mode into APPN mode configuration mode. Within this mode, you must assign a class of service to the mode definition by performing the following task.

Task Command
Associate a class of service with the defined mode. class-of-service cosname

The following commands allow for the addition, removal, or completion of configuration items within the APPN mode configuration mode:

Task Command
Negate or restore the default value for a configuration command. no command
Complete the APPN mode definition, return to global configuration mode, and update the APPN subsystem. complete
Allow modifications to a previously completed APPN mode definition. no complete
Exit APPN class of service definition dialog without completing the definition and without updating the APPN subsystem. exit

Define an APPN Partner LU Location

Defining the APPN Partner LU Location is optional for the Database Connection feature. The APPN directory stores names of resources and their owners. Usually this information is learned dynamically via APPN searches. However, you may wish to manually define the location of specific resources. Doing so can improve network performance by allowing directed APPN searches to travel straight to the owning control point, without the need for an initial broadcast search for the resource. However, APPN is known for its dynamic capabilities, not its need for system definition. For this reason, and for easier manageability, it is good practice to define location names only when necessary.

If you do not use APPN in your SNA environment, you must configure an APPN partner-lu-location and specify the destination LU and D2 for Database Connection in the router configuration.

When a LEN node is attached to an APPN network node, all destination resources that reside on the LEN node must be defined on the network node to be reachable via the APPN network.

To define a partner LU location, perform the following task in global configuration mode:

Task Command
Specify the partner resource name. appn partner-lu-location netid.luname

Specifying the partner resource name takes you from the global configuration mode into the APPN partner LU location configuration mode.

You must configure an owning control point for each partner LU configured. The owning control point is the control point name for the LEN node, end node, or network node on which the resource resides. To specify the name of the control point owning the partner LU, perform the following task in APPN partner LU location configuration mode:  

Task Command
Specify the name of the control point owning the partner LU. owning-cp netid.cpname

If this node is not the network node server for the resource, you may also configure the network node server name. To reduce APPN searching, the network node server operand must be coded and must be the current server for the resource.

If this node is the network node server for the resource being defined, do not configure a network node server.

To specify the name of the network node server for the resource, perform the following task in APPN partner LU location configuration mode:  

Task Command
Specify the name of the network node server for the resource. serving-nn netid.cpname

A partial name wildcard partner LU is a definition that applies to all resources that match a partial name. For example, a definition for location NETA.PE, which is specified as a wildcard definition, serves as a entry for NETA.PEANUT and NETA.PENNY, but not NETA.PUMKIN. Be careful when using partial name wildcards, as they can easily cause network problems if resources that match the partial name do not actually exist in the specified location.

A full name wildcard partner LU definition is specified by defining a partner LU location without specifying a resource name and specifying the wildcard option. Full wildcards answer positively to any search for any resource in the network. Only one full name wildcard definition can exist in an APPN network. Full wildcards are sometimes used when the APPN subnetwork is small and an attached LEN node is the gateway to a large connected network. Full wildcard definitions reduce APPN performance and can cause a variety of network problems. Hence, use of full name wildcard definitions should be avoided.

To specify a partial name or full wildcard partner LU, perform the following task in APPN partner LU location configuration mode:

Task Command
Specify the entry as a partial-name wildcard or a full wildcard. wildcard

The following commands allow you to add, remove, or complete configuration items within the APPN partner LU location configuration mode:

Task Command
Negate or restore the default value for a configuration command. no command
Complete the APPN partner LU definition, return to global configuration mode, and update the APPN subsystem. complete
Allow modifications to a previously completed APPN partner LU definition. no complete
Exit APPN partner LU definition dialog without completing the definition and without updating the APPN subsystem. exit

Configure the Database Connection Server

To configure a Database Connection server on a Cisco router, perform the following task in Priveleged EXEC mode:

Task Command
Configure a Database Connection server. 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]

When a client attempts to connect to a Database Connection server, the server's port, IP address, and remote database name (RDB name) determine whether that connection is accepted or not. By default, the port for Database Connection servers is 446.

You can configure Database Connection servers and specify any of the options used by the servers when accepting connections.

Configure Database Connection for StarSQL License

If you are using StarSQL or StarSQL Pro software, configure the Database Connection license for StarSQL clients by performing the following task in Priveleged EXEC mode :

Task Command
Configure a Database Connection license key. dbconn license license-key

The license key is available from StarQuest Software, Inc. Skip this step if you are not using StarSQL or StarSQL Pro products.

Monitor and Maintain Database Connection

To monitor and maintain Database Connection configured on a router, perform one or more of the following tasks:

Task Command
Display a summary of each Database Connection server. show dbconn server server-name
Display a detailed status of specified Database Connection server. show dbconn server
Display the status of each connection. show dbconn connection
Display a detailed status of specified Database Connection connection. show dbconn connection connection-id
Display the status of Database Connection connection server show dbconn connection server server-name
Display the status of a user connected to Database Connection show dbconn connection userid
Display a status of each connection that matches the specified RDB name. show dbconn connection rdbname rdbname
Display information on all ports through which Database Connection servers are accepting connections. show dbconn ports
Display the status of dbconn license for StarSQL. show dbconn license
Break the specified client connection to the server. clear dbconn connection connection-id
Connect to the relational database on the IBM system for troubleshooting. dbconn ping server-name [rdbname rdbname] [userid userid] [password password]
Enable debugging. debug dbconn {appc | config | drda | event | tcp | all}
Displays current status of debugging for Database Connection. show debugging

Start and Stop APPN Ports and Link Stations

APPN port and link station definitions are started automatically when the APPN subsystem starts. However, configuration commands will not take effect on an APPN port or link when it is active. The following privileged EXEC commands allow an APPN ports and link stations to be stopped and started when making configuration changes or when resetting the APPN port or link is desired: 

Task Command
Deactivate the specified APPN link. appn stop link-station linkname
Deactivate the specified APPN port. appn stop port portname
Activate the specified APPN link. appn start link-station linkname
Activate the specified APPN port. appn start port portname

Configuration Examples

The following sections provide Database Connection configuration examples:

Database Connection Servers with IP Addresses,
Configuration Example 1

Figure 3 shows a Database Connection configuration where the Database Connection servers are configured to listen on port 446 (by default) for IP addresses specified for these servers in the router's configuration for Database Connection. When a client attempts to make a connection, a Database Connection 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 3: Database Connection Servers' Configuration with IP Addresses



The following are the configurations for servers Server A, Server B, and Server C in the Cisco router's configuration:

dbconn server SERVERA ip-address 172.0.10.2 rdbname nevada
dbconn server SERVERB ip-address 172.0.45.3
dbconn server SERVERC rdbname iowa

Database Connection Servers with IP Addresses, RDB Names, and Ports, Configuration Example 2

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 Database Connection 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 Database Connection server that meets the most specific criteria accepts the connection. For example, Servers A and B in Figure 4 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 4: Database Connection Server Configuration with IP Address and RDB Name Defined



Database Connection Servers with IP Addresses, RDB Names and Ports, Configuration Example 3

The IP address and port specified for a server in a router's configuration also determine 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, Database Connection 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 4

If a situation arises where multiple servers in a router meet the criteria for accepting a client connection, the Database Connection server that meets the most specific criteria accepts the connection. In Figure 5, 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 were to connect to IP address 161.55.122.80 on port 446 and send 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 the highest precedence when matching a connection to a server.


Figure 5: Database Connection Server Configurations with IP Addresses, RDB Names, and Default Port



Configuration for Servers A, B, C, and D in the Cisco router:

hostname routera
!
enable password allie
dbconn server SERVERA ip-address 161.55.122.80 rdbname NEVADA
dbconn server SERVERB ip-address 161.55.122.80
dbconn server SERVERC rdbname NEVADA
dbconn server SERVERD

Database Connection With CIP and DB2 on VTAM, Example 5

Figure 6 illustrates a Cisco router with a Channel Interface Processor (CIP) that is configured with Database Connection. The CIP is networked and connected to VTAM on the mainframe. DB2 is configured on VTAM.


Figure 6: Cisco Router with CIP and Connection to DB2 on VTAM



The configuration in Figure 6 uses router commands to configure APPN over CIP and CSNA via RSRB. Note that the source-bridge ring-group of 100 matches the source bridge of 10 2 100 for interface Channel 13/2 to enable APPN to run over RSRB. In addition, the destination LAN address used by the APPN link station MVS1 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.

Configuration example for router Smoke:

!
version 11.3
service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname smoke
!
enable password 7 11051807
!
microcode CIP flash slot0:cip22-14
microcode reload
ip subnet-zero
no ip routing
!
dbconn server BUDDHA rdbname DB2510 rlu STARW.DSNV510 mode LU62STAR
!
interface TokenRing0/0
 mac-address 4000.2222.0501
 ip address 10.10.22.1 255.255.255.0
 no ip route-cache
 no ip mroute-cache
 early-token-release
 ring-speed 16
 multiring all
!
interface TokenRing0/1
 mac-address 4000.1111.0501
 ip address 198.147.235.196 255.255.255.224
 no ip route-cache
 no ip mroute-cache
 early-token-release
 ring-speed 16
 multiring all
!
source-bridge ring-group 100
!
interface Channel13/0
 no ip address
 no keepalive
 shutdown
!
interface Channel 13/1
 no ip address
 no keepalive
 csna F010 38
!
interface Channel 13/2
 no ip address
 no keepalive
 lan TokenRing 1
  source bridge 10 2 100
  adapter 1 4000.0190.2001
!
appn control-point STARW.SMOKECP
  xid-block-number 05E 
  xid-id-number 00002
  complete
!
appn mode LU62STAR
  class-of-service #INTER
  complete
!
appn port TOK1 TokenRing0/1
  complete
!
appn port TOK0 TokenRing0/0
  complete
!
appn port SRB rsrb
 rsrb-virtual-station 4000.2222.3333 50 1 100
 complete
!
appn link-station MVS1
 port SRB
 lan-dest-address 4000.0190.2001
 adjacent-cp-name NETA.MVS1
 complete
!
appn link-station BUDDHA
  port TOK1
  lan-dest-address 4000.0200.0448
  retry-limit infinite
  complete
!
appn partner-lu-location STARW.DSNV510 / DB2 APPL
  owning-cp STARW.BUDDHA / VTAM NetID
  complete
!
appn routing
ip default-gateway 198.147.235.12
no ip classless
logging monitor informational
!
line con 0
 exec-timeout 0 0
line aux 0
 transport input all
line vty 0 4
 exec-timeout 0 0
 password 7 11051807
 login
!

Sample VTAM host definitions:

>Switched Major Node
 000042 P0202    PU    ADDR=C1,                Router SMOKE
X
 000043                IDBLK=05E,
X
 000044                IDNUM=00002,
X
 000045                PUTYPE=2,
X
 000046                MAXDATA=1456,
X
 000047                USSTAB=STARSNA,
X
 000048                MODETAB=AGWTAB,
X
 000049                CPNAME=SMOKECP,
X
 000050                CONNTYPE=APPN
 000051 *
 000052 L02T0201 LU    LOCADDR=000,            Independent LU
X
 000053                MODETAB=AGWTAB,
X
 000054                MAXSESS=1024,
X
 000055                DLOGMOD=LU62STAR,PACING=1,VPACING=1

Sample DB2 APPLID :

DB2 APPL
 000100 DSNAPPL  VBUILD TYPE=APPL
 000200 DSNV510  APPL  APPC=YES,         X
 000300                AUTH=ACQ,         X
 000400                AUTOSES=1,        X
 000500                DMINWNL=2048,     X
 000600                DMINWNR=2048,     X
 000700                DSESLIM=4096,     X
 000800                EAS=65535,        X
 000900                MODETAB=AGWTAB,   X
 001000                SECACPT=ALREADYV, X
 001100                SRBEXIT=YES,      X
 001200                VERIFY=NONE,      X
 001300                VPACING=1,        X
 001400                SYNCLVL=SYNCPT,   X
 001500                ATNLOSS=ALL

Command Reference

This section documents the following new Database Connection configuration commands:

clear dbconn connection

Use the clear dbconn connection privileged EXEC command to break a client connection.

clear dbconn connection connection-id

Syntax Description

connection-id Client connection identification number.
Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Examples

In the following example, the client connection 786A7c is cleared:

router# clear dbconn connection 786A7C
Connection 786A7C cleared
Related Commands

show dbconn connection

dbconn license

Use the dbconn license privileged EXEC command to configure the Database Connection license for StarSQL clients. Use the no form of the command to remove the license.

dbconn license license-key
no dbconn license

Syntax Description

license-key License key obtained from StarQuest Software Inc. The license determines the maximum number of StarSQL connections to a Cisco router configured with Connection Database. The license key is a 32-character hexadecimal string and it is not case sensitive.
Command Mode

Priveleged EXEC.

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T. A Database Connection license is required if you use StarSQL clients.

Examples

In the following example, a StarSQL license is configured for StarSQL client connections:

dbconn license F66F84ABF809AF020HE0RC33KJH0MQ89
Related Commands

show dbconn license

dbconn ping

Use the dbconn ping EXEC command to check whether or not the Database Connection servers are connecting to the relational databases on the IBM systems.

dbconn ping server-name [user user-id ] [password password] [rdbname rdbname]
Syntax Description

server-name Name of the Database Connection server.
user-id (Optional) Userid used to connect to the IBM system. If no userid is specified, the ping connection is made without APPC security. The IBM system's security settings determine whether or not the ping can succeed.
password (Optional) Password used to connect to the IBM system.
rdbname (Optional) The name of the relational database. If RDB name is not specified, the RDB name configured for the server is used.
Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Sample Output

The following is sample output from the dbconn ping command:

router>dbconn ping canopus
RDB named NEVADA on database server CANOPUS successfully contacted!
Database server product id is QSQ03020, DB2 for OS/400 V3R2
Elapsed time was 00:00:00
Related Commands

show dbconn server

dbconn server

Use the dbconn server Priveleged EXEC mode command to configure a Database Connection server in a Cisco router. Use the no form of this command to unconfigure and disable the server.

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]
no dbconn server
Syntax Description
server-name Name of the Database Connection server. Server names are user-defined strings up to 16 characters.
ip-address (Optional) IP address used by the Database Connection server to receive a connection. When a connection arrives, this IP address is used for matching and selecting the server from multiple configured servers.
port-number (Optional) The port used to listen for connections. If no port is specified, the default is 446.
RDBname (Optional) The remote database name on host. When a connection arrives, this name is used to identify and select the appropriate server from multiple configured servers. The string is used to match the RDB name sent by the client in the DRDA data stream at connect time. The default RDB name is an asterisk (*) which indicates that this Database Connection server serves any remote database.
remote-LU (Optional) APPC remote LU used to allocate the connection to the IBM system. An example is NETA.S103B345. If no remote LU is specified, 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 APPN control point is used to fully qualify the LU name.
mode (Optional) APPC mode used to allocate the conversation to the IBM system. If no mode is specified, the default is #INTER.
TP-name (Optional) APPC remote transaction program name used to allocate the conversation to the IBM system. If no TP name is specified the default is the architected DRDA TP name \x076DB.
idle-timeout (Optional) Time in minutes to wait for an idle client. If there is no activity from the client for this amount of time, the connection is forcibly broken. The time spent in waiting for a response from the IBM system is not counted, only idle time in between client requests is counted. The maximum is 1440 minutes (24 hours). If no idle timeout is specified, the default is 0 (zero) for no timeout.
bytes (Optional) This value is used for the TCP receive window size. If no window size is specified, the default is 4K (4096 KB).
Command Mode

Priveleged EXEC.

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

You can configure more than one Database Connection server per router. For each IBM database system in your network, you can configure a Database Connection server in the router configuration.

If you do not specify a port number, DRDA clients in a TCP/IP network expect to use port 446 by default.

Examples

In the following example, a Database Connection server is configured:

dbconn server coffee rdbname COFFEE rlu PARIS.COFFEE match idle-timeout 20 window-size 16
Related Commands

clear dbconn connection
dbconn ping
show dbconn server
show dbconn ports

show dbconn connection

Use the show dbconn connection EXEC command to display the status of connections made to Database Connection servers.

show dbconn connection connection-id [server server-name] [user user-id]
[rdbname RDB-name]
Syntax Description

connection-id Display status for specified connection.
server-name (Optional) Display connection information for specified server.
user-id (Optional) Display connections for specified userid.
RDB name (Optional) Display connections for specified RDBname.
Command Mode

EXEC

Default

Displays all connections if you do not specify connection-id.

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Sample Output

The following is sample output from the show dbconn connection command:

router#show dbconn connection
ID       Server           Userid     ClientIPAddress Connect   Idle
6127E428 SERVERA          ALLIE      198.999.989.36  00:01:26  00:01:12
6127D34C SERVERB          BRIAN      198.999.989.84  00:00:48  00:00:41

The following is sample output from the show dbconn connection command for a specified connection:

router#show dbconn connection 6127E428
connection id 6127E428
  connection state is active
  server is WILLOW
  rdbname is KINGSTON
  userid is JSMITH
  client name is ARIES
  local ip-address is 198.999.999.5
  local port is 446
  client ip-address is 198.999.999.53
  client port is 1067
  connect time 00:03:51
  idle time 00:03:37 (client)
  508 bytes received from client
  9644 bytes received from host
  client is licensed StarSQL

Table 1 describes significant fields shown in the display.


Table 1: Show dbconn Connection Field Descriptions
Field Description
connection id Identification number of the connection made by a StarSQL client to the Database Connection server.
connection state Status of the connection made by a StarSQL client.
server Name of the Database Connection server.
rdbname Name of the relational database on the IBM system.
userid Userid of the user connected through a port to the Database Connection server.
client name Name of the client system.
local ip-address IP address of the Database Connection server in the router to which the client connects.
local port Port in the Database Connection server through which the client connects.
client ip-address IP address of the client connected to the Database Connection server.
client port Port used by the client to connect to the Database Connection server.
connect time Time when connection was made by the client to the Database Connection server.
idle time Amount of time that the active client connection has been idle.
Related Commands

show dbconn license
show dbconn ports
show dbconn server

show dbconn license

Use the show dbconn license EXEC command to display the status of licensed StarSQL connections made to Database Connection servers.

show dbconn license
Syntax Description

None

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Sample Output

The following is sample output from the show dbconn license command:

router#show dbconn license
Database Connection is licensed for unlimited connections, 2 licensed connections in use
Related Commands

dbconn license
show dbconn connection
show dbconn ports
show dbconn server

show dbconn ports

Use the show dbconn ports EXEC command to display information on all ports that are being used by Database Connection to receive connections.

show dbconn ports
Syntax Description

None

Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Sample Output

The following is sample output from the show dbconn ports command:

router#show dbconn ports
Port  State
446   listening
447   listening

Table 2 describes significant fields shown in the display.


Table 2: Show Dbconn Ports Field Descriptions
Field Description
Port Port number.
State Listening or disabled status.
Related Commands

show dbconn connection
show dbconn license
show dbconn server

show dbconn server

Use the show dbconn server EXEC command to display the status of Database Connection servers.

show dbconn server [server-name]
Syntax Description

server-name (Optional) Specific server for which status should be displayed.
Command Mode

EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Sample Output

The following is sample output from the show dbconn server command:

router#show dbconn server
Server           Port  IPAddress       RDBName            State    NumConn
SERVERA          446   0.0.0.0         MATTY              enabled  0
SERVERB          446   0.0.0.0         SCU_DSNM           enabled  4
SERVERC          446   0.0.0.0         DSN4               enabled  0
SERVERD          446   0.0.0.0         MKTG               enabled  0
SERVERE          446   0.0.0.0         ABBY               enabled  6
SERVERF          446   0.0.0.0         DB2510             enabled  0
SERVERG          446   0.0.0.0         ELLE               enabled  3
SERVERH          446   0.0.0.0         SUNSET             enabled  0
SERVERI          446   0.0.0.0         NELL               enabled  1
SERVERJ          446   198.989.999.32  SAMPLE             enabled  0
SERVERK          446   0.0.0.0         DB2410             enabled  0
SERVERL          446   0.0.0.0         SQLDS              enabled  0
SERVERM          446   0.0.0.0         STELLA             enabled  1
SERVERN          446   10.10.19.4      OAK                enabled  2
SERVERO          447   0.0.0.0         DB2510             enabled  0

The following is sample output from show dbconn server server-name command where the database server willow is a specified:

router#show dbconn server willow
server willow
  server state is enabled (accepting connections)
  ip-address is 10.10.11.4
  port is 446
  rdbname is MATTY
  rlu is STARW.MATTY
  mode is LU62STAR
  tpname is DB2
  idle-timeout is 1 minute
  window-size is 4096 bytes
  database server name is DB2
  database product id is SQL05000
  number of connections is 2000 
  number of licensed StarSQL connections is 200

Table 3 describes significant fields shown in the display:


Table 3: Show Database Connection Server Field Descriptions
Field Description
server Server name.
server state Current state of the server (enabled or disabled).
ip-address IP address accepted by the Database Connection server.
port Port number through which the Database Connection server accepts a client connection.
rdbname Name of the remote database accessed by the Connection Database server.
rlu Remote SNA LU used when connecting to the database server.
mode SNA mode used when connecting to the database.
tpname SNA transaction program name used for DRDA server on the database system.
idle-timeout Maximum length of time allowed for inactive connections to the Database Connection server.
window-size TCP receive window size.
database server name System name returned by the database server. Field shows none until first contact.
database product ID Database product ID. Field shows none until first contact.
number of connections Number of all ODBC clients currently connected to the Database connection server.
number of StarSQL connections Number of licensed StarSQL clients currently connected to the Database connection server.
Related Commands

show dbconn connection
show dbconn ports

Debug Commands

Following are the debug commands for the Database Connection feature.

debug dbconn all

Use the debug dbconn all priveleged EXEC command to turn on all debug flags for Database Connection. The Database Connection debug flags include appc, config, drda, event, and tcp. Use the no form of this command to disable all debugging output.

debug dbconn all
no debug dbconn all
Default

Debugging is not enabled for Database Connection.

Command Mode

Privelged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

The debug dbconn all command displays debug output for APPC, Database Connection configuration, DRDA, error messages, event traces and TCP.

Sample Output

See the sample outputs provided for the debug dbconn appc, debug dbconn config, debug dbconn config, debug dbconn drda, debug dbconn event, and debug dbconn tcp commands.

Related Commands

debug appn
debug dbconn appc
debug dbconn config
debug dbconn drda
debug dbconn event
debug dbconn tcp

debug dbconn appc

Use the debug dbconn priveleged EXEC command to display APPC-related trace or error messages. Use the no form of this command to disable debugging output.

debug dbconn appc
no debug dbconn appc
Syntax Description

None.

Command Mode

Priveleged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

In a router with stable Database Connection, the alias_cp_name in the trace message should not be blank. There should be no other APPC error message. You can use APPN debug commands with this debug command to track APPN-related errors.

Sample Output

Following is sample output for the debug dbconn appc command with explanations:

In a normal situation, only the following message is displayed.

DBCONN-APPC: alias_cp_name is "ASH"

The following error messages are displayed if there is a network configuration error or other APPN related problem. 

DBCONN-APPC-612C2B28: APPC error: opcode 0x1, primary_rc 0x0003,
secondary_rc 0x00000004
DBCONN-APPC-612C2B28: Verb block =
DBCONN-APPC-612C2B28:   0001 0200 0003 0000  0000 0004 0020 100C
DBCONN-APPC-612C2B28:   610A 828B 0000 0000  0000 0000 0000 0000
DBCONN-APPC-612C2B28:   0000 0000 8014 0003  0000 0000 0000 0000
DBCONN-APPC-612C2B28:   D3E4 F6F2 E2E3 C1D9  C4C2 F240 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  0200 0000 0000 0000
DBCONN-APPC-612C2B28:   0000 0000 D4C5 D9D9  C9C5 4040 4040 D7C5
DBCONN-APPC-612C2B28:   E3C5 D940 4040 4040  0000 0000 0000 0000
DBCONN-APPC-612C2B28:   00E2 E3C1 D9E6 4BE3  D6D9 C3C8 4040 4040
DBCONN-APPC-612C2B28:   4040 0000 0000 0000  0000 0000
DBCONN-APPC-612C2B28: ALLOCATE verb block =
DBCONN-APPC-612C2B28:   0001 0200 0003 0000  0000 0004 0020 100C
DBCONN-APPC-612C2B28:   610A 828B 0000 0000  0000 0000 0000 0000
DBCONN-APPC-612C2B28:   0000 0000 8014 0003  0000 0000 0000 0000
DBCONN-APPC-612C2B28:   D3E4 F6F2 E2E3 C1D9  C4C2 F240 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  4040 4040 4040 4040
DBCONN-APPC-612C2B28:   4040 4040 4040 4040  0200 0000 0000 0000

You can use the debug appn command to obtain more information.

The following message is displayed if a database connection is manually cleared and there is an outstanding APPC verb pending:

DBCONN-APPC-%612C2B28: Canceling pending APPC verb 0x1
Related Commands

debug appn
debug dbconn all
debug dbconn config
debug dbconn drda
debug dbconn event
debug dbconn tcp

debug dbconn config

Use the debug dbconn config priveleged EXEC command to display trace or error messages for Database Connection configuration and control blocks. Use the no form of this command to disable debugging output.

debug dbconn config
no debug dbconn config
Syntax Description

None.

Command Mode

Priveleged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

Most of the messages for Database Connection and control blocks do not report any errors. If a connection is inactive and cannot be cleared, use this command with debug dbconn appc, debug dbconn tcp, and debug appn commands to locate the problem. The alias_cp_name must match the configured APPN cpname.

Sample Output

Following is sample output for the debug dbconn config command:

DBCONN-CONFIG: alias_cp_name is "ASH     "
DBCONN-CONFIG: connection 612BDAAC matching server on 198.147.235.5:0 with
rdbname=STELLA
DBCONN-CONFIG: APPN shutdown; clearing connection 1234abcd
DBCONN-CONFIG: created server 612C2720
DBCONN-CONFIG: server 612C2720 (listen 60F72E94) is active
DBCONN-CONFIG: server 612C2720 (listen 60F72E94) is active
DBCONN-CONFIG: new connection 612BDAAC
DBCONN-CONFIG: listen 60F72E94 accepts connection 612BDAAC
DBCONN-CONFIG: server 60F74614 takes connection 612BDAAC
DBCONN-CONFIG: listen 60F72E94 releases connection 612BDAAC
DBCONN-CONFIG: server 60F74614 releases connection 612BDAAC
DBCONN-CONFIG: deleting connection 612BDAAC
DBCONN-CONFIG: listen 60F72E94 abandons connection 612BDAAC
DBCONN-CONFIG: server 612C2720 abandons connection 612BDAAC
DBCONN-CONFIG: deleting server 612C2720
DBCONN-CONFIG: daemon 60381738 takes zombie connection 612BDAAC
DBCONN-CONFIG: daemon 60381738  releases zombie connection 612BDAAC
Related Commands

debug appn
debug dbconn all
debug dbconn appc
debug dbconn drda
debug dbconn event
debug dbconn tcp

debug dbconn drda

Use the debug dbconn drda priveleged EXEC command to display error messages and stream traces for DRDA. Use the no form of this command to disable debugging output.

debug dbconn drda
no debug dbconn drda
Syntax Description

None.

Command Mode

Priveleged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

The DRDA debug messages display the result of parsing a DRDA stream. These messages are useful for debugging if a database connection cannot be established or the clients receive errors. An example of a DRDA client is StarSQL.

Sample Output

Following is sample output for the debug dbconn drda command:

DBCONN-DRDA-611404E4: DSS X'0056D0010001', length 86, end of chain, REQDSS,
correlator 1
DBCONN-DRDA-611404E4: End-of-chain received
DBCONN-DRDA-611404E4: EXCSAT.MGRLVLLS: AR Manager X'0102' at level 1
DBCONN-DRDA-611404E4: OBJECT X'0056D0010001', in COLLECTION X'ABCD', length
100, code point X'ABCD'SECCHK
DBCONN-PARSER-63518301: object parser level 2
DBCONN-DRDA-611404E4: DSS SEGMENT X'0056D0010001', length 100 
DBCONN-DRDA-611404E4: Syntax error in data stream, SYNERRCD = 1
Related Commands

debug appn
debug dbconn all
debug dbconn appc
debug dbconn config
debug dbconn event
debug dbconn tcp

debug dbconn event

Use the debug dbconn event priveleged EXEC command to display trace or error messages for Database Connection events. Use the no form of this command to disable debugging output.

debug dbconn event
no debug dbconn event
Syntax Description

None.

Command Mode

Priveleged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

If Database Connection is stable on the Cisco router, only the following types of trace messages should appear for this command: dispatch, post, flush events, event discarded, and send to. The trace message for Calling foreign event callback is displayed if APPN is stopped while Database Connection remains configured on the router. When other error messages are displayed, use the debug dbconn appc and debug dbconn drda commands to obtain more information.

Sample Output

Following is sample output for the debug dbconn event command with explanations. A normal trace for the debug dbconn event displays as follows:

DBCONN-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), msg
61339273, msgid 0x6372 'cr' buffer 0.
DBCONN-EVENT: == Send to 1234abcd, from 22938acd, msg 72618394, msgid
0x6372 'cr', buffer 0.

The following message is displayed if APPN is stopped, but Database Connection remains configured on the router:

DBCONN-EVENT: Calling foreign event callback for wakeup: major = 0x00001111,
minor = 0x00111189.

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 appn
debug dbconn all
debug dbconn appc
debug dbconn config
debug dbconn drda
debug dbconn tcp

debug dbconn tcp

Use the debug dbconn tcp priveleged EXEC command to display error messages and traces for TCP. Use the no form of this command to disable debugging output.

debug dbconn tcp
no debug dbconn tcp
Syntax Description

None.

Command Mode

Priveleged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3(2)T.

In a normal situation, TCP-related debug messages do not displayed. TCP-related error messages are not displayed if the router is running out of resources or an error exists with the TCP driver.

Sample Output

Following is sample output for the debug dbconn tcp command:

DBCONN-TCP-63528473: tcpdriver_passive_open returned NULL
DBCONN-TCP-63528473: (no memory) tcp_reset(63829482) returns 4
DBCONN-TCP: tcp_accept(74625348,&error) returns tcb 63829482, error 4
DBCONN-TCP: (no memory) tcp_reset(63829482) returns 4
DBCONN-TCP-63528473: (open) tcp_create returns 63829482, error = 4
DBCONN-TCP-63528473: tcb_connect(63829482,1.2.3.4,2010) returns 4
DBCONN-TCP-63528473: (open error) tcp_reset(63829482) returns 4
DBCONN-TCP-63528473: tcp_create returns 63829482, error = 4
DBCONN-TCP-63528473: tcb_bind(63829482,0.0.0.0,2001) returns 4
DBCONN-TCP-63528473: tcp_listen(63829482,,) returns 4
DBCONN-TCP-63528473: (errors) Calling tcp_close (63829482)
Related Commands

debug ip
debug dbconn all
debug dbconn event
debug dbconn config
debug dbconn drda

Supported MIBs

The Database Connection MIB is supported and contains information available from show commands for Database Connection. The MIB includes both configuration information as well as dynamic information such as active connection status. For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

Error Messages

Following are the error messages associated with Database Connection.


Error Message    DBCONN-APPCVERB: Unexpected APPC error: opcode 01, primary code 0003, secondary code 00000005

Explanation    An unexpected APPC error occurred.

Recommended Action    If the APPC error occurs when attempting to connect to the remote database server, try the dbconn ping command to test the APPC connectivity to the APPN remote LU. If the dbconn ping command fails, try stopping and restarting the APPN link to the remote system.


Error Message    DBCONN-APPNNOTSTARTED: APPN is not started -- unable to connect to remote database.

Explanation    A client connected to a Database Connection server, but the server was unable to connect to the remote database because APPN was not started.

Recommended Action    Start APPN in the router configuration and retry the client connection.


Error Message    DBCONN-APPNSTOPPED: APPN was stopped - existing connections have been closed.

Explanation    APPN was stopped while some dbconn connections were active.

Recommended Action    Restart APPN. Previously connected clients must reconnect.


Error Message    DBCONN-BADLICENSEKEY: Bad license key configured for Database Connection.

Explanation    The configured license key for StarSQL cannot be validated.

Recommended Action    Update the server configuration with the corrected license key.


Error Message    DBCONN-BADMODE: Unknown mode % configured for server %.

Explanation    The configured mode for the server was rejected by the remote database.

Recommended Action    Configure a mode that is acceptable to the remote database server. Contact your SNA network administrator to determine which mode to use on the remote system.


Error Message    DBCONN-BADRLU: Bad remote LU % configured for server %.

Explanation    The configured remote LU (rlu) for the server is incorrect.

Recommended Action    Configure an remote LU that is acceptable to the remote database server. Contact your SNA network administrator to determine the correct name of the remote LU on the remote database server. Verify that the SNA network name and the LU name are correct.


Error Message    Bad TP name configured for server SENATE.

Explanation    The configured TP name is not recognized by the database server.

Recommended Action    Configure a TP name that is available on the remote database server. With the exception of SQL/DS, almost all DB2 systems accept the DRDA default TP name of \x076DB. Contact your SNA network administrator or your DB2 administrator to determine the TPname used by your DB2. To use the DRDA default, do not explicitly configure a TP name for your Database Connection server.


Error Message    DBCONN-DRDA SYNTAX: DRDA data stream error from %, SYNERRCD 03.

Explanation    This is a low-level DRDA protocol error.

Recommended Action    Report the error to Cisco technical support. We recommend that you include an SNA line trace between the router and the remote database server. Include the output of debug dbconn drda command.


Error Message    DBCONN-SECFAIL: APPC security failed, client % using userid '%' for server %.

Explanation    The userid and or password provided by the client was rejected by the remote database server.

Recommended Action    Retry with correct userid and password.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.