PQ75203: IVT FAILS AND USES INCORRECT HOST NAME WHEN "NODE HOST NAME" IS NOT THE LOCAL HOST | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When running the IVT for the base app server, it fails because it uses the wrong host name. On a system where the host name specified in the Customization Dialog "Server Customization" panel for the "Node host name" field is a different host name from what is specified for the HOSTNAME keyword in the TCPIP DATA file. The IVT code calls getLocalHost to obtain the host name. This retrieves the default host name (localhost) of the system not the host name specified in the WebSphere Customization Dialog panels. The IVT code and BBOWIVT job should use the value from the "Node host name" field. . This problem can surface with the following messages from the IVT job: IVTL0010I: Connecting to the WebSphere Application Server TCP90 on port: 9080 IVTL0020I: Could not connect to Application Server, waiting for server to start Server is not active. Start Server and rerun the ivt IVTL0140E: WebSphere Application Server is not running and could not be started . where the TCP90 in message IVTL0010I is the incorrect host name used by the IVT.Local fix A temp fix of the ivt.jar file can be obtained from the WebSphere for z/OS service team until this apar is available. This ivt.jar file will work on service levels W500100, W500101, and W500102. This is FIXED in service level W500103 which is cor-closed PTFs UQ79131 and UQ79132. For service levels W500103 and above, the corrected jar file is shipped with the product and no temp fix is needed. For service levels below W500103, please contact the WebSphere L2 team for the jar file fix: . Once the ivt.jar file is obtained, these are the steps to use the jar file: - download the jar file from the ftp site in binary - rename the version of ivt.jar that is in directory /WebSphere/V5R0M0/AppServer/lib to something else. - copy the ivt.jar you downloaded from the ftp site into directory /WebSphere/V5R0M0/AppServer/lib and keep it called ivt.jar - either invoke the ivt.sh from the command line as follows from directory /WebSphere/V5R0M0/AppServer/bin ivt.sh -p 9080 -host yourhost.name.com OR modify the BBOWIVT job to add the extra -host parameter and its value to the invocation of ivt.sh from within the job. . The new -host option will take a host name or ip address. . Another option, which may not be viable, would be to change the host name value in TCPIP DATA for the HOSTNAME keyword.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Support is needed for IVT users who wan * * to specify a hostname different from * * the one entered in the TCPIP hosts * * file. * **************************************************************** * RECOMMENDATION: * **************************************************************** New functionality needed to be added to allow the user more flexibility when running the IVT. If the user specified a hostname value in the Installation and Customization Dialog, the user should be able to use that value in the job BBOWIVT. Also, this allows the user to specify any hostname they wish at the command line when running the IVT shell script. Previously, the IVT used the value set in the TCPIP hosts file.Problem conclusion An optional command line argument, -host, has been added to the ivtClient.java code. If the host name is specified when at the command line (ex: ivt.sh -host boss0090), then it is used to connect to the tests. If the -host variable is not specified, the IVT will use the hostname variable set in the TCPIP hosts file. During the Installation and Customization Dialog, if the user enters a value for the hostname, then the BBOWIVT job will call ivt.sh with -host host_name specified. During the Installation and Customization Dialog, if the user uses the hostname default value of *, then the BBOWIVT job will call ivt.sh as usual, and not specify the -host argument. APAR PQ75203 requires a change to WebSphere V5.0 for z/OS documentation. A change to WebSphere Application Server for z/OS V5: Installation and Customization, GA22-7910-00, will be available in the next refresh of the documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The following changed section appears in the book on page 158: Steps for running the Installation Verification Test from a command line Follow these steps to run the Installation Verification Test from a command line: 1. Verify that the application server is running. Note: The IVT will end unsuccessfully if the application server is not running. ---------------------------------------------------------------- 2. Confirm that the ivtApp application is installed and started. ---------------------------------------------------------------- 3. From a command line, navigate to the /WebSphere/V5R0M0/AppServer/bin directory. ---------------------------------------------------------------- 4. Issue the following execution: ivt.sh -p port_number -host host_name where: - "-p port_number" is an optional argument that specifies your port number. If you do not specify a port number, the program will use the default port number value of 9080. - "-host host_name" is an optional argument that specifies your host name. If you do not specify a host name, the program will use the host name value that is set in your TCP/IP hosts file. Example: /WebSphere/V5R0M0/AppServer/bin> ivt.sh -p 9090 -host myhost ---------------------------------------------------------------- You are done when the Installation Verification Test runs successfully. Note: After command line initialization, the IVT runs its series of verification tests and reports pass or fail status for each. Once it finishes, check the results in the install_root/logs/ivt.log file. APAR PQ75203 is associated with SERVICE LEVEL W500103 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ75203.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ75203
IBM Group: Software Group
Modified date: Aug 16, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.