-
Cisco IOS Release 12.0 Bridging and IBM Networking Configuration Guide
-
About the Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Bridging and IBM Networking Overview
- Part 1: Bridging
-
Part 2: IBM Networking
-
Configuring Remote Source-Route Bridging
-
Configuring Data-Link Switching Plus
-
Configuring Serial Tunnel and Block Serial Tunnel
-
Configuring LLC2 and SDLC Parameters
-
Configuring IBM Network Media Translation
-
Configuring DSPU and SNA Service Point
-
Configuring SNA Frame Relay Access Support
-
Configuing APPN
-
Configuring Cisco Database Connection
-
Configuring NCIA Client/Server Topologies
-
Configuring Cisco Mainframe Channel Connection Adapters
-
Configuring the Airline Product Set
-
-
Table Of Contents
Configuring Cisco Mainframe Channel Connection Adapters
Cisco's Mainframe Channel Connection Adapters
Differences between the CIP and CPA
TCP/IP Environments Using CLAW
Cisco MultiPath Channel Environments
CMCC Adapter Interface Configuration Task List
Load the CMCC Adapter Microcode Image
Configure Channel Interface Tracking for HSRP or SNMP Alerts
Configure TCP/IP CLAW or CLAW Packing Support
Configure the IBM Channel Attach Interface
Select a Data Rate for the Parallel Channel Interfaces
Configure Other Interface Support
Configure TCP/IP Offload Support
Configure the IBM Channel Attach Interface
Select a Data Rate for the Parallel Channel Interfaces
Configure Other Interface Support
Select a Data Rate for the Parallel Channel Interfaces
Configure the Subchannel Information
Configure the LOCADDR Priority
Configure an Internal Adapter's Link Characteristics
Configure the CMCC Adapters for IP Host Backup
Configure a CLAW IP Host Backup Group
Configure an Offload IP Host Backup Group
Configure an IP Host Backup Group Using Paths
Values from the Host IOCP File
Values from the Host TCP/IP File
Monitor and Maintain the Interface
Monitor the Physical Channel Interface on the CPA
Shut Down and Restart an Interface
Run CMCC Adapter Interface Loopback Diagnostics
Configure CMCC Adapter Core Dump
Configure TN3270 on a CMCC Adapter
Formation of LU Model Type and Number
IP Type of Service and Precedence Setting
VTAM Host Configuration Considerations for Dynamic LU Allocation
TN3270 Server Configuration Mode
Commands Allowed in Multiple Modes
TN3270 Configuration Task List
Task List for Multiple APPN Hosts
Configure PU Parameters on the TN3270 Server
Configure the VTAM Transport Resource List Major Node
Configure the VTAM Local SNA Major Node
Configure the CMPC Subchannels
Configure the CMPC Transmission Groups
Configure the CMCC Adapter Internal LAN for CMPC
Configure the CMCC Adapter Internal LANs
Configure the Internal Adapter and Its Link Characteristics
CMCC Interface Configuration Examples
IP Address and Network Mask Configuration Example
CLAW Packing Configuration Examples
ECPA CSNA Configuration Example
Configure TN3270 DLUR with CMPC Host Connection
Static and Dynamic LUs with LU Nailing Configuration Example
Removing LU Nailing Definitions Example
Configuring Different Values for Precedence and TOS Example
Overriding Configured Values Example
Configure IP Host Backup Example
CMPC Configuration Examples for CMPC
Connecting VTAM to a Remote PC with Communications Server/2 Example
Connecting VTAM to the APPN NN on the CIP Example
Connecting Two VTAM Nodes Using Two CIPs in the Same Router Example
Connecting VTAM to the APPN NN on a Remote Router with DLUR Example
TN3270 Server DLUR Running on the Same CIP Example
Configuring Cisco Mainframe Channel Connection Adapters
This chapter describes how to configure the Cisco Mainframe Channel Connection (CMCC) family of adapters. These adapters include the Channel Interface Processor (CIP) for Cisco 7500 and Cisco 7000 series routers, and the ESCON Channel Port Adapter(ECPA) and the Parallel Channel Port Adapter (PCPA) for Cisco 7200 series routers.
Note
In this chapter, references to Channel Port Adapter (CPA) correspond to both the ECPA and the PCPA.
For hardware technical descriptions and information about installing the router interfaces, refer to the hardware installation and maintenance publication for your product. For a complete description of the CMCC adapter commands in this chapter, refer to the "Cisco Mainframe Channel Connection Adapter Commands" chapter of the Bridging and IBM Networking Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Cisco's Mainframe Channel Connection Adapters
The CMCC adapter family supports the IBM channel attachment and includes the following products:
•
•
•
All CMCC adapters support the full range of channel software applications available in the Cisco IOS software.
Figure 170 Cisco Mainframe Channel Connection Adapters
CIP
The CIP for the Cisco 7000 and Cisco 7500 series is designed for high-end network environments that demand high-performance, high-port density, high-capacity solutions.
The CIP provides support for the IBM ESCON Channel Adapter (ECA) and Bus-and-Tag Parallel Channel Adapter (PCA) channel-attached interfaces from Cisco 7000 series routers to IBM mainframes and in most cases, it eliminates the need for a separate front-end processor (FEP).
A single CIP can support up to two physical channel interfaces in any combination of either PCA or ECA. The CIP's Parallel channel interface is provided by the PCA, and the ESCON channel interface is provided by the ECA. Each CIP is pre-configured with the appropriate channel adapters at manufacturing time.
The Cisco 7000 and Cisco 7500 series routers support online insertion and removal (OIR), which allows you to install or remove CIPs while the system is operating.
Benefits
The key benefits of the CIP are as follows:
•
•
•
•
•
CPA
The CPA is available for the Cisco 7200 series routers. The CPA expands the value of Cisco's IBM channel solution by providing channel connectivity to mid-range mainframe configurations. The CPA is a standard single-width port adapter supporting ESCON or Parallel channel interfaces to IBM mainframes.
The only differences between CMCC software applications running on the CIP and a CPA are performance and capacity. The performance difference is based upon differences in the internal bus architecture of a CIP vs a CPA, and the capacity difference is based on the difference in maximum memory configurations (128 MB for CIP and 32 MB for CPA).
Each CPA provides a single channel interface for Cisco 7200-series routers. In some situations, this eliminates the need for a separate front-end processor (FEP). The CPA contains a single I/O connector.
The Cisco 7200-series router supports online insertion and removal (OIR), which allows you to install or remove port adapters while the system is operating.
Benefits
The key benefits of CPA are as follows:
•
•
•
ECPA
An ECPA is classified as a high-speed port adapter providing a single ESCON physical channel interface. Current Cisco 7200 configuration guidelines recommend using no more than three high-speed port adapters in a single Cisco 7200 router. Refer to the Cisco 7200 Series Port Adapter Hardware Configuration Guidelines publication for more details.
PCPA
A PCPA provides a single Parallel channel physical interface supporting both 3.0 and 4.5 MBps data transfer rates.
Differences between the CIP and CPA
illustrates the differences between the CMCC adapters.
Supported Environments
The CMCC adapters provide support for the environments discussed in the following sections:
•
•
TCP/IP Environments Using CLAW
TCP/IP mainframe protocol environments for IBM operating systems Multiple Virtual Storage (MVS) and Virtual Machine (VM) are supported. This support includes TCP/IP-based applications such as terminal emulation (Telnet), the File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP); and Network File System (NFS), a distributed file access system. In addition, Internet Control Message Protocol (ICMP) and User Datagram Protocol (UDP) are supported.
The Cisco IOS implements the Common Link Access to Workstation (CLAW) channel protocol to transport data between the mainframe and a CMCC adapter in TCP/IP environments. Each CLAW connection requires two devices out of a maximum of 256. Although this allows for a maximum of 128 CLAW connections per interface, a maximum of 32 CLAW connections per interface is recommended.
The CLAW packing feature enables the transport of multiple IP packets in a single channel operation and significantly increases throughput performance between a mainframe and a CMCC adapter. Currently, IBM's TCP/IP stack does not support the CLAW packing feature.
The CLAW packing feature requires changes to the mainframe CLAW driver support. In partnership with Cisco Systems, Interlink Computer Science has made the corresponding CLAW driver change to Cisco IOS for S/390 Release 2 and Interlink TCPaccess 5.2. Customers must make the necessary changes to their host configurations in order to enable the CLAW packing feature.
TCP/IP Offload Environments
TCP/IP mainframe protocol environments for IBM operating systems MVS, VM, and Transaction Processing Facility (TPF) are supported.
The TCP/IP offload feature for CMCC adapters delivers the same function as the TCP/IP offload function on the 3172 Interconnect Controller (Model 3), but with increased performance.
IP Host Backup Environment
You can connect multiple mainframes to a single CMCC adapter using a ESCON. Often, these mainframes run using the ESCON Multiple Image Facility (EMIF), which permits the physical machine to be divided into multiple logical partitions (LPARs). By defining an unused partition on another mainframe, a user can move the operating system from a failed mainframe or mainframe partition to the unused partition. By having multiple paths to each device, the move is accomplished without changing the mainframe software. This function also permits moving an IP stack between multiple operating system images.
On the CMCC adapter, each IP connection is treated as a physical device. The CMCC adapter does not support multiple active paths to a single IP connection (or device). Prior to IP Host Backup, the router configuration had to be changed whenever the mainframe operating system was moved from one mainframe or LPAR to another. The IP Host Backup feature permits the mainframe operating system to be moved from one mainframe to another without requiring a change to the router configuration at the time of the move.
Note
TN3270 Server Environments
The TN3270 server feature on a CMCC adapter card provides mapping between an SNA 3270 host and a TN3270 client connected to a TCP/IP network as shown in . Functionally, it is useful to view the TN3270 server from two different perspectives: SNA functions and Telnet Server functions.
•
From the perspective of an SNA 3270 host connected to the CMCC adapter, the TN3270 server is an SNA device that supports multiple PUs, with each PU supporting up to 255 logical units (LUs). The LU can be Type 1, 2, or 3. The SNA host is unaware of the existence of the TCP/IP extension on the implementation of these LUs.
The LUs implemented by TN3270 server are dependent LUs. To route these dependent LU sessions to multiple VTAM hosts connected to the TN3270 server in the CMCC adapter card, rather than routing in the VTAM hosts, the TN3270 server implements a SNA session switch with end node dependent LU requester (DLUR) function. Using the DLUR is optional so that the TN3270 server can be used with VTAM versions prior to version 4.2, which provide no Advanced Peer-to-Peer Networking (APPN) support.
SNA session switch allows you to eliminate SNA subarea routing between hosts of TN3270 traffic by establishing APPN links with the primary LU hosts directly.
•
From the perspective of a TN3270 client, the TN3270 server is a high-performance Telnet server that supports Telnet connections, negotiation and data format. The server on the CMCC adapter card supports Telnet connection negotiation and data format as specified in RFC 1576 (referred to as "traditional TN3270") and RFC 1647 (referred to as "TN3270E").
Figure 171 TN3270 Implementation
Unless the TN3270 server uses a Token Ring connection to a Front-End Processor (FEP) as its host connection, it will require CSNA or CMPC support. For this reason, TN3270 configuration issues and tasks begins in the section "Configure TN3270 on a CMCC Adapter," later in this chapter.
Note
Cisco SNA Environments
The CSNA feature provides support for SNA protocols over both ESCON and Parallel interfaces to the IBM mainframe. As an IBM 3172 replacement, a CMCC adapter supports the External Communications Adapter (XCA) feature of Virtual Telecommunications Access Method (VTAM), which allows VTAM to define Token Ring devices attached to the 3172 as switched devices.
In SNA environments, support for the XCA feature of VTAM allows the CMCC adapter to provide an alternative to FEPs at sites where NCP is not required for SNA routing functions.
By providing CLS and the Logical Link Control type 2 (LLC2) protocol stack on the CMCC adapter card, all frames destined to the CMCC adapter or from the CMCC adapter card are switched by the router. The presentation of LAN media types allows the CSNA feature to take advantage of current source-route bridging (SRB), remote source-route bridging (RSRB), data-link switching plus (DLSw+), Source-Route Translational Bridging (SR/TLB), internal SDLC-LLC2 translational bridging (SDLLC), Qualified Logical Link Control (QLLC) services and APPN.
The CSNA feature supports the following communication through a Cisco 7000 with RSP7000, Cisco 7500, and Cisco 7200 series router:
•
•
•
•
The CSNA feature provides SNA connectivity through Media Access Control (MAC) addresses configured for internal MAC adapters on the Cisco 7000 with RSP7000, Cisco 7500 series router and the Cisco 7200 series router. These internal MAC adapters correspond to XCA major node definitions in VTAM, providing access points (LAN gateway) to VTAM for SNA network nodes. The internal MAC adapters are configured to exist on internal LANs located on a CMCC adapter card. Each CMCC adapter card can be configured with multiple internal Token Ring LANs. Each internal Token Ring LAN must be configured to participate in source-route bridging. There is a maximum limit of 18 internal MAC adapters per CMCC adapter. The internal MAC adapter is an emulation of LAN adapters in an IBM 3172 Interconnect Controller.
Cisco MultiPath Channel Environments
The CMPC feature provides support for APPN connections using both High Performance Routing (HPR) and Intermediate Session Routing (ISR). It supports the VTAM Transport Resource List (TRL) major node and the VTAM Local SNA major node.
The CMPC feature can be used to establish an APPN connection between VTAM and the following APPN nodes:
•
•
•
•
•
The CMPC feature isolates VTAM from the actual network topology. The MPC protocol is terminated on the CMCC adapter and converted to LLC protocols. Once converted to LLC protocols other Cisco features are used to connect VTAM to other APPN nodes in the network. CMPC can be used with DLSw+, RSRB, SR/TLB, SRB, SDLLC, QLLC, ATM LAN emulation, and FRAS host to provide connectivity to VTAM.
CMCC Adapter Interface Configuration Task List
You can perform the tasks in the following sections to configure and maintain IBM channel attach interfaces.
Some CMCC adapter software features are configured on a virtual port. On the CIP adapter cards installed in a Cisco 7000 with RSP 7000 or a Cisco 7500 series router, there are up to two physical ports, numbered 0 and 1, and a virtual port, numbered 2. However, on the CPA installed in a Cisco 7200 series router, the single physical port and the virtual port are configured using the same port number ID, number 0.
Not all tasks are required. Your CMCC adapter image may be preloaded. You must select an interface, after which you configure the features you want supported on that interface.
Note
•
•
•
•
•
•
•
•
•
See the end of this chapter for "CMCC Interface Configuration Examples."
Because the TN3270 server configuration is performed after an interface is configured for CSNA support, TN3270 configuration issues and tasks are addressed separately from the interface configuration tasks. The TN3270 configuration task list begins in the section "TN3270 Configuration Task List," later in this chapter.
Load the CMCC Adapter Microcode Image
This section provides information on loading the microcode images for the CIP and CPA.
CIP Microcode Image
Beginning with Cisco IOS Software Release 11.1, the CIP microcode (or CIP image) no longer is bundled with the Cisco IOS software. You must have Flash memory installed on the Route Switch Processor (RSP) card to use the IBM channel attach features in Cisco IOS Software Release 11.1 and later.
The CIP image is preloaded on Flash cards for all Cisco 7000 with RSP7000 and Cisco 7500 series routers ordered with the CIP option for Cisco IOS Software Release 11.1 and later. Use the commands in this section if you are upgrading the CIP image in your router.
To prepare the CIP, use the following commands beginning in privileged EXEC command mode:
CPA Microcode Image
The CPA microcode image is preloaded on Flash memory cards for Cisco 7200 series routers for Cisco IOS Release 11.3(3)T and later. You may be required to copy a new image to Flash memory when a new microcode image becomes available. Use the commands in this section if you are upgrading or loading a microcode image other than the default.
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:
Select the Interface
Before you configure your channel attach interface, you must select the interface. Use the following command in global configuration mode:
interface channel slot/port
Select the channel attach interface and enter interface configuration mode.
Use the show extended channel EXEC commands to display current CMCC adapter status. This command provides a report for each interface configured to support IBM channel attach.
Configure Channel Interface Tracking for HSRP or SNMP Alerts
If you want to use Hot Standy Router Protocol (HSRP) or SNMP alerts to monitor channel interface status for an ECPA or PCPA channel interface, use the following command in interface configuration mode to enable physical interface signal tracking:
state-tracks-signal
Enables tracking of the physical interface signal for an ECPA or PCPA channel interface.
The state-tracks-signal command is valid only on channel interfaces which combine the functions of both a physical and virtual interface. The ECPA and PCPA are examples of this type of channel interface. The command is not valid for the CIP, which has a separate channel interface for the virtual channel functions.
Configure TCP/IP CLAW or CLAW Packing Support
The following sections describe how to configure CLAW support. This feature is configured on the physical interface. All tasks, except for configuring other interface support are required.
•
•
•
See the section "Select Host System Parameters" for guidelines on matching interface configuration values with host system values.
Assign an IP Address
You must assign an IP address to the channel interface so that it can communicate with other devices (or tasks) on the network. The IP address you assign to the interface must be in the same subnetwork as the hosts with which you wish to communicate.
To assign an IP address, use the following command in interface configuration mode:
ip address address mask
Assign an IP address and network mask to the selected interface.
Configure the IBM Channel Attach Interface
You must define the devices, or tasks, supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCPIP configuration. Refer to the section "Select Host System Parameters" for guidelines on matching interface configuration values with host system values.
To configure an IBM channel interface, use the following command in interface configuration mode:
claw path device-address ip-address host-name device-name host-app device-app [broadcast] [backup]
Define the CLAW parameters for this device.
The CLAW Packing feature requires changes to the mainframe CLAW driver support. In partnership with Cisco Systems, Interlink Computer Science has made the corresponding CLAW driver change to Cisco IOS software for S/390 Release 2 and Interlink TCPaccess 5.2. Configuration parameters in the host TCP/IP applications must change to enable the CLAW packing feature.
See the section "CMCC Interface Configuration Examples" for samples of claw commands for different configurations.
Select a Data Rate for the Parallel Channel Interfaces
When you configure a Parallel channel attach interface, you must define a data rate of either 3 MBPS or 4.5 MBPS.
To select a data rate, use the following command in interface configuration mode:
Configure Other Interface Support
To enhance the usefulness of IBM channel attach support, you can further define how the interface and the router interoperate by using the following commands in interface configuration mode:
Configure TCP/IP Offload Support
The following sections describe how to configure the IBM channel attach interface for TCP/IP offload support. All tasks, except for configuring other interface support, are required:
•
•
•
See the section "Select Host System Parameters" for guidelines on matching interface configuration values with host system values.
Assign an IP Address
You must assign an IP address to the channel interface so that it can communicate with other devices (or tasks) on the network. The IP address you assign to the interface must be in the same subnetwork as the hosts with which you wish to communicate.
To assign an IP address, use the following command in interface configuration mode:
ip address address mask
Assign an IP address and network mask to the selected interface.
Configure the IBM Channel Attach Interface
You must define the devices, or tasks supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCP/IP configuration. Refer to the section "Select Host System Parameters" for guidelines on matching interface configuration values with host system values.
To configure the IBM channel interface, use the following command in interface configuration mode:
offload path device-address ip-address host-name device-name host-app device-app host-link device-link [broadcast] [backup]
Define the offload parameters for this device.
See the section "CMCC Interface Configuration Examples" for samples of offload commands for different configurations.
Select a Data Rate for the Parallel Channel Interfaces
When you configure a Parallel channel attach interface, you must define a data rate of either 3 MB per second or 4.5 MB per second.
To select a data rate, use the following command in interface configuration mode:
Configure Other Interface Support
You can further define how the interface and the router interoperate. You can use the following commands in interface configuration mode to enhance the usefulness of IBM channel attach support:
Configure CSNA Support
The following sections describe how to configure the IBM channel attach interface for CSNA support. This procedures requires the configuration of both the physical and virtual interfaces. The last task, "Configure an Internal Adapter's Link Characteristics," is optional. All other tasks are required.
•
•
•
•
•
Select a Data Rate for the Parallel Channel Interfaces
When you configure a Parallel channel attach interface, you must define a data rate of either 3 MBps or 4.5 MBps.
To configure the data rate, use the following command in interface configuration mode:
Configure the Subchannel Information
To define an SNA subchannel supported by the CSNA feature, use the following command in interface configuration mode for the physical channel interface:
csna path device [maxpiu value] [time-delay value] [length-delay value]
Define the CSNA subchannel device.
Configure the Internal LAN
To configure an internal LAN, use the following commands beginning in global configuration mode:
1
interface channel slot/port
Select the virtual interface.
2
lan tokenring lan-id
Select the internal LAN interface and enter internal LAN configuration mode.
Note
Configure the Source Bridge
Select the bridging characteristics for the internal LAN. Use the following commands in internal LAN configuration mode:
source-bridge local-ring bridge-number target-ring
Select source-route bridging for the selected LAN interface.
Configure the LOCADDR Priority
Select the LOCADDR priority for the internal LAN. Use the following commands in internal LAN configuration mode:
locaddr-priority list-number
Select locaddr priority for the selected LAN interface.
Configure the SAP Priority
Select the SAP priority for the internal LAN. Use the following commands in internal LAN configuration mode:
Configure Internal Adapters
To select or configure an internal adapter, use the following command in internal LAN configuration mode:
Name the Internal Adapter
Select a name for the internal adapter. Use the following command in internal adapter configuration mode:
Configure an Internal Adapter's Link Characteristics
To configure the LLC link characteristics of an internal adapter, use the following optional commands in internal adapter configuration mode:
Configure the CMCC Adapters for IP Host Backup
The following sections describe how to configure the IBM channel attach interface for IP Host Backup support. With IP Host Backup, you can configure a backup group for each CLAW or offload device, one path at a time, or you can specify a group of IP host paths and then configure which CLAW or offload IP addresses are used with those paths. Using the second method, specifying paths, provides a shortcut to the one at a time method.
•
•
•
Configure a CLAW IP Host Backup Group
You must define the devices, or tasks, supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCPIP configuration.
To configure the CLAW IP Host Backup, use the following command in interface configuration mode:
claw path device-address ip-address host-name device-name host-app device-app [broadcast] backup
Define the CLAW parameters for this device.
See the section "Configuration Tasks" for samples of claw commands for different configurations.
Configure an Offload IP Host Backup Group
You must define the devices, or tasks supported on the interface. Some information you need to perform this task is derived from the following host system configuration files: MVSIOCP, IOCP, and the TCP/IP configuration.
To configure the Offload IP Host backup, use the following command in interface configuration mode to configure an Offload device (read and write subchannel) for communication with a mainframe TCP/IP stack in Offload mode:
See the section "Configuration Tasks" for samples of offload commands for different configurations.
Configure an IP Host Backup Group Using Paths
You can define a backup group by specifying a path, or group of paths, that are used as the IP Host Backup. Under the backup group, you can have multiple backup connections defined that all use the same IP address.
To configure the IP Host Backup using paths, use the following commands beginning in interface configuration mode:
Select Host System Parameters
This section describes how to correlate values found in the VM and MVS system I/O configuration program (IOCP) files with the fields in the claw, csna, cmpc, and offload interface configuration commands. In addition, for CLAW and Offload, you will need configuration information from the host TCP/IP application configuration file. Refer to the following IBM operating system manuals for specific IOCP configuration statement details:
•
•
Values from the Host IOCP File
When you define CLAW or offload parameters, you must supply path information and device address information to support routing on an IBM channel. The path information can be simple, in the case of a channel directly attached to a router, or more challenging when the path includes an ESCON director switch or multiple image facility support.
The path argument is a concatenation of three hexadecimal numbers that represent the values listed in .
In , two host systems connect to the ESCON director switch on paths 23 and 29. The channels both exit the switch on path 1B and attach to Router A.
Figure 172 System with an ESCON Director Switch and a Directly Attached Channel
Note that the path between Host A and Host B is dynamically switched within the ESCON director. A third host is attached directly to Router B through path 42.
The IOCP control unit statements would look similar to the following examples:
•
CNTLUNIT CUNUMBER=0001, PATH=(23), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=F•
CNTLUNIT CUNUMBER=0002, PATH=(29), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=A•
CNTLUNIT CUNUMBER=000A, PATH=(42), UNIT=SCTC, UNITADD=((00,64))The system administrator can provide you with the values. For example the ESCON director ports 15 and 19 in are the channel attachments from the ESCON director to each host. Given these values, the claw command path argument for the two channel attachments to Router A becomes:
claw 150F claw 190AThe offload command path argument for the two channel attachments to Router A becomes:
offload 150F offload 190AThe claw command path argument for the directly attached channel to Router B is easy to determine:
claw 0100Similarly, the offload command path argument for the directly attached channel to Router B is as follows:
offload 0100Next, determine the claw, csna, cmpc, or offload command device-address argument value, which is shown as 00 in the UNITADD parameter for all three devices. Based on the above example, this value can be any even value.
The UNITADD parameter in the CNTLUNIT macro of the IOCP file defines the valid range for device addresses. In the example above, a UNITADD parameter of (00,64) means that the first valid device address is 00 and the number of devices is 64 for a range of 00 to 63. In the hexadecimal notation used by channel configuration commands this translates to a range of 00 to 3F.
The claw (or offload) commands now become:
•
claw 150F 00claw 190A 00•
offload 150F 00offload 190A 00•
claw 0100 02•
offload 0100 02Values from the Host TCP/IP File
The remainder of the claw and offload command arguments are derived from the DEVICE, LINK, and HOME statements in the host TCP/IP configuration files. The csna and cmpc configuration commands include only path and device. The statements will be similar to the following:
•
DEVICE EVAL CLAW 500 VMSYSTEM C7000 NONE 20 20 4096 4096LINK EVAL1 IP 0 EVALHOME 198.92.2.12 EVAL1•
DEVICE EVAL CLAW 600 STSYSTEM C7000 NONE 20 20 4096 4096LINK EVAL1 IP 0 EVALHOME 198.92.2.13 EVAL1•
DEVICE EVAL CLAW 700 RDUSYSTM C7000 NONE 20 20 4096 4096LINK EVAL1 IP 0 EVALHOME 198.92.2.14 EVAL1The DEVICE statement lists the host-name and device-name values to use, which follows the CLAW 500 entry in the DEVICE statement.
The LINK statement links the device name, EVAL, to EVAL1. The IP address for EVAL1 appears in the HOME statement.
Based on this example, you can supply the remainder of the arguments for the sample claw commands:
•
claw 150F 00 198.92.2.12 VMSYSTEM C7000 TCPIP TCPIPclaw 190A 00 198.92.2.13 STSYSTEM C7000 TCPIP TCPIP•
claw 0100 02 198.92.2.14 RDUSYSTM C7000 TCPIP TCPIPSimilarly, the sample offload commands are as follows:
•
offload 150F 00 198.92.2.12 VMSYSTEM C7000 TCPIP TCPIP TCPIP APIoffload 190A 00 198.92.2.13 STSYSTEM C7000 TCPIP TCPIP TCPIP API•
offload 0100 02 198.92.2.14 RDUSYSTM C7000 TCPIP TCPIP TCPIP APIExample of a Derived Value
When you have a directly attached channel, the system administrator may provide you with a system IODEVICE ADDRESS that you can use. In this case, you must work backwards through the IOCP file to locate the proper device-address argument value for the claw command.
In this first example, the IODEVICE ADDRESS value is 800. Using this number, you locate the IODEVICE ADDRESS
