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

Chapter 3. Base functions 75

We recommend using the //PROFILE DD statement in the TCP/IP address space JCL

procedure to explicitly allocate the PROFILE data set.

3.6.5 TCP/IP configuration data set names

This topic is described in z/OS V1R7.0 CS: IP Configuration Guide, SC31-8775. We strongly

recommend that you read the information about data set names in this book, before you

decide on your data set naming conventions.

The purpose here is to give an introduction to the data set naming and allocation techniques

used by z/OS Communication Server IP.

With z/OS Communication Server IP you have a choice for some of the configuration data

sets, whether they should be allocated implicitly or explicitly. Additionally, you need to ensure

that not only MVS functions find the appropriate data sets, but also that the z/OS UNIX

functions do as well.

򐂰 Implicit

The name of the configuration data set is resolved at runtime based on a set of rules (the

search order) implemented in the various components of TCP/IP. When a data set name

has been resolved, the TCP/IP component uses the dynamic allocation services of MVS

or of UNIX System Services to allocate that configuration data set. See z/OS V1R7.0 CS:

IP Configuration Guide, SC31-8775, for details.

These are some of the data sets (or files) that can only be implicitly allocated in an z/OS

Communication Server IP:

hlq.ETC.PROTO

hlq.ETC.RPC

hlq.HOSTS.ADDRINFO

hlq.HOSTS.SITEINFO

hlq.SRVRFTP.TCPCHBIN

hlq.SRVRFTP.TCPHGBIN

hlq.SRVRFTP.TCPKJBIN

hlq.SRVRFTP.TCPSCBIN

hlq.SRVRFTP.TCPXLBIN

hlq.STANDARD.TCPCHBIN

hlq.STANDARD.TCPHGBIN

hlq.STANDARD.TCPKJBIN

hlq.STANDARD.TCPSCBIN

hlq.STANDARD.TCPXLBIN

In the above data set names, hlq is determined using the following search sequence:

– User ID or jobname

– DATASETPREFIX value (or its default of TCPIP), defined in TCPIP.DATA

Dynamically allocated data sets can include a mid-level qualifier (MLQ), for example, a

node name, or a function name:

– For data sets containing a PROFILE configuration file:

xxxx.nodename.zzzz

– For data sets containing a translate table used by a particular TCP/IP server:

xxxx.function_name.zzzz (for the FTP server the function_name is SRVRFTP)

Data set SYS1.TCPPARMS(TCPDATA) can be dynamically allocated if it contains the

TCPIP.DATA configuration file.

򐂰 Explicit

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

For some of the configuration files, you can tell TCP/IP which files to use by coding DD

statements in JCL procedures, or by setting UNIX environment variables. Again, the

various data sets used by TCP/IP functions and their resolution method are described in

z/OS V1R7.0 CS: IP Configuration Guide, SC31-8775.

TCPIP.DATA

The TCPIP.DATA configuration data set is the anchor configuration data set for the TCP/IP

stack and all TCP/IP servers and clients running on that stack. In z/OS Communication

Server IP, you can define the TCPIP DATA parameters in an z/OS UNIX file system file or in

an MVS data set. The TCPIP.DATA configuration data set is read during initialization of

all

TCP/IP server and client functions. They must all access this data set in order to find the

basic configuration information, such as the name of the TCP/IP address space (keyword

TCPIPJOBNAME), the TCP/IP host name (keyword HOSTNAME), and the data set prefix to

use when searching for other configuration data sets (keyword DATASETPREFIX).

Notes:

򐂰 The syntax for the parameters in the TCPIP DATA file can be found in z/OS V1R7.0 CS:

IP Configuration Reference, SC31-8776.

򐂰 A sample TCPIP.DATA configuration file is provided in hlq.SEZAINST(TCPDATA).

The TCPIP.DATA file is also known as one of the Resolver configuration files. In fact, the

name is now more commonly used to refer to this important file in the UNIX System Services

environment because the sockets library contains a component called the Resolver. In the

UNIX environment you use the /etc/resolv.conf file for the same purpose as you use

TCPIP.DATA in an MVS environment.

Testing TCPIP.DATA

HOMETEST is a TSO command that can be used to test your active and current

TCPIP.DATA specifications. The HOMETEST command is meant to be issued only from

TSO; therefore, it uses the native MVS search order when locating configuration data sets

and it uses Resolver for doing name to IP address resolutions.

Example 3-5 TCPIP.DATA with HOMETEST

EZA0619I Running IBM MVS TCP/IP CS V1R7 TCP/IP Configuration Tester

EZA0602I TCP Host Name is: WTSC30E

EZA0605I Using Host Tables to Resolve WTSC30E

EZA0611I The following IP addresses correspond to TCP Host Name: WTSC30E

EZA0612I 10.10.10.210

EZA0614I The following IP addresses are the HOME IP addresses defined in

PROFILE.TCPIP:

EZA0615I 10.10.10.210

EZA0615I 10.10.2.212

EZA0615I 10.10.3.213

EZA0615I 10.10.2.214

EZA0615I 10.10.3.215

EZA0615I 10.10.4.214

EZA0615I 10.10.4.215

EZA0615I 10.10.5.216

EZA0615I 10.10.20.130

EZA0615I 10.10.20.130

EZA0615I 127.0.0.1

EZA0618I All IP addresses for WTSC30E are in the HOME list!