Chapter 16. Communication Controller for Linux on System z9 and zSeries (CCL) 285
between the CCL Engines and other devices in the network. Only a single
instance of the NDH is loaded per Linux image, regardless of how many CCL
Engines (NCPs) are running in that Linux image.
򐂰 The CCL MOSS console, accessible via a Web browser, is used to perform
many of the functions typically performed using the MOSS console of the
3745 hardware.
For more information about CCL, see Communication Controller for Linux on
System z9 and zSeries Implementation and Users Guide, SC31-6872. You can
also find CCL Technotes, white papers, and other useful information on the CCL
support Web pages at:
http://www.ibm.com/software/network/ccl/support/
16.2 Why is CCL important?
CCL is the first product other than IBM communication controller hardware to
support 3745-based program products and their broad set of functional
capabilities. In many cases, CCL provides the most transparent and functionally
equivalent option for migration from your current IBM 3745 Communication
Controllers. Of particular importance are:
򐂰 SNA Network Interconnection (SNI): CCL provides an attractive option
because it eliminates the need for coordinated interorganizational changes
that are required by every other alternative. (Discussed in 5.3.4, “SNA
Network Interconnection (SNI)” on page 167.)
򐂰 Token-ring to Ethernet migration: The CCL can handle SNA traffic on
Ethernet LAN interfaces, whereas the 3745 only supports SNA on token-ring
LANs. (Discussed in “Migrating from token ring to Ethernet” on page 117.)
򐂰 Extended Recovery Facility (XRF): Prior to the introduction of CCL, no
functional alternative existed other than to make significant application
changes. (Discussed in 5.3.7, “Extended Recovery Facility (XRF)” on
page 180.)
򐂰 Network Routing Facility (NRF): Prior to the introduction of CCL, no functional
alternative existed other than to make significant application changes.
(Discussed in 11.2.1, “Peer-to-peer connection of SNA devices (before PU
type 2.1)” on page 239.)
򐂰 X.25 NCP Packet Switching Interface (NPSI): Using X.25 over TCP/IP (XOT)
technology and CCL V1.2 NPSI program product support, your mainframe
environment can support
all of the X.25 capabilities currently supported by
NPSI in your IBM 3745 communication controllers. Routers are used to
support the actual X.25 physical interfaces, and XOT technology transports
the X.25 traffic over your TCP/IP network into your mainframes. Advantages

Get IBM Communication Controller Migration Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.