Communications Server for z/OS V1R7 TCP/IP Implementation, Volume 1: Base Functions, Connectivity, and Routing

50 Communications Server for z/OS V1R7 TCP/IP Implementation, Volume 1 - Base Functions, Connectivity, and Routing

3.1 The base functions

Base functions are those functions considered to be standard in TCP/IP environments

regardless of the implementation. Most of these functions are implemented at the lower

layers. There are some base functions that are implemented at the application layer (such as

Telnet and FTP). However, the details of the standard applications can be found in

Communications Server for z/OS V1R7 TCP/IP Implementation, Volume 2 - Standard

Applications, SG24-7170. Here we discuss the configuration that provides the infrastructure

of the TCP/IP protocol suite in the z/OS Communications Server environment.

3.1.1 Basic concepts

The z/OS TCP/IP stack (a TCP/IP instance) is a full functional implementation of the standard

RFC protocols that are fully integrated and tightly coupled between z/OS and UNIX System

Services. It provides the environment that supports the base functions as well as the many

traditional TCP/IP applications. The two environments that need to be created and

customized to support the z/OS Communications Server for TCP/IP are:

򐂰 A native z/OS environment in which users can exploit the TCP/IP protocols in a standard

z/OS application environment such as batch jobs (with JES interface), started tasks, TSO,

CICS, and IMS applications.

򐂰 A z/OS UNIX System Services environment that lets you develop and use applications

and services that conform to the POSIX or XPG4 standards (UNIX specifications). The

z/OS UNIX environment also provides some of the base functions to support the z/OS

environment and vice versa.

Since the z/OS Communications Server exploits z/OS UNIX services even for traditional

z/OS environments and applications a full-function mode z/OS UNIX environment—including

a Data Facility Storage Management Subsystem (DFSMS), a z/OS UNIX file system and a

security product (such as Resource Access Control Facility, or RACF) are required before the

z/OS Communications Server can be started successfully and the TCP/IP environment

initialized.

3.1.2 For additional information

When you install and customize the z/OS Communications Server IP, it will be very helpful to

have the following documentation and product publications available:

򐂰 Implementation and migration plans, fallback plans, and test plans that you have created

and customized for your environment

򐂰 Printouts of procedures and data sets that you will be using for the implementation

򐂰 z/OS V1R7.0 Program Directory, Program Number 5694-A01, GI10-0670

򐂰 z/OS V1R7.0 XL C/C++ Run-Time Library Reference, SA22-7821

򐂰 z/OS V1R7.0 Migration, GA22-7499

򐂰 z/OS V1R7.0 Communications Server: IP Configuration Guide, SC31-8775

򐂰 z/OS V1R7.0 Communications Server: IP Configuration Reference, SC31-8776

򐂰 z/OS V1R7.0 Communications Server: IP Messages Volume 1 (EZA), SC31-8783

򐂰 z/OS V1R7.0 Communications Server: IP Messages Volume 2 (EZB, EZD), SC31-8784

򐂰 z/OS V1R7.0 Communications Server: IP Messages Volume 3 (EZY), SC31-8785

򐂰 z/OS V1R7.0 Communications Server: IP Messages Volume 4 (EZZ, SNM), SC31-8786

򐂰 z/OS V1R7.0 Communications Server: IP and SNA Codes, SC31-8791