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

Chapter 3. Base functions 51

򐂰 z/OS V1R7.0 UNIX System Services Planning, GA22-7800

򐂰 z/OS V1R7.0 UNIX System Services User’s Guide, SA22-7801

򐂰 z/OS V1R7.0 UNIX System Services Messages and Codes, SA22-7807

򐂰 z/OS V1R7.0 MVS System Messages, Vol 1 (ABA-AOM), SA22-7631

򐂰 z/OS V1R7.0 MVS System Messages, Vol 2 (ARC-ASA), SA22-7632

򐂰 z/OS V1R7.0 MVS System Messages, Vol 3 (ASB-BPX), SA22-7633

򐂰 z/OS V1R7.0 MVS System Messages, Vol 4 (CBD-DMO), SA22-7634

򐂰 z/OS V1R7.0 MVS System Messages, Vol 5 (EDG-GFS), SA22-7635

򐂰 z/OS V1R7.0 MVS System Messages, Vol 6 (GOS-IEA), SA22-7636

򐂰 z/OS V1R7.0 MVS System Messages, Vol 7 (IEB-IEE), SA22-7637

򐂰 z/OS V1R7.0 MVS System Messages, Vol 8 (IEF-IGD), SA22-7638

򐂰 z/OS V1R7.0 MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

򐂰 z/OS V1R7.0 MVS System Messages, Vol 10 (IXC-IZP), SA22-7640

3.2 Why base functions are important

Base functions are important because they establish a functional working environment that

may be exploited by other features or upon which many other functions may be implemented

or validated. When the base functions are implemented, they exercise the most commonly

used code and features of a TCP/IP environment, providing an effective way to perform

integrity tests and validate the TCP/IP environment before embarking on the more complex

features, configurations, and implementations of the stack.

3.3 Common design scenarios for base functions

Because base functions are primarily setting up the primitives in the TCP/IP environment, we

deal with very basic scenarios, which can be built upon at a later time. For the base functions

we consider two scenarios:

򐂰 Single TCP/IP stack environment

򐂰 Multiple TCP/IP stack environment

3.3.1 Single stack

A single stack environment is the existence of one TCP/IP system address space in a single

z/OS image (LPAR) providing support for the functions and features of the TCP/IP protocol

suite. The tasks to complete the configuration of a single stack may be achieved using the

IBM z/OS IP Configuration Wizard or msys for Setup configuration tools. We will explore

using those IBM offerings to perform the configuration task to set up the single stack

environment. However, since these tools provide just the basic setup to get a minimally

configured environment up and running, we additionally use conventional z/OS commands to

add features to the configuration as we create our single stack environment.