Feedback


5735-HAL IBM TCP/IP FOR MVS Version 2.2


Table of Contents

5735-HAL IBM TCP/IP FOR MVS Version 2.2
IBM U.S. Product Life Cycle Dates
Abstract
Product Positioning
Highlights
Description
Technical Description

  • Operating Environment
  • Hardware Requirements
  • Software Requirements
  • Planning Information
    Publications
    Security, Auditability, and Control
    5735-HAL - IBM TCP/IP V2 for MVS Version 2
    Abstract
    Product Positioning
    Highlights
    Description
  • Operating Environment
  • Hardware Requirements
  • Software Requirements
  • Security, Auditability, and Control
    Publications

    5735-HAL IBM TCP/IP FOR MVS Version 2.2


    IBM U.S. Product Life Cycle Dates

    
    Program                                  Marketing   Service      Replaced
    Number   VRM     Announced   Available   Withdrawn   Discontinued    By
    

    5735-HAL 2.02.1 1992/06/16 1992/06/26 1994/12/13 1998/06/30 5655-A29 5735-HAL 2.02.0 1990/09/18 1991/03/29 1994/12/13 1993/03/31 5655-A29 5735-HAL 2.00.0 1990/09/18 1991/06/28 1994/12/13 - -


    Abstract

    There Is More Than One Description for This Product

    (For IBM US, No Longer Available as of December 13, 1994)

    TCP/IP Version 2 Release 2.1 for MVS provides the user of MVS the capability to participate in a multivendor network using the TCP/IP protocol set. TCP/IP V2 R2.1 for MVS is upgraded to Program Product status demonstrating IBM's increased commitment to TCP/IP as a key networking protocol for the multivendor environment.

    TCP/IP Version 2 Release 2.1 for MVS provides significant performance, functional and usability enhancements. The addition of offloading will permit the user to process portions of the TCP/IP protocols in the IBM 3172 Interconnect Controller Model 003, thus saving the host cycles for other processing. TCP/IP Version 2 Release 2.1 extends the applicability and usability of TCP/IP on MVS by providing CICS applications with additional access to a TCP/IP network. The applications may be client or server applications. The LPR client sends data sets to be printed to LPD print servers throughout the TCP/IP network. An LPD server provides both local and remote users access to MVS-supported printers. SMF record support for TELNET and FTP will provide accounting and control information permitting the identification of users logging in for use of terminal emulation and file transfer. Users will also be able to identify the data sets accessed and, when combined with user exits, will be able to extend the security checking and control through user-supplied routines.

    TCP/IP Version 2 Release 2.1 for MVS allows the user to communicate and interoperate with other systems in a TCP/IP network. Applications include the ability to send mail, transfer files, log on to a remote host and multiple network server functions. In addition, users are provided with several options to develop unique applications for their networks. The network connection options are extended to include the IBM 3172 Interconnect Controller Model 3 for offload, CTC (3088) support, Continuously Executing Transfer Interface, IBM RS/6000 Parallel Channel Attachment, High Performance Parallel Interface (HIPPI) channel support and transferring TCP/IP packets over SNA LU6.2 conversations.


    Product Positioning

    The choice of multivendor networking protocols, TCP/IP, OSI (Open Systems Interconnect), and SNA, allows customers to connect multivendor systems in the most effective manner to meet their objectives.

    TCP/IP Version 2 Release 2.1 for MVS enhances the IBM Family of TCP/IP products which include TCP/IP on MVS, VM, OS/2, OS/400, DOS, the AIX Family, and the System/88. IBM's family of TCP/IP products provides a multivendor networking solution.

    Users of TCP/IP for MVS Version 1 should consider migrating to Version 2 to obtain network management support, expanded network connection options, CICS access to TCP/IP, LPR/LPD printer support, accounting via SMF, and other enhancements in function, security, and performance.

    Users with SNA networks can install TCP/IP on their host processors and use their existing SNA wide area backbone to transmit TCP/IP traffic between IBM TCP/IP hosts (function called SNALINK) capitalizing on the SNA investment using LU0 or LU6.2. Local Area Network (Ethernet** V2, 802.3 and IBM Token-ring) users can use the same LAN to communicate via SNA and TCP/IP to the same host system.

    TCP/IP customers who also may have OSI users in the enterprise and need to send mail and files between users of TCP/IP and OSI, can plan on using the AIX OSI Messaging and Filing/6000 program. This program provides a solution for the customer who requires a coexistence solution between the two protocols.


    Highlights

    • Improves the product status from Program Offering to Program Product

    • Improves resource utilization by offloading the lower levels of TCP/IP Protocol Processing

    • Expands access to host information and applications with the CICS to TCP/IP Socket Interface

    • Provides enhanced printing support with LPR/LPD Support

    • Increases accountability and control through the support for writing SMF record support

    • Enhances user control of security by providing User Security Exits for the FTP Server

    • Extends network connection options to include offload, IBM RS/6000 Parallel Channel Attachment, Continuously Executing Transfer Interface (CETI), High Performance Parallel Interface channel and transferring TCP/IP packets over SNA LU6.2 conversations

    Also a part of Version 2 are the following:

    • TCP/IP SNMP support for network management via IBM NetView

    • FTP Enhancements including Job Submission and support of Parallel I/O Access Method

    • Enhanced Sockets Library

    • Dynamic Routing using Routing Information Protocol

    • Domain Name Server

    • Simple Mail Transfer Protocol enhancements

    • X Window System enhancements

    • Enhanced performance and tuning options.

    • 3172 Fiber Distributed Data Interface Support

    Description

    Business Solutions

    To support the achievement of the TCP/IP customer's business objectives, TCP/IP Version 2 Release 2.1 for MVS offers business solutions to its users. These solutions help the TCP/IP user to improve the company's overall productivity. They facilitate decision making and enhance integration of business systems. Listed below are the many functions of the TCP/IP Version 2 Release 2.1 for MVS which assist a TCP/IP user to develop business solutions. TCP/IP Version 2 Release 2.1 for MVS allows the MVS user to communicate with other systems in a TCP/IP network. Applications include the ability to send mail, transfer files, log onto a remote host, and to provide multiple server functions for network users. The network protocols supported are the IBM Token-Ring, Ethernet Version 2 LAN, IEEE 802.3 LAN, DDN X.25, PDN X.25, and PC Network. Attachments to the host include the 3172 Interconnect Controller Models 001, 002 or 003 (Offloading) and the 8232 LAN Channel Station for LANS, the 37XX family of Communications Controllers for X.25 and SNA backbone transport, IBM RS/6000 Parallel Channel Attachment, High Performance Parallel Interface (HIPPI) channel, Continuously Executing Transfer Interface (CETI), and HYPERchannel** support from Network Systems Corporation.

    Network File System** (NFS) support, formerly a separate feature of the TCP/IP for MVS Version 1 product, will now be provided as part of the IBM MVS/Data Facility Product (MVS/DFP) (5665-XA3) or by DFSMS/MVS Version 1 Release 1 (5695-DF1).

    New functions in TCP/IP MVS Version 2 Release 2.1nclude:

    Offloading TCP/IP Protocol Processing

    The offloading of the processing for the TCP/UDP and lower protocols will reduce the CPU utilization on the mainframe while maintaining or improving the throughput for the host system. The TCP/IP applications executing in the host will not be affected by the offload of the TCP/IP transport protocols. The offloaded protocols will be processed in an attached IBM 3172 Interconnect Controller Model 3 running TCP/IP Version 1.2.1 for OS/2. Appropriate status information is maintained between the host and the offload device.

    CICS to TCP/IP Socket Interface

    The CICS to TCP/IP Socket Interface allow the user to develop CICS applications which interoperate with applications on processors attached to a TCP/IP network. The applications may be either client or server applications. The CICS to TCP/IP Socket Interface provides socket interfaces for both assembler and COBOL languages to use Stream (Connection Oriented) sockets. It also provides ASCII-EBCDIC conversion routines, and a Listener function to listen for and accept connection requests and start the appropriate CICS transaction to service those requests. While most CICS facilities will be available to applications written to use the Socket interface, there will be some restrictions.

    LPR/LPD Printing Support

    LPR/LPD provides client and server support for remote printing. The line printer client (LPR) sends the print data to a line printer daemon (LPD) on a specified server host and to a specified printer.

    SMF Record Support for Telnet and FTP

    The TELNET server and the FTP server provide increased accountability and control through the addition of SMF record support. The servers will provide the following:

    • TELNET Server

      The TELNET Server will provide SMF records identifying the local user id, local and remote ip addresses, date/time of log-on and log-off and the VTAM LU used for log-on.

    • FTP Server

      The FTP server provides SMF records for recording the services provided to various clients. Append, Delete/Mdelete, Get/Mget, Put/Mput and Rename commands will generate records. The FTP server can also provide information regarding failed login attempts. For further user control, an exit is provided for user written routines to get control before the SMF record is written.

    File Transfer Protocol Enhancements

    In addition to the addition of accounting information mentioned above, the File Transfer Protocol (FTP) support will provide the following enhancements in Release 2.1:

    • User Security Exits

      Four new user exits have been added to FTP. They are loaded at FTP server initialization time. If a user exit is not found, functioning will proceed as it did before the addition of this FTP User Exit feature. The four user exits are:

      • Check IP and PORT Addresses

        This exit routine is called at the initial stage of logon, or whenever the user issues an OPEN command to open a new connection. It is passed the IP and PORT addresses of the local and foreign hosts to determine if the foreign host's control connection should remain or be cancelled.

      • Check USER and PASSWORD

        This exit routine is called just after the user enters the password. The exit is passed the userid and password of the user that has just logged on. The exit has the option of rejecting the logon.

      • Check the Command

        This user exit routine is called whenever the user enters a command to execute (such as GET, PUT, or any other FTP command). The exit has the option of not permitting the execution of the command, with the user receiving a message to that effect.

      • Check use of JES

        This routine is called if the server is in filetype=jes mode and the client tries to submit a job. The exit is passed the userid and the job being submitted, and can allow or refuse the job to be submitted to the JES internal reader. For example, the exit can look for a USER= parameter on the JOB card and check it against the client's userid.

    • DB2 FTP SQL Query

      A remote TCP/IP user may submit a file containing a SQL query for DB2 and retrieve the results via FTP.

    • Removal of Server Authority

      The FTP server (SRVRFTP) will no longer require RACF operator authority.

    • SMS MGMTCLAS = NAME

      FTP supports the functions associated with the MVS/DFP Version 3 Release 1 Storage Management Subsystem (SMS) Management Class. SMS Management Class definitions created by the storage administrator, in conjunction with DFHSM or a functionally equivalent product, allow you to control space and availability management at the data set level.

    • Change Password Via FTP

      FTP will allow the user to change the RACF account password.

    Network Data Base Client/Server System

    This new component in TCP/IP Version 2 Release 2.1 for MVS can be used for relational data base systems in a TCP/IP-based internet environment, making possible interoperability among different data base systems. It is built upon Remote Procedure Call (RPC) with a client/server relationship. Its purpose is to allow any IBM RS/6000 or Sun Microsystems user or application to issue Structured Query Language (SQL) statements interactively or imbedded within the application program and query the database. This provides interoperability between these workstations and MVS's DB2* system, along with improved accessibility to data held in central SQL data bases. The clients run on the workstations and the servers run on MVS systems.

    REXEC Client Support

    Remote Execution Protocol (REXEC) client allows TCP/IP Version 2 Release 2.1 for MVS to execute a command on a foreign host and receive the results on the local host. REXEC provides automatic logon and user authentication, depending on the parameters set by the users. Only client support is provided.

    Security Feature - Kerberos

    Kerberos provides a security function that allows a client/server pair to verify the authenticity of its partner. In order to communicate with the Kerberos server, the client/server application pair must use the Kerberos libraries/Kerberos ticket-granting services. Kerberos services include

    • Kerberos application library
    • Database library
    • Database administration program
    • Administration server
    • Authentication server (Kerberos server)
    • Database management and user programs

    The Kerberos Security Feature is available for the MVS/XA/ESA environments only.

    The Kerberos server includes an encryption facility that provides a secure way of authenticating the application client/server pair. This encryption facility is based on the Data Encryption Standard (DES) algorithm. The Kerberos Feature with DES Encryption is subject to U.S. Export Licensing Controls. Questions concerning eligibility and/or U.S. licensing requirements should be directed to your local Export Regulation Coordinator/Executive (ERC/ERE).

    NCS Program Interfaces

    Network Computing System (NCS) is a programmer toolkit that allows programmers to distribute processing power to other hosts. NCS is similar to Remote Procedure Call (RPC) in that it allows a higher level of program calls. TCP/IP Version 2 Release 2.1 for MVS provides a program interface to NCS.

    Bulk Mode Socket Support

    Bulk Mode Socket Support allows an application to group multiple packets during transfer between the application address space and the TCP/IP address space. Improve performance and reduced cycle consumption will result for suitable traffic loads. This support is provided for applications using the User Datagram Protocol (UDP).

    SNALINK LU0 Single Session Support

    The TCP/IP SNALINK LU0 support is expanded to include the new capabilities of Advanced Communications Function/Network Control Program (ACF/NCP) Version 6 (5688-231) in combination optionally with the new 3745 Ethernet* LAN Adapter, enabling Internet Protocol (IP) traffic routing through a 3745 conforming to Ethernet Version 2 or IEEE 802.3 standards. SNALINK (LU0) can now communicate over a single, full-duplex session as required by NCP's connnectionless Systems Network Architecture (SNA) transport mechanism. Internet Protocol (IP) traffic can be routed locally and remotely via single sessions across existing 3745 backbone networks to other Transmission Control Protocol (TCP) applications.

    SNALINK LU6.2 Support

    SNALINK is extended to support the passing of TCP/IP datagrams among multiple hosts and/or workstations via SNA LU Type 6.2 conversations.

    IBM 3172 FDDI (Fiber Distributed Data Interface) Connectivity Support

    Provides high-speed (up to 100 Mbits per second) fiber optic local area network (LAN) connectivity through an IBM 3172 Interconnect Controller gateway to a TCP/IP for MVS system. TCP/IP Version 2 Release 2 for MVS now supports the new family of 3172s with the FDDI LAN adapter, allowing MVS attachment and TCP/IP communications to an FDDI ring. The enhancement greatly increases TCP/IP for MVS's performance potential by allowing customers to transmit TCP/IP traffic at high speeds and with exceptional reliability offered by FDDI.

    Continuously Executing Transfer Interface

    Continuously Executing Transfer Interface permits users to attach network controllers supporting this popular protocol.

    IBM RS/6000 Parallel Channel Attachment

    Provides TCP/IP Version 2 Release 2.1 for MVS support of parallel channel attachment and communications to a network governed by one or more RS/6000 devices. TCP/IP is supported across the RS/6000 Block Multiplexer Channel Adapter, which provides high-speed parallel channel attachment to ES/9000*, 3090*, and 4381 mainframes. This connectivity enhancement increases TCP/IP for MVS's performance potential through high-speed channel attachments to RS/6000-controlled LANs.

    High Performance Parallel Interface (HIPPI) MVS Driver

    TCP/IP Version 2 Release 2.1 provides access to the High Performance parallel Interface (HIPPI) which provides fast data transfer between HIPPI compatible devices and processors.

    CTC (3088) Device Driver

    The CTC Device Driver allows TCP/IP Version 2 Release 2.1 for MVS to transmit IP packets over an IBM 3088 Channel to Channel Controller to another S/370 host. This device driver uses the CTC without SNALINK and will show a substantial performance benefit over SNALINK.

    Simple Mail Transfer Protocol (SMTP) Enhancements

    With mail header customization, users can change the rules used to rewrite header addresses and specify desired header address transformations. The mail header enhancements conform to the guidelines set forth by RFC 822. Other SMTP enhancements include the ability to limit the number of simultaneously-delivered pieces of mail in order to save on system resources.

    In addition to these new functions TCP/IP Version 2 for MVS includes Mail Exchange (MX) support (RFC974) and an Asynchronous Interface to the Domain Name Server from Release 1. Mail exchange (MX) support allows the delivery of mail to TCP/IP and non-TCP/IP hosts. The asynchronous name server interface improves performance by providing multi-thread access to the domain name server, and provides a mailbox function by holding mail, for a user specified period of time, in the event the name server is unavailable. The Network Job Entry (NJE) to TCP/IP mail gateway provides a secure gateway option that allows an installation to create a data base of registered NJE users who are allowed to send mail through SMTP to a TCP/IP network recipient. Mail from or to unregistered users is rejected by the SMTP server.

    IBM 3172 Simple Network Management Protocol (SNMP) Support

    In conjunction with IBM's NetView product on MVS, this enhancement provides monitoring by the TCP/IP program of a 3172 gateway within the network, allowing the 3172 to participate in the management of TCP/IP networks. When participating in the TCP/IP environment, the 3172 is actually an extension of the MVS host node. While the 3172 is not, by itself, addressable as a TCP/IP node, it can provide network management information and status via the TCP/IP attribute support available with its Interconnect Controller Program Version 2 Release 1 (5601-433) or later. The 3172 support is activated via SNMP commands from the MVS host TCP/IP agent, which requests 3172 information based on input from a NetView operator or an operator from some other node in the TCP/IP network. The NetView operator, via the SNMP monitor in TCP/IP Version 2 for MVS, manages TCP/IP agents in the network and acts as a focal point for network management. The SNMP agent responds to commands from an SNMP monitor in the network and forwards both solicited and unsolicited information back to designated monitors. With this release, requests for information from the SNMP agent on MVS are recognized by the 3172, and the 3172 responds via its TCP/IP attribute support.

    Domain Name Server Enhancements

    This release includes two new name resolution utilities, DIG and NSLOOKUP. These complement prior-release enhancements made for performance and usability, such as SMSG support, User Datagram Protocol recursion, intermediary caching, and "zone transfer" (transferring a domain from a remote authoritative name server).

    MOTIF Update to Version 1.1.2

    As in Release 1 of TCP/IP Version 2 for MVS, an application development toolkit based on OSF/Motif from the Open Software Foundation, Inc. is also supported. This toolkit enables the application programmer to evoke high quality graphic designs from the application program. Included in TCP/IP Version 2 Release 2.1 for MVS is the latest level of Motif/X, Release 1.1.2.

    Common SMP/E Zone

    IBM TCP/IP Version 2 Release 2.1 complies with IBM naming conventions and will not require a unique SMP/E zone as previous versions did.

    The following functions were contained originally in Release 1 of TCP/IP Version 2 for MVS and continue to be supported in Release 2.1:

    • TCP/IP Network Management via NetView

      TCP/IP Version 2 for MVS provides both Simple Network Management Protocol (SNMP) monitor and agent support. This product, via IBM's NetView product, can be used to manage other TCP/IP systems which provide SNMP agent support. Conversely, TCP/IP Version 2 for MVS provides agent support that can be managed by other SNMP products. The IBM TCP/IP product family also provides both SNMP monitor and agent support in TCP/IP Version 2 Release 2.1 for VM and AIX Netview/6000, and provides SNMP agent support in TCP/IP Versions 1.0, 1.1, 1.2, and 1.2.1 for OS/2. The SNMP monitor provides and uses a NetView command processor as the user(monitor) interface for TCP/IP Version 2 Release 2.1 for MVS. The NetView operator, via the SNMP monitor in TCP/IP Version 2.1 for MVS, manages TCP/IP agents in the network.

      The SNMP agent function responds to the SNMP commands from an SNMP monitor in the network, and forwards both solicited and unsolicited information back to designated monitors.

      The following TCP/IP network management functions are provided:

      • Data is defined by the Management Information Base (MIB) and represents information such as message counts and transmission error statistics. Supported MIB groups include system, interfaces, address translation, Internet Protocols, Internet Control Message Protocol, TCP and User Datagram Protocol.

      • Additionally, a subset of MIB2 enhancements is supported by the MVS agent.

      • Commands provided GET, GETNEXT and SET

      • Asynchronous events (TRAPS) directed from any SNMP agent, are forwarded from MVS Version 2 SNMP to NetView. Using NetView's message automation capabilities, these traps can then be converted and displayed via the Hardware Monitor component of NetView. TRAPS from designated sources may optionally be filtered by the MVS Version 2 SNMP monitor support before they are passed to NetView.

      • The Distributed Program Interface is provided and allows the user to extend the MIB through user defined variables.

        NetView applications can be written to automate and/or customize the gathering and presentation of the TCP/IP network management data. A set of sample NetView applications, written in CLIST language or REXX, will be provided to enhance the usability of the SNMP monitor interface. These applications will provide a base upon which users can build and customize to meet their individual installation requirements. The CLISTs samples are supplied "as is" with no service implied. The SNMP for MVS support provided is equivalent to that announced in the TCP/IP Version 2 for VM.

    • Job Submission via FTP

      FTP can be utilized to submit jobs to the MVS internal reader. This enables any user with FTP access to submit jobs to MVS from a remote system using a TCP/IP network. This FTP feature allows job submission to be automated.

    • FTP support of PIOAM (5685-137)

      The MVS Parallel I/O Access Method is a set of subroutines providing high speed access for both sequential and random accessing of user data stored as PIOAM datasets on DASD. This high performance access method supports 'striping', the ability to write a file across multiple DASD devices in parallel. This technique is especially suited to the engineering, scientific, and real time computing environments. PIOAM is available to the MVS user as a separate product and can also be used by FORTRAN.

    • Enhanced Socket Library

      TCP/IP Version 2 for MVS has a more extensive socket library than provided by Version 1. This extended Socket Library support, based on Berkeley Socket Library**, BSD 4.3*, removes the requirement for the PASCAL Runtime library since all sockets are written to the C language interface. This support facilitates the port of UNIX** applications to the System/370*.

    • Remote Procedure Call Libraries.

      Remote Procedure Call support provides a more sophisticated interface which allows users to write distributed applications which execute procedures on a remote system. This product now provides a complete RPC environment for SUN** Remote Procedure Call (RPC) (including the Portmapper** function). RPC uses the XDR data represent which allows data to be exchanged between machines of dissimilar architecture (e.g., different byte ordering). RPCGEN is available to aid programmers in developing their applications.

    • Dynamic Routing using RIP

      The 'RouteD' server is now provided, enhancing the TCP/IP for MVS routing function by using Routing Information Protocol (RIP), which listens to routing information and dynamically updates its routing tables accordingly. This helps to automate the administration of routing tables, and is a transparent response to changing network topology.

    • Domain Name Server

      TCP/IP Version 2 for MVS provides a full functioned Domain Name Server which allows users to operate in primary, secondary and caching-only mode. Primary and secondary modes require DB2. The name server also includes support for UDP Recursion; Intermediary, Standard Query, and Negative Caching; as well as Zone Transfer.

      UDP Recursion: TCP/IP V2 for MVS now uses User Datagram Protocol between Domain Name Servers. An option is provided to use the Transmission Control Protocol for retry requests if a response does not come back from the remote domain name server.

      Intermediary Caching: The TCP/IP Version 2 for MVS name server will cache resource records defining remote name servers. Subsequent queries will go directly to these name servers for query resolution, rather than always going to the same default name server.

      Standard Query Caching: Provides the ability for the Systems Administrator to specify the size of the table which contains the most frequently used queries which are held in the cache for higher speed name resolution.

      Negative Caching: The TCP/IP Version 2 for MVS name server will cache query responses containing no answers from an authoritative name server. Subsequent queries will quickly return this negatively cached response.

      Zone Transfer: The TCP/IP Version 2 for MVS name server is capable of making a local copy of the domain data from a remote authoritative name server. Once the MVS name server has the domain data, it becomes authoritative for that domain as well, eliminating the need to access the remote name server. This is referred to as a 'secondary' name server for a domain.

    • National Language Support (SMTP and FTP only)

      National Language support is provided for Single Byte Character Set (SBCS) and Double Byte Character Set (DBCS) for Japanese and Korean languages. This supports conversion function from JIS Kanji and Korea Standard Hangul to IBM DBCS code. Machine Readable Image Translation, Enabling or Publication Translation are not included in this level of support.

    • X Window System Support

      The X Window System client support offered by TCP/IP Version 2 for MVS has been enhanced to the current release level (X11.4). An application development toolkit based on OSF/Motif from the Open Software Foundation Inc. is also supported and provided in this product. This toolkit enables the application programmer to generate high quality two- dimensional graphic design output from the application program.

    • Graphics support with the X Window System

      The TSO user can run typical S/370 GDDM applications with X Window System Version 11 server machines such as AIX/PS2, AIX/RT, RISC/System 6000 using AIX V3, X Terminal, SUN, Apollo**, or other OEM UNIX environments. This now extends the access to the S/370 GDDM applications to the non-System/370 environments.

      In general, applications using GDDM/MVS Version 2 Release 2.1 and later are supported. Some exceptions are applications using multiple instances of GDDM or operator windows. For further details on limitations, refer to the product publications.

    • 3172 FDDI Support

      See Programming Requirements under the Operating Environment in the Technical Information section for specifics.

    User Productivity:

    • Performance and tuning enhancements.

      TCP/IP Version 2 for MVS can now define packet size and communication window sizes, up to a maximum of 32K Bytes each. This allows improved flexibility in tuning network performance on those network devices and systems which can handle the increased sizes. This product incorporates the performance enhancements made to TCP/IP for MVS Version 1, which included improved check sum processing and other storage utilization improvements. In addition, TCP header prediction is provided, which can potentially save cycles processing predictable header patterns.

    Standards

    IBM is committed to industry standards. The Internet protocol suite is still evolving through the mechanism of Request for Comments (RFC). New protocols are being designed and implemented by researchers, and are brought to the attention of the Internet community in the form of an RFC. Some of them are so useful that they become a "recommended" protocol, that is, all future implementations of TCP/IP are recommended to implement this particular function or protocol. These become the "de facto" standards, by which the TCP/IP protocol suite is built upon. A list of the RFCs that TCP/IP version 2 for MVS is based on is provided as an appendix in each of the manuals shipped with the product.

    SHARE**

    In support of the SHARE TCP/IP Committee requirements, TCP/IP Version 2 for MVS offers a larger Maximum Transmission Unit Packet size -- up to a maximum of 32K Bytes each.

    TCP/IP to OSI Transition

    IBM supports TCP/IP to OSI transition.

    Systems Management

    TCP/IP Version 2 for MVS provides Simple Network Management Protocol support permitting TCP/IP for MVS to communicate with NetView allowing it to act as a "focal point" for network management of TCP/IP networks. TCP/IP Version 2 for MVS can monitor/control appropriate resources to attain business objectives.

    TCP/IP Version 2 for MVS provides monitoring support and in those cases where agent nodes support the SET function, IBM's TCP/IP Version 2 for MVS with NetView can manage those nodes within the parameters of the SET function supported.

    Customer Responsibilities

    Customer responsibilities include the following:

    • Provide suitable hardware and software environments
    • Keep backup copies of the programs, authorized user lists and other required data
    • Provide administrative support for the enrollment of new users and maintenance of the TCP/IP directories.

    Technical Description

    Operating Environment

    This product uses only the existing interfaces of the other System/370 products to which it attaches.

    Hardware Requirements

    This licensed program is designed to operate on any IBM System/370 (308X, 3090,or 43XX) or S/390 processor that supports MVS/SP Versions 1, 2, 3, or 4 (see programming requirements section). The machine requirements are:

    • 200KB (KB equals 1024 bytes) of main storage to be permanently used while TCP/IP Version 2 for MVS is running@

    • A virtual storage size of at least one megabyte for a TSO session to execute the client commands provided with TCP/IP V2 for MVS*

    • 500 MB (MB equals 1 million bytes) of direct access storage* to hold the libraries and data:
      • base = 165MB
      • source = 335MB

    • Sufficient paging space* to hold at least 10MB of virtual storage

    • One tape/cartridge drive for installing IBM TCP/IP Version 2 for MVS

    • A System/370 channel for attachment of one or more of the following:
      • 8232 LAN Channel Station
      • 3172 Interconnect Controller
      • The family of IBM 37XX Communication Controllers for X.25 support and SNA backbone support or IBM 3745 Ethernet LAN Adapter
      • High Performance Parallel Interface (HIPPI)
      • NSC IBM channel adapter for NSC HYPERchannel
      • A network attachment device using the Continuously Executing Transfer Interface.

    • One or more terminals using IBM 3270 protocols for maintenance functions.

    @ The amount of storage required by TCP/IP Version 2 of MVS is dependent on the TCP/IP configuration options. Refer to the "TCP/IP Version 2 for MVS: Planning and Customization" (SC31-6085) for further details.

    Attachment of TCP/IP Version 2 for MVS to the network requires one of the following network processors and/or associated components described below:

    IBM 3172 Interconnect Controller

    • IBM 3172 Interconnect Controller Model 001 or Model 002 or Model 003

    • IBM Interconnect Controller Program (5601-400 or 5601-433 or 5621-425)

    • One of the following adapters or a combination of the following:
      • 3172 Interconnect Controller Token-Ring Adapter (#2210)
      • 3172 Interconnect Controller Ethernet Adapter (#2220)
      • 3172 Interconnect Controller PC Network Baseband Adapter/A (#2270)
      • 3172 Interconnect Controller PC Network Adapter II/A (#2271)
      • 3172 Interconnect Controller PC Network Adapter II/A Freq 2 (#2272)
      • 3172 Interconnect Controller PC Network Adapter II/A Freq 3 (#2273)
      • 3172 Interconnect Controller FDDI A Station Adapter (#2250)
      • 3172 Interconnect Controller Token-Ring Adapter (#2215)
      • 3172 Interconnect Controller Ethernet Adapter (#2225)

    • Standard System/370 I/O Channel Interface Cable

    Support for the 3172 Interconnect Controller FDDI capability, is provided in TCP/IP Version 2 Release 2.1 for MVS.

    TCP/IP Offload to IBM 3172 Interconnect Controller Model 003

    • IBM 3172 Interconnect Controller Model 003

    • and its required software:
      • OS/2 Version 2.1 (61G0900) for the 3172 Interconnect Controller Model 3
      • TCP/IP Version 2.0 for OS/2 (65G1220) for the 3172 Interconnect Controller Model 3
      • Offload diskette for OS/2

    • One of the following adapters or a combination of the following:
      • 3172 Interconnect Controller Token-Ring Adapter (#2215)
      • 3172 Interconnect Controller Ethernet Adapter (#2225)
      • 3172 Interconnect Controller FDDI A Station Adapter (#2300)

    • Standard System/370 I/O Interface cable

    IBM 8232 LAN Channel Station:

    • IBM 8232 LAN Channel Station Model 001 or 002
    • One or more adapters for Token-Ring, PC Network, or Ethernet
    • Standard System/370 I/O Interface cable

    High Performance Parallel Interface (HIPPI):

    • The following Hardware RPQs are supported:
      • 8P1347
      • 8P1348
      • 8P1353
      • 8P1354

    • Software RPQ P88039

    IBM RS/6000 Parallel Channel Attachment requires the following:

    • IBM RS/6000 with the Block Multiplexer Channel Adapter

    • AIX Version 3 (5756-030), or later

    • Standard System/370 I/O Channel Interface Cable.

    IBM 37XX Communication Controller Interface

    • IBM 3720 or 3745 Communication Controller for X.25 or SNALINK

    • IBM 3745 Communication Controller with Ethernet LAN Adapter (for Models 210, 310, 410, or 610), available September 25, 1992

    IBM 3088 Multisystem Channel Communication Unit

    • The IBM 3088 is supported via the new CTC support.

    HYPERchannel A220 Processor Adapter 42990007

    • TCP/IP for MVS supports the HYPERchannel Series A devices (and HYPERchannel Series DX devices which are functioning as Series A devices). For additional information, see the appropriate Network Systems Corporation documentation.

    Software Requirements

    IBM TCP/IP Version 2 for MVS is designed to operate with one of the the following:

    • MVS/SP (MVS/370) Version 1 Release 3.5, or later
    • MVS/SP (MVS/XA) Version 2 Release 1.3, or later
    • MVS/SP (MVS/ESA) Version 3 Release 1.0
    • MVS/SP Version 4.1, or later

    TSO is required for interactive use of all client commands. TSO/E Release 1.3 or later is required for users of SMTPNOTE and TELNET. VTAM Version 3 Release 2 or later is required for the TELNET (both 3270 and line mode) server and SNALINK.

    SNMP Client support requires NetView Version 1 Release 3 or later. Since NetView Version 1 Release 3 does not support MVS/370, SNMP Client support is available on MVS/XA and MVS/ESA and is not available on MVS/370. SNMP agent does not require NetView, and is available on all supported versions of MVS.

    Customers who wish to do X.25 communications will require the corresponding levels of VTAM and NCP that support NPSI. See the VTAM and NCP publications for specific details.

    Customers who wish to use SNALINK LU0 Single Session support or to make use of the new 3745 Ethernet LAN Adapter will require Advanced Communication Function/ Network Control Program (ACF/NCP) Version 6 (5688-231) available in 9/92.

    Customers may choose to run TCP/IP Version 2 Release 2.1 for MVS in either 24 bit mode or 31 bit mode. All optional features must be ordered in the same mode, i.e., all must be 24 bit or all must be 31 bit. The following considerations apply:

    • 24 bit mode
      • This version may be used on MVS/370, MVS/XA, or MVS/ESA.
      • The Pascal Run Time Library is not required
      • Buffers and number of sessions will be restricted since only 16MB is available.
      • CICS to TCP/IP Socket Interface will not be available in a 24 bit version.
      • The Kerberos Security Feature is not available.
      • SNMP Client support is not available for MVS/370. The 31 bit version may not be used with a 24 bit base.
      • Order the MVS/370 options for TCP/IP Version 2 Release 2.1 for MVS regardless of the version of MVS in use (e.g., Feature codes #5851 or 5852 for base tape).
      • Note that this is the last release for which 24 bit mode is planned.

    • 31 bit mode
      • This version requires MVS/XA or MVS/ESA.
      • The Pascal Run Time Library is required.
      • Memory above the 16MB line will be used, permitting more and larger buffers and more sessions.
      • CICS to TCP/IP Socket Interface will be available in 31 bit mode.
      • The Kerberos Security Feature is available.
      • Order the XA/ESA version of TCP/IP Version 2 Release 2.1 for MVS (e.g., Feature codes #5861 or 5862 for base tape).

    TCP/IP Version 2 for MVS functions written in C Language, require

    • IBM C/370* Runtime Library V2.1 or C/370* Library V2.2 (5688-188) or
    • LE/370 V1.2 or LE/370 V1.3 (5688-198)

    These functions include:

    • C sample programs
    • Domain Name Server
    • Remote Procedure Call (RPC)
    • Network Computing Systems (NCS)
    • X Window System
    • SNMP Client and Server
    • Portmapper
    • RPCinfo
    • Kerberos Services
    • RouteD Server
    • Network Data Base Server

    TCP/IP Version 2 for MVS will run on an MVS/370 system, although the C/370 Runtime Library is not supported on MVS/370. The TCP/IP for MVS functions which require the C/370 Runtime Library, listed above, may behave unpredictably when running on an MVS/370 system.

    The optional support software required is as follows:

    • To run CICS to TCP/IP Socket Interface
      • CICS Version 2.1 or later is supported.

    • To run GDDM/X:
      • GDDM/MVS Version 2 Release 2 or later (5665-356)

    • For Domain Nameserver:
      • IBM C/370 Library program product (5688-039) or IBM C/370 Library Version 2 (5688-187)
      • In Authoritative (Primary or Secondary) mode - DB2 Version 2 Release 2 (5665-DB2)

    • For FTP use of PIOAM
      • PIOAM (5685-137)
      • Support for PIOAM in the MVS/370 environment is not provided

    • For file access protection with FTP:
      • RACF (5740-XXH) or equivalent

    • For Network File System support, now a part of MVS/DFP:
      • In the MVS/XA environment MVS/Data Facility Product (MVS/DFP) (5665-XA3) Version 3 Release 1
      • In the MVS/ESA environment MVS/Data Facility Product (MVS/DFP) (5665-XA3) Version 3 Release 2 or Release 3 or DFSMS/MVS Version 1 Release 1 (5695-DF1)
      • Network File System support is not provided by MVS/DFP for the MVS/370 environment

    Application Program Services Requirements: Customer-written programs that interface to:

    • X Window System client
    • Remote Procedure Call
    • TCP protocol boundary
    • UDP protocol boundary
    • DPI
    • IP

    If written in C, require the following:

    • IBM C/370 Compiler V2 (5688-187) or IBM AD/Cycle C/370 Compiler (5688-216) and one of the libraries supported by that compiler.

    Customer-written programs that interface to:

    • TCP Protocol boundary

    • UDP Protocol boundary

    • IP Protocol boundary

    If written in Pascal, require the following:

    • IBM VS Pascal Compiler and Library (5668-767)

    Compatibility

    An existing offering, TCP/IP for MVS Version 1 (5685-061), provides a subset of the function in TCP/IP Version 2 for MVS (5735-HAL). These two programs are compatible with each other and users moving from the existing offering will have new functions, including network management using NetView. Network File System support is no longer offered with this product. It must be ordered separately if required for file server support. Network File System is now provided as part of the Data Facility Product (see programming requirements section.)

    Customers with applications, which were written using the C language program product in TCP/IP for MVS Version 1 to the socket programming interface, must recompile these applications and may need to change their code in order to operate using TCP/IP Version 2 for MVS. Configuration options may require that TCP/IP Version 2 for MVS be run in 31 bit mode. For further details on limitations, refer to the product publications.


    Planning Information

    Customer Responsibilities

    Not available.


    Publications

    A memo, program directory, and one copy of the following publications are supplied automatically with the basic machine-readable material:

    • GC31-6086 IBM TCP/IP Version 2 Release 2 for MVS: License Program Specification
    • SC31-6085 IBM TCP/IP Version 2 Release 2 for MVS: Planning and Customization
    • SC31-6088 IBM TCP/IP Version 2 Release 2 for MVS: Users' Guide
    • SC31-6142 IBM TCP/IP Version 2 Release 2 for MVS: Messages and Codes
    • SC31-6087 IBM TCP/IP Version 2 Release 2 for MVS: Programmer's Reference
    • SX75-0082 IBM TCP/IP Version 2 Release 2 for MVS: Quick Reference Guide
    • LY43-0013 TCP/IP Version 2 for VM and MVS: Diagnosis Guide
    • GC31-7015 CICS to TCP/IP Socket Interface User's Guide

    For a current list of publications, refer to the appropriate publications option on your respective HONE system, or contact your local IBM representative.


    Security, Auditability, and Control

    IBM TCP/IP Version 2 for MVS has the security and auditability features of the MVS Operating System.

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    5735-HAL - IBM TCP/IP V2 for MVS Version 2


    Abstract

    TCP/IP Version 2 for MVS provides the user of MVS the capability to participate in a multivendor network using the TCP/IP protocol set.

    TCP/IP V2 for MVS provides significant enhanced function. The addition of Simple Network Management Protocol (SNMP) support permits TCP/IP V2 for MVS to communicate with NetView* allowing it to act as a "focal point" for network management of TCP/IP networks as well as existing SNA NetView managed networks. File Transfer Protocol (FTP) enhancements include support of PIOAM and job submission via FTP. Improvements to the sockets library and the addition of an application development toolkit, based on OSF/Motif** from the Open Software Foundation, Inc., to the X Window System** client support, are other key enhancements.


    Product Positioning

    The choice of multivendor networking protocols, TCP/IP, OSI (Open Systems Interconnect), and SNA, allows customers to connect multivendor systems in the most effective manner to meet their objectives.

    TCP/IP Version 2 for MVS enhances the IBM Family of TCP/IP products, which include TCP/IP on MVS, VM, OS/2, OS/400, DOS, the AIX Family, and the System/88. IBM's family of TCP/IP products provides a multivendor networking solution.

    Users of TCP/IP for MVS Version 1 should consider migrating to Version 2 to obtain network management support and enhancements in function, security (via the secure gateway), and performance.

    Users with SNA networks can install TCP/IP on their host processors and use their existing SNA wide area backbone to transmit TCP/IP traffic between IBM TCP/IP hosts (function called SNALINK) capitalizing on the SNA investment. Local Area Network (Ethernet** V2, 802.3 and IBM Token-Ring) users can use the same LAN to communicate via SNA and TCP/IP to the same host system.

    TCP/IP customers who also may have OSI users in the enterprise and need to send mail and files between users of TCP/IP and OSI, can plan on using the AIX OSI Messaging and Filing/6000 program. This program provides a solution for the customer who requires a coexistence solution between the two protocols.


    Highlights

    • TCP/IP SNMP support for network management via IBM NetView

    • FTP Enhancements including Job Submission and support of Parallel I/O Access Method

    • Enhanced Sockets Library

    • Dynamic Routing using Routing Information Protocol

    • Domain Name Server

    • Simple Mail Transfer Protocol enhancements

    • X Window System enhancements

    • Enhanced performance and tuning options.

    • 3172 Fiber Distributed Data Interface Support

    Description

    Business Solutions

    To support the achievement of the TCP/IP customer's business objectives, TCP/IP Version 2 for MVS offers business solutions to its users. These solutions help the TCP/IP user to improve the company's overall productivity. They facilitate decision making and enhance integration of business systems. Listed below are the many functions of the TCP/IP Version 2 for MVS which assist a TCP/IP user to develop business solutions.

    TCP/IP Version 2 for MVS allows the MVS user to communicate with other systems in a TCP/IP network. Applications include the ability to send mail, transfer files, log onto a remote host, and to provide multiple server functions for network users. The network protocols supported are the IBM Token-Ring, Ethernet Version 2 LAN, IEEE 802.3 LAN, DDN X.25, PDN X.25 and PC Network. Attachments to the host include the 3172 Interconnect Controller and the 8232 LAN Channel Station for LANS, the 37XX family of Communications Controllers for X.25 and SNA backbone transport, and HYPERchannel** support from Network Systems Corporation.

    Network File System** (NFS) support , formerly a separate feature of the TCP/IP for MVS Version 1 product, will now be provided as part of the IBM MVS/Data Facility Product (MVS/DFP) (5665-XA3).

    New functions in TCP/IP MVS Version 2 include:

    • TCP/IP Network Management via NetView

      TCP/IP Version 2 for MVS provides both Simple Network Management Protocol (SNMP) monitor and agent support. This product, via IBM's NetView product, can be used to manage other TCP/IP systems which provide SNMP agent support. Conversely, TCP/IP Version 2 for MVS provides agent support that can be managed by other SNMP products. The IBM TCP/IP product family also provides both SNMP monitor and agent support in TCP/IP Version 2 for VM and AIX Network Management/6000, and provides SNMP agent support in TCP/IP Versions 1.0 and 1.1 for OS/2. The SNMP monitor provides and uses a NetView command processor as the user (monitor) interface for TCP/IP Version 2 for MVS. The NetView operator, via the SNMP monitor in TCP/IP Version 2 for MVS, manages TCP/IP agents in the network.

      The SNMP agent function responds to the SNMP commands from an SNMP monitor in the network, and forwards both solicited and unsolicited information back to designated monitors.

    The following TCP/IP network management functions are provided:

    • Data is defined by the Management Information Base (MIB) and represents information such as message counts and transmission error statistics. Supported MIB groups include system, interfaces, address translation, Internet Protocols, Internet Control Message Protocol, TCP and User Datagram Protocol.

    • Additionally, a subset of MIB2 enhancements is supported by the MVS agent.

    • Commands provided GET, GETNEXT and SET

    • Asynchronous events (TRAPS) directed from any SNMP agent, are forwarded from MVS Version 2 SNMP to NetView. Using NetView's message automation capabilities, these traps can then be converted and displayed via the Hardware Monitor component of NetView. TRAPS from designated sources may optionally be filtered by the MVS Version 2 SNMP monitor support before they are passed to NetView.

    • The Distributed Program Interface is provided and allows the user to extend the MIB through user defined variables.

      NetView applications, called CLISTS, can be written to automate and/or customize the gathering and presentation of the TCP/IP network management data. A set of sample NetView CLISTs will be provided to enhance the usability of the SNMP monitor interface. These CLISTs will provide a base upon which users can build and customize to meet their individual installation requirements. The CLISTs samples are supplied "as is" with no service implied. The SNMP for MVS support provided is equivalent to that announced in the TCP/IP Version 2 for VM.

    • Job Submission via FTP

      FTP can be utilized to submit jobs to the MVS internal reader. This enables any user with FTP access to submit jobs to MVS from a remote system using a TCP/IP network. This FTP feature allows job submission to be automated.

    • FTP support of PIOAM (5685-137)

      The MVS Parallel I/O Access Method is a set of subroutines providing high speed access for both sequential and random accessing of user data stored as PIOAM datasets on DASD. This high performance access method supports 'striping', the ability to write a file across multiple DASD devices in parallel. This technique is especially suited to the engineering, scientific, and real time computing environments. PIOAM is available to the MVS user as a separate product and can also be used by FORTRAN.

    • Enhanced Socket Library

      TCP/IP Version 2 for MVS has a more extensive socket library than provided by Version 1. This extended Socket Library support, based on Berkeley Socket Library**, BSD 4.3*, removes the requirement for the PASCAL Runtime library since all sockets are written to the C language interface. This support facilitates the port of UNIX** applications to the System/370*.

    • Remote Procedure Call Libraries.

      Remote Procedure Call support provides a more sophisticated interface which allows users to write distributed applications which execute procedures on a remote system. This product now provides a complete RPC environment for SUN** Remote Procedure Call (RPC) (including the Portmapper** function). RPC uses the XDR data represent which allows data to be exchanged between machines of dissimilar architecture (e.g., different byte ordering). RPCGEN is available to aid programmers in developing their applications.

    • Dynamic Routing using RIP

      The 'routed' server is now provided, enhancing the TCP/IP for MVS routing function by using Routing Information Protocol (RIP), which listens to routing information and dynamically updates its routing tables accordingly. This helps to automate the administration of routing tables, and is a transparent response to changing network topology.

    • Domain Name Server

      This release provides support for the "caching-only" mode of the Domain Name Server.

      Information has been added to assist in the ordering of this product for specific MVS environments (MVS/370, MVS/XA and MVS/ESA). (See the Ordering Information section for specifics).

      The media option of 9/1600 Magnetic Tape is no longer available. Marketing representative should check the backlog of orders for TCP/IP Version 2 for MVS (5735-HAL). Any customers with a system on order that includes the 9/1600 BPI Tape option, Feature Number 5850 or 5880, should be contacted and informed that this media option is no longer available. Customers should be informed that they may select either of the two remaining media feature, 9/6250 Magnetic Tape and the 3480 Magnetic Tape Cartridge and their orders revised accordingly.

      TCP/IP Version 2 for MVS provides a full functioned Domain Name Server which allows users to operate in primary, secondary and caching-only mode. Primary and secondary modes require DB2. The name server also includes support for UDP Recursion; Intermediary, Standard Query, and Negative Caching; as well as Zone Transfer.

      UDP Recursion: TCP/IP V2 for MVS now uses User Datagram Protocol between Domain Name Servers. An option is provided to use the Transmission Control Protocol for retry requests if a response does not come back from the remote domain name server.

      Intermediary Caching: The TCP/IP Version 2 for MVS name server will cache resource records defining remote name servers. Subsequent queries will go directly to these name servers for query resolution, rather than always going to the same default name server.

      Standard Query Caching: Provides the ability for the Systems Administrator to specify the size of the table which contains the most frequently used queries which are held in the cache for higher speed name resolution.

      Negative Caching: The TCP/IP Version 2 for MVS name server will cache query responses containing no answers from an authoritative name server. Subsequent queries will quickly return a negative answer based on the query responses held in the cache.

      Zone Transfer: The TCP/IP Version 2 for MVS name server is capable of making a local copy of the domain data from a remote authoritative name server. Once the MVS name server has the domain data, it becomes authoritative for that domain as well, eliminating the need to access the remote name server. This is referred to as a 'secondary' name server for a domain.

    • SMTP Enhancements

      TCP/IP Version 2 for MVS now includes Mail Exchange (MX) support (RFC974) and an Asynchronous Interface to the Domain Name Server. Mail exchange (MX) support allows the delivery of mail to TCP/IP and non-TCP/IP hosts The asynchronous name server interface improves performance by providing multi-thread access to the domain name server, and provides a mailbox function by holding mail, for a user specified period of time, in the event the name server is unavailable. The Network Job Entry (NJE) to TCP/IP mail gateway provides a secure gateway option that allows an installation to create a data base of registered NJE users who are allowed to send mail through SMTP to a TCP/IP network recipient. Mail from or to unregistered users is rejected by the SMTP server.

    • National Language Support (SMTP and FTP only)

      National Language support is provided for Single Byte Character Set (SBCS) and Double Byte Character Set (DBCS) for Japanese and Korean languages. This supports conversion function from JIS Kanji and Korea Standard Hangeul to IBM DBCS code. Machine Readable Image Translation, Enabling or Publication Translation are not included in this level of support.

    • X Window System Support

      The X Window System client support offered by TCP/IP Version 2 for MVS has been enhanced to the current release level (X11.4). An application development toolkit based on OSF/Motif from the Open Software Foundation Inc. is also supported and provided in this product. This toolkit enables the application programmer to generate high quality two- dimensional graphic design output from the application program.

    • Graphics support with the X Window System

      The TSO user can run typical S/370 GDDM applications with X Window System Version 11 server machines such as AIX/PS2, AIX/RT, RISC/System 6000 using AIX V3, X Terminal, SUN, Apollo(8), or other OEM UNIX environments. This now extends the access to the S/370 GDDM applications to the non-System/370 environments.

      In general, applications using GDDM/MVS Version 2 Release 2 and later are supported. Some exceptions are applications using multiple instances of GDDM or operator windows. For further details on limitations, refer to the product publications.

    • 3172 FDDI Support

      See Programming Requirements under the Specified Operating Environment in the Technical Information section for specifics.

    User Productivity:

    • Performance and tuning enhancements.

      TCP/IP Version 2 for MVS can now define packet size and communication window sizes, up to a maximum of 32K Bytes each. This allows improved flexibility in tuning network performance on those network devices and systems which can handle the increased sizes. This product incorporates the performance enhancements made to TCP/IP for MVS Version 1, which included improved check sum processing and other storage utilization improvements. In addition, TCP header prediction is provided, which can potentially save cycles processing predictable header patterns.

    Standards

    IBM is committed to industry standards. The Internet protocol suite is still evolving through the mechanism of Request for Comments (RFC). New protocols are being designed and implemented by researchers, and are brought to the attention of the Internet community in the form of an RFC. Some of them are so useful that they become a "recommended" protocol, that is, all future implementations of TCP/IP are recommended to implement this particular function or protocol. These become the "de facto" standards, by which the TCP/IP protocol suite is built upon. A list of the RFCs that TCP/IP version 2 for MVS is based on is provided as an appendix in each of the manuals shipped with the product.

    SHARE*

    In support of the SHARE TCP/IP Committee requirements, TCP/IP Version 2 for MVS offers a larger Maximum Transmission Unit Packet size -- up to a maximum of 32K Bytes each.

    TCP/IP to OSI Transition

    IBM supports TCP/IP to OSI transition.

    Systems Management

    TCP/IP Version 2 for MVS provides Simple Network Management Protocol support permitting TCP/IP for MVS to communicate with NetView allowing it to act as a "focal point" for network management of TCP/IP networks. TCP/IP Version 2 for MVS can monitor/control appropriate resources to attain business objectives.

    TCP/IP Version 2 for MVS provides monitoring support and in those cases where agent nodes support the SET function, IBM's TCP/IP Version 2 for MVS with NetView can manage those nodes within the parameters of the SET function supported.

    Customer Responsibilities

    Customer responsibilities include the following:

    • Provide suitable hardware and software environments
    • Keep backup copies of the programs, authorized user lists and other required data
    • Provide administrative support for the enrollment of new users and maintenance of the TCP/IP directories.

    Operating Environment

    This product uses only the existing interfaces of the other System/370 products to which it attaches.

    Hardware Requirements

    This licensed program is designed to operate on any IBM System/370 (308X, 3090,or 43XX) or S/390 processor that supports MVS/SP Versions 1, 2, 3,or 4 (see programming requirements section). The machine requirements are:

    • 200KB (KB equals 1024 bytes) of main storage to be permanently used while TCP/IP Version 2 for MVS is running*

    • A virtual storage size of at least one megabyte for a TSO session to execute the client commands provided with TCP/IP V2 for MVS*

    • 500 MB (MB equals 1 million bytes) of direct access storage* to hold the libraries and data:
      • base = 165MB
      • source = 335MB

    • Sufficient paging space* to hold at least 10MB of virtual storage

    • One tape/cartridge drive for installing IBM TCP/IP Version 2 for MVS

    • A System/370 channel for attachment of one or more of the following:
      • 8232 LAN Channel Station
      • 3172 Interconnect Controller
      • Family of IBM 37XX Communication Controllers for X.25 support and SNA backbone support
      • NSC IBM channel adapter for NSC HYPERchannel

    • One or more terminals using IBM 3270 protocols for maintenance functions.

    * The amount of storage required by TCP/IP Version 2 of MVS is dependent on the TCP/IP configuration options. Refer to the "TCP/IP Version 2 for MVS: Installation and Planning" (SC31-6085) for further details.

    Attachment of TCP/IP Version 2 for MVS to the network requires one of the following network processors and/or associated components described below:

    IBM 3172 Interconnect Controller

    • IBM 3172 Interconnect Controller Model 001 or Model 002

    • IBM Interconnect Controller Program (5601-400 or 5601-433)

    • One of the following adapters or a combination of the following:
      • 3172 Interconnect Controller Token-Ring Adapter (#2210)
      • 3172 Interconnect Controller Ethernet Adapter (#2220)
      • 3172 Interconnect Controller PC Network Baseband Adapter/A (#2270)
      • 3172 Interconnect Controller PC Network Adapter II/A (#2271)
      • 3172 Interconnect Controller PC Network Adapter II/A Freq 2 (#2272)
      • 3172 Interconnect Controller PC Network Adapter II/A Freq 3 (#2273)
      • Standard System/370 I/O Channel Interface Cable

    Support for the 3172 Interconnect Controller FDDI capability, will be provided in a then current release of TCP/IP for MVS and VM at the time of the 3172 FDDI availability.

    IBM 8232 LAN Channel Station:

    • IBM 8232 LAN Channel Station Model 001 or 002

    • One of the following adapters or a combination of the following:
      • IBM Token-Ring adapter (6339100)
      • IBM Token-Ring adapter II (67X0438 or 25F9858)
      • IBM Token-Ring Network 16/4 Adapter
      • IBM Token-Ring Network 16/4 Adapter/A
      • IBM PC Network adapter (6450213)
      • IBM PC Network adapter II (1501220)
      • Ethernet LAN adapter (Ungermann Bass, P/N 2273A or equivalent)
      • IBM Local Area Network (LAN) Support Program V1.0 (83X7873) or V1.1 (93X5683) needed if Token-Ring adapter and/or PC Network are installed
      • Standard System/370 I/O Interface cable

    Software Requirements

    IBM TCP/IP Version 2 for MVS is designed to operate with one of the the following:

    • MVS/SP (MVS/370) Version 1 Release 3.5, or later
    • MVS/SP (MVS/XA) Version 2 Release 1.3, or later
    • MVS/SP (MVS/ESA) Version 3 Release 1.0
    • MVS/SP Version 4.1, or later

    TSO is required for interactive use of all client commands. TSO/E Release 1.3 or later is required for users of SMTPNOTE and TELNET. VTAM Version 3.1.1 or later is required for the TELNET (both 3270 and line mode) server and SNALINK. NetView Version 1 Release 3, or later, is a prerequisite for the TCP/IP Version 2 for MVS SNMP Client support.

    NetView Version 1 Release 3 and later releases run only on MVS/XA and MVS/ESA; therefore, SNMP Client support is only available on these operating systems.

    Customers who wish to do X.25 communications will require the corresponding levels of VTAM and NCP that support NPSI. See the VTAM and NCP publications for specific details.

    Customers who plan to run TCP/IP V2 for MVS in 31 bit mode (that is, on MVS/XA, or MVS/ESA), require the IBM VS Pascal Runtime Library to execute the program. However, TCP/IP Version 2 for MVS can be run in 24 bit mode on these systems, without the IBM VS Pascal Runtime Library. This library is not required if TCP/IP V2 for MVS is run in 24 bit mode on MVS/370. Running in 31 bit mode, TCP/IP will utilize storage above the 16MB line.

    TCP/IP Version 2 for MVS functions written in C Language, require the IBM C/370 Runtime Library (5688-039). These functions include:

    • C sample programs
    • Domain Name Server
    • Remote Procedure Call (RPC)
    • X Window System
    • SNMP Client and Server
    • routed
    • Portmapper
    • RPCinfo

    TCP/IP Version 2 for MVS will run on an MVS/370 system, although the C/370 Runtime Library is not supported on MVS/370. The TCP/IP for MVS functions which require the C/370 Runtime Library, listed above, may behave unpredictably when running on an MVS/370 system.

    The optional support software required is as follows:

    • To run GDDM/X:
      • GDDM/MVS Version 2 Release 2 or later (5665-356)

    • For Domain Nameserver:
      • IBM C/370 Library program product (5688-039)
      • In Authoritative mode - DB2 Version 2 Release 2 (5665-DB2)

    • For FTP use of PIOAM
      • PIOAM (5685-137)
      • Support for PIOAM in the MVS/370 environment is not provided

    • For file access protection with FTP:
      • RACF (5740-XXH)

    • For Network File System support, now a part of MVS/DFP:
      • In the MVS/XA environment MVS/Data Facility Product (MVS/DFP) (5665-XA3) Version 3 Release 1
      • In the MVS/ESA environment MVS/Data Facility Product (MVS/DFP) (5665-XA3) Version 3 Release 2 or Release 3
      • Network File System support is not provided by MVS/DFP for the MVS/370 environment

    Application Program Services Requirements: Customer-written programs that interface to:

    • X Window System client
    • Remote Procedure Call
    • TCP protocol boundary
    • UDP protocol boundary
    • DPI
    • IP

    If written in C, require the following:

    • IBM C/370 Compiler Program Product (5688-040)
    • IBM C/370 Library Program Product (5688-039)

    Customer-written programs that interface to:

    • TCP Protocol boundary

    • UDP Protocol boundary

    • IP Protocol boundary

    If written in Pascal, require the following:

    • IBM VS Pascal Compiler and Library (5668-767)

    Compatibility

    An existing offering, TCP/IP for MVS Version 1 (5685-061), provides a subset of the function in TCP/IP Version 2 for MVS (5735-HAL). These two programs are compatible with each other and users moving from the existing offering will have new functions, including network management using NetView. Network File System support is no longer offered with this product. It must be ordered separately if required for file server support. Network File System is now provided as part of the Data Facility Product (see programming requirements section.)

    Customers with applications, which were written using the C language program product in TCP/IP for MVS Version 1 to the socket programming interface, must recompile these applications and may need to change their code in order to operate using TCP/IP Version 2 for MVS. Configuration options may require that TCP/IP Version 2 for MVS be run in 31 bit mode. For further details on limitations, refer to the product publications.


    Security, Auditability, and Control

    IBM TCP/IP Version 2 for MVS has the security and auditability features of the MVS Operating System.

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    Publications

    A memo, program directory, and one copy of the following publications are supplied automatically with the basic machine-readable material:

    • GC31-6086 IBM TCP/IP Version 2 for MVS: License Program Specification
    • SC31-6085 IBM TCP/IP Version 2 for MVS: Installation and Maintenance
    • SC31-6088 IBM TCP/IP Version 2 for MVS: Users' Guide
    • SC31-6087 IBM TCP/IP Version 2 for MVS: Programmer's Reference

    Trademarks

    (R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

    ** Company, product, or service name may be a trademark or service mark of others.

    UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.