-
Cisco IOS Bridging and IBM Networking Command Reference, Volume 2 of 2: IBM Networking, Release 12.3
-
IBM Networking Commands: A through B
-
IBM Networking Commands: C through D
-
IBM Networking Commands: D
-
IBM Networking Commands: E through O
-
IBM Networking Commands: P through S
-
IBM Networking Commands: S
-
IBM Networking Commands: show ext through show ext
-
IBM Networking Commands: show fra through show txc
-
IBM Networking Commands: S through X
-
Table Of Contents
certificate reload
To configure Secure Socket Layer (SSL) Encryption Support enabled to read the profile security certificate from the file specified in the servercert command, use the certificate reload command in customer profile configuration mode.
certificate reload
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Profile configuration
Command History
Usage Guidelines
There is not a no form for this command.
The TN3270 server must be configured for security.
Examples
The following example configures the TN3270 server with SSL Encryption Support to read the profile security certificate from the file specified in the servercert command:
certificate reloadRelated Commands
servercert
Specifies the location of the TN3270 server's security certificate in the Flash memory.
channel-protocol
To define a data rate of either 3 MBps or 4.5 MBps for Parallel Channel Interfaces, use the channel-protocol command in interface configuration mode. To return to the default rate of 3 MBps, use the no form of this command.
channel-protocol [s | s4]
no channel-protocol
Syntax Description
Defaults
If no value is specified, the default data rate for the Parallel Channel Adapter (PCA) and the Parallel Channel Port Adapter (PCPA) is 3 MBps.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid on Parallel Channel Interfaces.
Examples
The following example specifies a data rate of 4.5 MBps for the interface:
channel-protocol s4claw (backup)
To configure a Common Link Access for Workstations (CLAW) device (read and write subchannel) for communication with a mainframe TCP/IP stack in offload mode and configure individual members of a CLAW backup group for the IP Host Backup feature, use the claw command in IP host backup configuration mode. To remove the CLAW device, use the no form of this command.
claw path device-address ip-address host-name device-name host-app device-app [broadcast]
no claw device-address
Syntax Description
Defaults
No default behavior or values
Command Modes
IP host backup configuration
Command History
Usage Guidelines
This command defines information that is specific to the hardware interface and the IBM channels supported on the interface.
CLAW devices are used to switch IP packets between a mainframe and a channel-attached router.
At most, 128 statements can be configured per interface because each interface is limited to 256 subchannels. Each CLAW device uses a read channel and a write channel. There is also a restriction of 64 unique paths.
A limit of 32 CLAW device configuration commands is recommended.
Duplicate IP addresses are invalid for nonbackup configurations.
Duplicate IP addresses are permitted if they appear within a backup group of only claw or offload interface configuration commands. All configuration commands in one backup group must specify the backup keyword.
You can use the path interface configuration command to specify a number of paths that belong to a backup group. In that case, a claw IP host backup configuration command is used that needs no path variable or backup keyword.
Examples
The following examples show two methods for entering the same IP host backup group information. The first group of commands is the long form, using the claw interface configuration command. The second group is the shortcut, using the path interface configuration command and a claw IP host backup configuration command.
Long form:
claw c000 00 10.92.10.5 sysa router1 tcpip tcpipclaw c100 00 10.92.10.5 sysa router1 tcpip tcpipclaw c200 00 10.92.10.5 sysa router1 tcpip tcpipShortcut form:
path c000 c100 c200claw 00 10.92.10.5 sysa router1 tcpip tcpipRelated Commands
claw (primary)
To configure a Common Link Access for Workstations (CLAW) device (read and write subchannel) for communication with a mainframe TCP/IP stack in IP datagram mode and also configure individual members of a CLAW backup group for the IP Host Backup feature, use the claw command in interface configuration mode. To remove the CLAW device, use the no form of this command.
claw path device-address ip-address host-name device-name host-app device-app [broadcast] [backup]
no claw path device-address
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
10.2
This command was introduced.
12.0
The following options were added:
•
backup
•
Usage Guidelines
This command defines information that is specific to the hardware interface and the IBM channels supported on the interface. When used with the path command, the claw command provides a quick way to configure a CLAW backup group.
CLAW devices are used to switch IP packets between a mainframe and a channel-attached router.
At most, 128 statements can be configured per interface because each interface is limited to 256 subchannels. Each CLAW device uses a read channel and a write channel. There is also a restriction of 64 unique paths.
A limit of 32 CLAW device configuration commands is recommended.
Duplicate IP addresses are invalid for nonbackup configurations.
Duplicate IP addresses are permitted if they appear within a backup group of only claw or offload interface configuration commands. All configuration commands in one backup group must specify the backup keyword.
You can use the path interface configuration command to specify a number of paths that belong to a backup group. In that case, a claw IP host backup configuration command is used that needs no path variable or backup keyword. You can use the packed value as an optional keyword for the host-app and device-app arguments.
Examples
The following example shows how to enable IBM channel attach routing on channel interface 3/0, which is supporting an ESCON direct connection to the mainframe:
interface channel 3/0ip address 172.18.4.49 255.255.255.248claw c020 F4 172.18.4.52 HOSTB RTRA TCPIP TCPIPThe following example shows how to enable CLAW packing:
interface Channel 3/0ip address 172.18.4.49 255.255.255.248claw c010 F2 172.18.4.50 HOSTA RTRA PACKED PACKEDThe following example shows how an IP host backup group is specified using the backup keyword:
interface Channel3/0no ip addressno keepaliveno shutdownclaw 0100 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backupclaw 0110 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backupclaw 0120 C0 10.30.1.2 CISCOVM EVAL TCPIP TCPIP backupclaw 0110 C2 10.30.1.3 CISCOVM EVAL TCPIP TCPIPRelated Commands
clear alps circuits
To remove configured Airline Product Set (ALPS) circuits, use the clear alps circuits command in user EXEC or privileged EXEC mode.
clear alps circuits [ipaddr address | name string]
Syntax Description
ipaddr address
(Optional) Clear ALPS circuits for peer with specified IP address.
name string
(Optional) Clear ALPS circuits for peer with specified name.
Defaults
If no IP address or name is specified, the command clears all ALPS circuits.
Command Modes
EXEC
Command History
Examples
The following example clears the ALPS circuit named CKT1:
Router# clear alps circuits name CKT1Related Commands
alps auto-reset
Automatically resets a nonresponsive ALC ASCU in the DOWN state.
show alps circuits
Displays the status of the ALPS circuits.
clear alps counters
To clear all counters relevant to the ALPS feature, use the clear alps counters command in user EXEC or privileged EXEC mode.
clear alps counters
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example clears all counters for the ALPS feature:
Router# clear alps countersRelated Commands
clear dbconn connection
To break a client connection to DATABASE2 (DB2), use the clear dbconn connection command in privileged EXEC configuration mode, specifying the ID of the connection you want to terminate.
clear dbconn connection connection-id
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the client connection 786A7C being cleared:
Router# clear dbconn connection 786A7CConnection 786A7C clearedRelated Commands
clear dbconn statistic
To clear a specific statistic or all Cisco Transaction Connection (CTRC) statistics concerning communications with DB2, use the clear dbconn statistic command in privileged EXEC configuration mode.
clear dbconn statistic {chains | clientturnaround | connectionsdown | connectionsup | every | hostreceived | hostresponse | hostsent | maxconnections}
Syntax Description
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:
Router# clear dbconn statistic hostreceivedRelated Commands
show dbconn statistic
Displays all CTRC statistics concerning communications with DB2.
clear dlsw circuit
To cause all data-link switching plus (DLSw+) circuits to be closed, use the clear dlsw circuit command in privileged EXEC configuration mode.
clear dlsw circuit [circuit-id]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all circuits.
Caution
Examples
The following example closes all DLSw+ circuits:
Router# clear dlsw circuitclear dlsw history
To clear all currently inactive circuits from the DLSw+ circuit history, use the clear dlsw history privileged EXEC command.
clear dlsw history
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all inactive circuits from the DLSW+ circuit history:
clear dlsw historyclear dlsw local-circuit
To cause all locally-switched DLSw+ circuits to be closed, use the clear dlsw local-circuit privileged EXEC command.
clear dlsw local-circuit [circuit-id]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A user can specify a circuit ID of a specific circuit to clear rather than clearing all local-switched circuits.
Caution
Examples
The following example closes the locally-switched DLSw+ circuit with ID number 100:
clear dlsw local-circuit 100clear dlsw reachability
To remove all entries from the data-link switching plus (DLSw+) reachability cache, use the clear dlsw reachability command in privileged EXEC configuration mode.
clear dlsw reachability
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command does not affect existing sessions.
Examples
The following example removes all entries from the DLSw+ reachability cache:
Router# clear dlsw reachabilityclear dlsw statistics
To reset to zero the number of frames that have been processed in the local, remote, and group cache, use the clear dlsw statistics command in privileged EXEC configuration mode.
clear dlsw statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example resets to zero the number of frames in the local, remote, and group cache:
Router# clear dlsw statisticsclear dlsw transparent
To clear DLSw+ transparent local MAC entries, use the clear dlsw transparent privileged EXEC command.
clear dlsw transparent
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is designed to be used in networks that employ DLSw+ Ethernet redundancy without transparent mappings.
Examples
The following example clears DLSw+ transparent local MAC entries:
clear dlsw transparentclear extended counters
To clear the extended interface counters associated with Cisco Mainframe Channel Connection (CMCC) features, use the clear extended counters command in user EXEC or privileged EXEC mode.
clear extended counters [channel slot/port [csna | icmp-stack | ip-stack | llc2 | statistics | tcp-connections | tcp-stack | tg | tn3270-server | udp-stack]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command is valid on both the physical and virtual channel interfaces. To clear counters for a selected CMCC feature, you must specify the channel interface on which the feature is configured or running.
Counters displayed using the show extended channel EXEC command are cleared using this command.
Entering any form of this command will prompt the user for a confirmation before clearing any counters. A "CLEAR-5-EXT_COUNT" message is displayed to indicate completion of the command.
These counters will be cleared in the show commands and remain uncleared when obtained through the Simple Network Management Protocol (SNMP) interface.
Examples
The following example shows how to clear the extended interface counters:
Router# clear extended countersRelated Commands
clear ncia circuit
To drop a specified native client interface architecture (NCIA) circuit, use the clear ncia circuit command in privileged EXEC configuration mode.
clear ncia circuit [id-number]
Syntax Description
id-number
(Optional) Number assigned to identify the circuit. If no circuit ID number is specified, the command drops all circuits.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no circuit ID number is specified, the command drops all circuits.
Examples
The following example clears the active NCIA circuit identified as 791F8C:
Router# clear ncia circuit 791F8CRelated Commands
show ncia circuits
Displays the state of all circuits involving this MAC address as a source and destination.
clear ncia client registered
To release the control block of a specified registered client after terminating the active connection to it, use the clear ncia client registered command in privileged EXEC configuration mode.
clear ncia client registered [ip-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no IP address is specified in the command, the command releases the control blocks of all registered clients after terminating any active connections to them.
Examples
The following example terminates the active connection to the registered client identified by the IP address 10.2.20.126 and releases its control block:
Router# clear ncia client registered 10.2.20.126Related Commands
clear ncia client
To terminate a specified active client connection, use the clear ncia client command in privileged EXEC configuration mode.
clear ncia client [ip-address]
Syntax Description
ip-address
(Optional) IP address of the client. If no IP address is specified in the command, the command terminates all active client connections.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no IP address is specified in the command, the command terminates all active client connections.
Examples
The following example terminates the active connection to the client identified by the IP address 10.2.20.126:
Router# clear ncia client 10.2.20.126Related Commands
clear txconn connection
To clear a Cisco Transaction Connection (CTRC) connection to a Customer Information Control System (CICS) client and all associated transactions, use the clear txconn connection command in privileged EXEC configuration mode.
clear txconn connection connection-id
Syntax Description
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 T12.0(7)T
Examples
The following example clears the specified CICS client connection number 62146088 and all its transactions:
Router# clear txconn connection 62146088% Connection 62146088 clearedRelated Commands
clear txconn transaction
Terminates a specified CICS transaction.
show txconn connection
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 Cisco Transaction Connection (CTRC) statistics concerning communications with Customer Information Control System (CICS), use the clear txconn statistic command in privileged EXEC configuration mode.
clear txconn statistic {allocatetime | clientreceived | clientsent | clientturnaround | every | hostreceived | hostresponse | hostsent | maxconnections | maxtransactions | totalconnections | totaltransactions}
Syntax Description
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(7)T.
Examples
The following example clears the stored statistics for the number of bytes the current router has received from CICS clients:
Router# clear txconn statistic clientreceivedRelated Commands
show txconn statistic
Displays information about the CTRC communications of the current router with CICS.
clear txconn transaction
To terminate a specified Customer Information Control System (CICS) transaction, use the clear txconn transaction command in privileged EXEC configuration mode. This command terminates the conversation with the host and returns DEALLOC_ABEND_PROG to the client.
clear txconn transaction transaction-id
Syntax Description
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(7)T.
Examples
The following example clears the CICS transaction number 621FC8E0:
Router# clear txconn transaction 621FC8E0% Transaction 621FC8E0 clearedRelated Commands
client ip
To add an IP subnet to a client subnet response-time group, use the client ip command in response-time configuration mode. To remove an IP subnet from a client subnet response-time group, use the no form of this command.
client ip ip-address [ip-mask]
no client ip ip-address [ip-mask]
Syntax Description
Defaults
The default mask is 255.255.255.255.
Command Modes
Response-time configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
The following example adds an IP subnet to a client subnet response-time group:
tn3270-serverresponse-time group acctgclient ip 10.1.2.3 255.0.0.0Related Commands
client ip lu
To define a specific logical unit (LU) or range of LUs to a client at the IP address or subnet, use the client ip lu command in TN3270 PU configuration mode. To cancel this definition, use the no form of this command.
client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
no client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
Syntax Description
Defaults
No LUs are nailed. They are all available to any client.
Command Modes
TN3270 PU configuration mode
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. Multiple statements can be configured for one IP address or nail type either on one PU or multiple PUs. But each LU can appear in only one client statement.
A client with a nailed IP address can request one of the nailed LUs via the TN3270 device name. If the requested LU is not available then the connection is rejected.
A client with a nailed IP address cannot request an LU outside the range of nailed LUs for its type (screen or printer).
A client with a nonnailed IP address cannot request an LU that is configured as nailed.
The command will be rejected if some of the local address are already nailed. If the local address are in use by other remote clients, the nailing statement will take effect only when the local address is made available.
To cancel the definition, the no client form of the command must be entered exactly as the client command was originally configured. If a range of local address was specified, to cancel this definition the whole range of local address must be specified. There is no way to cancel only one local address if a whole range of local address was configured.
Examples
In the following example, local address from 1 to 50 are reserved for remote devices in the 10.69.176.0 subnet:
interface channel 2/2tn3270-serverpu BAGE4client ip 10.69.176.28 255.255.255.0 lu 1 50In the following example, local address 1 to 40 are reserved for screen devices in the 10.69.176.0 subnet, and 41 to 50 are reserved for printers in that subnet:
interface channel 2/2tn3270-serverpu BAGE4client ip 10.69.176.28 255.255.255.0 lu 1 40client printer ip 10.69.176.28 255.255.255.0 lu 41 50In the following example, an attempt to cancel a definition is rejected because it does not specify the full range of local address and the second attempt fails to specify the correct nail type:
interface channel 2/2tn3270-serverpu BAGE4client printer ip 10.69.176.50 255.255.255.0 lu 1 100no client printer ip 10.69.176.50 255.255.255.0 lu 1%Invalid LU range specifiedno client ip 10.69.176.50 255.255.255.0 lu 1 100%client ip 10.69.176.50 nail type not matched with configured nail type printerRelated Commands
pu (DLUR)
Creates a PU entity that has no direct link to a host and enters DLUR PU configuration mode.
client ip pool
To nail clients to pools, use the client ip pool command in listen-point configuration mode. To remove clients from pools, use the no form of this command.
client ip ip-address [ip-mask] pool poolname
no client ip ip-address [ip-mask] pool poolname
Syntax Description
Defaults
No clients are nailed to pools.
Command Modes
Listen-point configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
Usage Guidelines
If the pool is configured while logical unit (LU)s are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the name spaces do not clash.
Examples
The following is an example of the client ip pool command that nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named POOL-1:
tn3270-serverpool POOL-1 cluster layout 10s1plisten-point 172.18.4.18client ip 10.1.2.3 255.255.255.0 pool POOL-1Related Commands
client lu maximum
To limit the number of logical unit (LU) sessions that can be established for each client IP address or IP subnet address, use the client lu maximum TN3270 server configuration command. To remove a single LU limit associated with a particular IP address, use the no form of this command.
client [ip-address [ip-mask]] lu maximum number
no client [ip-address [ip-mask]]
Syntax Description
Defaults
The default is that there is no limit on the number of concurrent sessions from one client IP address.
The default value for the ip-mask argument is 255.255.255.255.
In the no form of this command, the default value for the number argument is 65535.Command Modes
TN3270 server configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. An instance of the client (lu limit) command on a given tn3270-server is uniquely identified by the ip-mask and the logical AND of the ip-address with that mask. For example, if the command is entered as the following:
client 10.1.1.62 255.255.255.192 lu maximum 2Then it will be stored (and subsequently displayed by write term) as:
client 10.1.1.0 255.255.255.192 lu maximum 2The maximum specified on the command can be changed by reissuing the command with the new value. It is not necessary to remove the command first.
When you use the no client command, only the corresponding client lu maximum statement is removed, as identified by the IP address and IP address mask combination. You cannot use the no client command to specify an unlimited number of LU sessions. The lu maximum keyword is optional in the no form of the command.
For example, if a service bureau has 8000 clients and each client IP address is limited to four LU sessions, you will never need more than 32000 concurrent LU definitions even when the service is running at 100 percent capacity.
Examples
The following example limits all clients to a maximum of two LU sessions:
client lu maximum 2The following example limits a client at IP address 10.1.1.28 to a maximum of three LU sessions:
client 10.1.1.28 lu maximum 3The LU limit can be applied to different subnets as shown in the following example. The most exact match to the client IP address is chosen. Clients with IP addresses that reside in the subnet 10.1.1.64 (those with IP addresses in the range from 10.1.1.64 through 10.1.1.127) are limited to a maximum of five LU sessions while other clients with IP addresses in the subnet 10.1.1.0 are limited to a maximum of four LU sessions.
client 10.1.1.0 255.255.255.0 lu maximum 4client 10.1.1.64 255.255.255.192 lu maximum 5The following example prevents an LU session for the client at IP address 10.1.1.28:
client 10.1.1.28 lu maximum 0Related Commands
maximum-lus
Limits the number of LU control blocks that will be allocated for TN3270 server use.
client pool
To nail clients to pools, use the client pool command in listen-point configuration mode. To remove clients from pools, use the no form of this command.
client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
no client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
Syntax Description
Defaults
No default behavior or values
Command Modes
Listen-point configuration
Command History
Usage Guidelines
If the pool is configured while logical units (LU)s are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the LU names do not conflict.
Examples
Nailing Clients to Pools by IP Address
The following is an example of the client pool command with the ip keyword configured. The command nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named POOL-1:
tn3270-serverpool POOL-1 cluster layout 10s1plisten-point 172.18.4.18client ip 10.1.2.3 255.255.255.0 pool POOL-1Nailing Clients to Pools by Device Name
The following is an example of the client pool command with the name keyword configured. The command nails the client at device name user1.cisco.com to the pool named POOL-2:
tn3270-serverpool POOL-2 cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool POOL-2 clusters 1client name user1.cisco.com pool POOL-2Nailing Clients to Pools by Device Name Using a Domain ID
The following is an example of the client pool command with the name keyword and the optional DNS-domain-identifier argument configured. The command nails the client at device name lucy-isdn49.cisco.com to the pool named POOL-2:
tn3270-serverdomain-id 23 .cisco.compool POOL-2 cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool POOL-2 clusters 1client name lucy-isdn49 23 pool POOL-2Nailing Clients to Pools by Domain Name
The following is an example of the client pool command with the domain-name keyword configured. The command nails any client at domain name cisco.com to the pool named POOL-2:
tn3270-serverpool POOL-2 cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool POOL-2 clusters 1client domain-name .cisco.com pool POOL-2Nailing Clients to Pools by Domain Name Using a Domain ID
The following is an example of the client pool command with the domain-id keyword configured. The command nails any client at domain name cisco.com to the pool named POOL-2:
tn3270-serverdomain-id 23 .cisco.compool POOL-2 cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool POOL-2 clusters 1client domain-id 23 pool POOL-2Related Commands
cmpc
To configure a Cisco Multipath Channel (CMPC or CMPC+) read subchannel and a CMPC (or CMPC+) write subchannel, use the cmpc command in interface configuration mode. To remove a subchannel definition and to deactivate the transmission group, use the no form of this command.
cmpc path device tg-name {read | write}
no cmpc path device
Syntax Description
Defaults
No default is specified.
Command Modes
Interface configuration
Command History
11.3
This command was introduced.
12.0(3)T
Support was added for the CMPC+ feature.
Usage Guidelines
Each cmpc configuration command in a given CMPC or CMPC+ TG specifies the same TG name. The corresponding tg command specifies the same TG name. Together, the cmpc and tg commands make up the TG specification.
The cmpc command defines the read/write subchannel addresses that CMPC or CMPC+ uses to connect to the host. The command corresponds to the definitions in the TRL major node on the host. Configure the cmpc command on a Cisco Mainframe Channel Connection (CMCC) adapter physical interface. Configure one read subchannel and one write subchannel. If CMPC or CMPC+ is configured on a CMCC adapter with two physical interfaces, the read and write CMPC or CMPC+ subchannels may be configured on separate physical interfaces.
The no cmpc command deactivates the CMPC or CMPC+ subchannel. If the TG is used for a non-High-Performance Routing (HPR) connection, all sessions using the TG will be terminated immediately. If the TG is an HPR connection, all sessions using the TG will be terminated if no other HPR connection is available to the host.
Examples
The following example configures a read and a write subchannel on path C020 for the CMPC or CMPC+ TG named CONFIGE:
cmpc C020 F8 CONFIGE READcmpc C020 F9 CONFIGE WRITERelated Commands
csna
To configure Systems Network Architecture (SNA) support on a Cisco Mainframe Channel Connection (CMCC) physical channel interface, use the csna command in interface configuration mode. This command is used to specify the path and device or subchannel on a physical channel of the router to communicate with an attached mainframe. To delete the Cisco Systems Network Architecture (CSNA) device path, use the no form of this command.
csna path device [maxpiu value] [time-delay value] [length-delay value]
no csna path device
Syntax Description
Defaults
maxpiu value: 20470 bytes
time-delay value: 10 ms
length-delay value: 20470 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
The maxpiu, time-delay and length-delay keywords control the characteristics of host-bound traffic for the CSNA subchannel. The channel protocol used by CSNA allows multiple SNA frames to be blocked into one channel I/O block, reducing the channel bandwidth utilization and mainframe and CMCC adapter process utilization.
The maxpiu keyword allows you to set the maximum size of a host-bound channel I/O block.
The time-delay keyword instructs the CSNA subchannel to delay sending the channel I/O block for the specified time in milliseconds, from the time the first SNA packet is blocked. This can increase the network latency for an SNA packet by up to the specified time delay.
The length-delay keyword instructs the CSNA subchannel to delay sending the channel I/O block until it contains the number of bytes specified by the length-delay keyword. An accumulated block is sent to the mainframe if one of the following conditions is true:
•
•
•
A time delay value of 0 instructs the CSNA subchannel to send SNA packets to the mainframe as soon as they are received from the network. A length delay value of 0 instructs the CSNA subchannel to ignore this parameter.
The no csna command deactivates and removes the CSNA subchannel configuration. It also deactivates all Logical Link Control, type 2 (LLC2) sessions established over the subchannel.
Examples
The following example shows CSNA, offload, and Common Link Access for Workstations (CLAW) configured on a channel interface. CSNA has no dependencies to CLAW, offload, or CMPC.
interface channel 1/0no ip addressno keepaliveoffload c700 c0 172.18.1.127 TCPIP OS2TCP TCPIP TCPIP TCPIP APIclaw C700 c2 172.18.1.219 EVAL CISCOVM AAA BBBcsna c700 c4csna c700 c5 maxpiu 65535 time-delay 100 length-delay 65535csna c700 c6 maxpiu 65535 time-delay 100Related Commands
dbconn license
To configure client licenses for Cisco Transaction Connection (CTRC) connections to DATA BASE2 (DB2) or Customer Information Control System (CICS), use the dbconn license command in global configuration mode. To remove the licenses, use the no form of this command in privileged EXEC configuration 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
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 DATABASE2 (DB2), use the dbconn pem command in global configuration mode. 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 the tp-name assignment 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
show dbconn server
Displays information about CTRC servers configured for DB2 communications.
dbconn ping
To determine whether Cisco Transaction Connection (CTRC) servers are connecting to DATABASE2 (DB2) host databases, use the dbconn ping command in user EXEC or privileged EXEC mode.
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 Advanced Program-to-Program Communication (APPC) security. The DB2 system's security settings determine whether the ping can succeed.
If no rdbname value is specified, the relational database name configured for the CTRC server is used.Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command can be used for CTRC servers that communicate with DB2 over either Systems Network Architecture (SNA) or TCP/IP (dbconn servers and dbconn tcpservers). There is not a no form this command.
Examples
The following example illustrates using the dbconn ping command to verify the connection to the default database for the CTRC server SERVER-1:
dbconn ping SERVER-1RDB named DB2510 on database server SERVER-1 successfully contacted!Database server product id is QSQ03020, DB2 for OS/400 V3R2Elapsed time was 00:00:00Related Commands
dbconn server
To configure a Cisco Transaction Connection (CTRC) server process for Advanced Program-to-Program Communication (APPC) communications with DATABASE2 (DB2), use the dbconn server command in global configuration mode. 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 RDB name, 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 designed 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 Customer Information Control System (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 the keepalive attempts or keepalive interval keyword to zero (0) to disable the keepalive messages.
Examples
The following example shows configuring a CTRC server named SERVER-1 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 SERVER-1 idle-timeout 20 keepalive attempts 5 keepalive interval 300 mode IBMRDB rdbname DB2510 rlu STARW.SERVER-1Related Commands
dbconn tcpserver
To configure a Cisco Transaction Connection (CTRC) server process to communicate with IP-enabled DATABASE2 (DB2) databases, use the dbconn tcpserver command in global configuration mode. 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 every 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 RDB name.
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
default-profile
To specify the name of the profile to be applied as a default to all the listen points, use the default-profile command in security configuration mode. To disable the default profile specification, use the no form of this command.
default-profile profilename
no default-profile profilename
Syntax Description
Defaults
No default profile.
Command Modes
Security configuration
Command History
Usage Guidelines
If this command is configured, this profile name and all of its attributes will be associated with all listen points that do not specify an individual profile with the sec-profile command.
Profile names cannot be duplicated.
Entering the no form of this command removes the default specification and any listen points that do not have the sec-profile command specified will revert to a nonsecure mode.
This command has no retroactive effect. If a listen point is specified using the listen-point command, and the sec-profile command was already configured for that listen point, then all client connections to that listen point will be secure.
If a listen point is specified using the listen-point command, and the default-profile command is not configured, then all client connections to that listen point will not be secure. However, if the default-profile command is later configured, then all now connections to that listen point will be secure using the specified default-profile command. This will not affect the nonsecure connections.
Examples
The following example specifies DOMESTIC as the default profile name for all clients connecting to listen point 10.10.10.1 until the default-profile LAM command is configured. Once the default-profile LAM command is configured, all new client connections will use LAM as the default profile.
tn3270securityprofile NOSECURITY nonedefault-profile DOMESTICpu DIRECT 012ABCDE tok 0 04default-profile LAMlisten-point 10.10.10.1Related Commands
disable (TN3270)
To turn off security in the TN3270 server, use the disable (TN3270) command in security configuration mode.
disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Security configuration
Command History
Usage Guidelines
Configuring the disable command does not terminate any active secure or nonsecure connections. This command specifies that all new connections established with the TN3270 server will be nonsecure. If a client initiates a change cipher specification for an existing secure connection, then the TN3270 server will process the request.
There is not a no form for this command. The enable command is equivalent to the no form of this command.
Examples
The following example turns off security in the TN3270 server so that all new connections established with the TN3270 server will be nonsecure:
disableRelated Commands
