PQ73360: SYSTEMS WITH MULTIPLE TCPIP STACKS REQUIRE ADDITIONAL SETUP FOR NAME RESOLUTION.

APAR status
Closed as documentation error.

Error description
The WebSphere for z/OS Installation and Customization book
GA22-7834 does not clearly explain all the steps that must be
followed when configuring WebSphere for z/OS to use a
non-default TCPIP stack. It is not clear what is required in
order for the non-default stack to handle gethostbyname requests
and other name lookup functions. IP names which are resolveable
only by the non-default stack return "host not found" errors.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: The WebSphere for z/OS: Installation    *
*                      and Customization publication does not  *
*                      clearly explain all the steps that must *
*                      be followed when configuring WebSphere  *
*                      for z/OS to use a non-default TCPIP     *
*                      stack.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere for z/OS: Installation and Customization
publication does not clearly explain all the steps that must be
followed when configuring WebSphere for z/OS to use a non-
default TCPIP stack. It is not clear what is required in order
for the non-default stack to handle gethostbyname requests and
other name lookup functions. IP names which are resolveable only
by the non-default stack return "host not found" errors.

The WebSphere for z/OS: Installation and Customization
publication should be updated to clearly explain all the steps.
Problem conclusion
A change to V4.0.1 WebSphere for z/OS: Installation and
Customization (GA22-7834-06) will be available soon. To access
the latest online documentation, go to the product library page
at:

www.ibm.com/software/webservers/appserv/zos_os390/

The change is to the section "Multiple TCP/IP stacks" in
Chapter 5, which now reads:

________________________________________________________________

Chapter 5, pg. 256 (changed information)

Multiple TCP/IP stacks

You may want to run multiple TCP/IP stacks on the same system to
provide network isolation for one or more of your applications.
For instance, you may have multiple OSA Features, each one
connecting your system to a different network. You may assign a
TCP/IP stack to each one. To do so, use the common INET physical
file system (C_INET PFS). This physical file system allow you to
configure multiple physical file systems (network sockets) and
make them active concurrently. First, specify common INET
through the NETWORK DOMAINNAME parameter of
SYS1.PARMLIB(BPXPRMxx). Second, if you plan to configure
WebSphere for z/OS to use a non-default TCP/IP stack, consult
z/OS UNIX System Services Planning, GA22-7800, and z/OS
Communications Server: IP Configuration Reference, SC31-8776,
for details.

When configuring WebSphere for z/OS on a system with multiple
stacks, you must first establish WebSphere for z/OS's stack
affinity to the desired stack so that all socket communications
are bound to that stack, and then you establish WebSphere for
z/OS's allocation of the proper host name resolution
configuration data sets so that host name lookups have the
desired results.

Steps for establishing WebSphere for z/OS's stack affinity to

Perform the following steps to establish WebSphere for z/OS's
stack affinity to the desired stack:

1. Set the BPXK_SETIBMOPT_TRANSPORT environment variable to the
value of the desired transport.
________________________________________________________________
2. Place the BPXK_SETIBMOPT_TRANSPORT environment variable in
the current.env file for each server.
________________________________________________________________
3. Export the BPXK_SETIBMOPT_TRANSPORT environment variable in
client shell scripts.
________________________________________________________________
Note: See z/OS UNIX System Services Planning, GA22-7800, for
more information on the BPXK_SETIBMOPT_TRANSPORT environment
variable.

Steps for establishing WebSphere for z/OS's host name resolution
configuration data set

Perform the following steps to establish WebSphere for z/OS's
host name resolution configuration data set:

1. Set the RESOLVER_CONFIG environment variable to the desired
data set name.
________________________________________________________________
2. Place the RESOLVER_CONFIG environment variable in the
current.env file for each server.
________________________________________________________________
3. Export the RESOLVER_CONFIG environment variable in client
shell scripts.
________________________________________________________________
Notes:
1. You can also use JCL to specify the name resolution
configuration data set. To use JCL, add //SYSTCPD DD
DSN=some.tcpip.DATA,DISP=SHR to the server JCL. The
RESOLVER_CONFIG environment variable overrides the SYSTCPD DD
statement.
2. See z/OS Communications Server: IP Configuration Reference,
SC31-8776, for more information on the RESOLVER_CONFIG
environment variable.
Temporary fix Comments
APAR information
APAR number PQ73360
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-18
Closed date 2003-06-03
Last modified date 2003-06-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ73360
IBM Group: Software Group
Modified date: Jun 3, 2003