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

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

Example 2-11 CS03 local IPNODES data set

; Entries in the hosts file have the following format:

; Address HostName

; Address HostName1 HostName2 HostName3 ..... HostName35

; Address HostName1 HostName2 HostName3 ..... HostName35

; Address: is an IP address, it can be IPV4 or IPV6 address.

; Note: IPv4-mapped IPv6 address is not allowed.

; HostName: the length of the hostname is up to 128 characters,

; and each IP address can have up to 35 hostnames.

10.12.4.221 tot177

10.10.1.230 tcpip30

10.10.1.221 tcpip32

10.10.1.241 tcpip31

10.10.2.1 router1

10.10.3.2 router2

1::2 TESTIPV6ADDRESS1

1:2:3:4:5:6:7:8 TESTIPV6ADDRESS2

2.4.4 Verification

To verify whether the local implementation is working as expected, we checked whether

FTPDA was started with the correct stack affinity by looking at its startup messages, as

shown in Example 2-12.

Example 2-12 Startup messages

m STARTING FTPDA

m FTPDA PROC

m FTPD FTPD: STARTINGi 0Ml NOLIMITk POSIX(ON) ALL31(ON)

ENVAR("_BPXK_SETIBMOPT_TRANSPORT=TCPIPA" "TX=EST")/

> CEEDUMP. *¢ TCPIP.FTPDA.STC06903.D0000101.?

> SYSFTPD SHR¢ b TCPIPA.TCPPARMS FTPDA32

> SYSTCPD SHR¢ b TCPIPA.TCPPARMS DATAA32

The next step was to check if port 21 has been assigned to FTPDA1 as expected, by

displaying the ports in stack TCPIPA, as shown in Example 2-13.

Example 2-13 Displaying the FTP port 21

D TCPIP,TCPIPA,N,CONN

EZD0101I NETSTAT CS V1R7 TCPIPA 525

USER ID CONN STATE

FTPDA1 000001DA LISTEN

LOCAL SOCKET: ::FFFF:10.10.1.221..21

FOREIGN SOCKET: ::FFFF:0.0.0.0..0

To verify whether the user CS03 was using the correct IPNODES data set, a ping command

to a host name defined in CS03.ETC.IPNODES was issued (see Example 2-14).

Example 2-14 Resolving the name TOT177 through local IPNODES data set

CS03 @ SC32:/u/cs03>ping tot177

CS V1R7: Pinging host tot177 (10.12.4.221)

Ping #1 response took 0.001 seconds.

It is also possible to verify where the Resolver is looking, by using the TRACE RESOLVER

parameter in the stack’s or application’s TCPIP.DATA data set. How this is done and the