PQ67299: WHEN CHANGING DAEMON_IPNAME BY DOING "PREPARE FOR COLD START", RESOLVE_IPNAME IS NOT CHANGED. | |||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||
APAR status Closed as unreproducible in next release. Error description When doing "prepare for cold start" to change DAEMON_IPNAME, a customer is never prompted to enter new RESOLVE_IPNAME and com.ibm.ws.naming.ldap.masterurl. As a result, Bootstrap Step 12 fails. current.env files have old values.Local fix There are two workarounds. You can use Option 2 only if you didn't do "prepare for cold start" yet. If you did it, ran the bootstrap and failed at some point because of the wrong IP names, you need to now drop LDAP tables with BBOLDTBD job and drop System Management tables with BBOMCRDB (note, BBOMCRDB also recreates the tables) and then follow steps in Option 1 described below. . Option 1. Changing RESOLVE_IPNAME AFTER prepare for cold start in the SMEUI a - Modify the current.env files for each server you have defined so they have the correct RESOLVE_IPNAME (BBOSMS, BBOIR, BBONM, BBODMN, and all application servers). b - Modify the following value in current.env file for BBONM server so it has the right address: com.ibm.ws.naming.ldap.masterurl= c - in configuration.xml file located in the following directory: /WebSphere390/CB390/PLEX1/conversations/current/ modify the following entry so it has the new ip name: <environment name="RESOLVE_IPNAME" value="new.ip.name" /> d - in the same configuration.xml file, modify the following: <environment name="com.ibm.ws.naming.ldap.masterurl" value= so it has the new LDAP IP name. e - continue with customization panels and etc. as described in the "WAS Installation and Customization" book (the instructions for doing "cold start") . Option 2. Changing RESOLVE_IPNAME BEFORE doing prepare for cold start in the SMEUI: a - Create a new conversation b - at the SYSPLEX level, modify RESOLVE_IPNAME to point to the new Resolve IP name c - modify the following env variable for Naming Server: com.ibm.ws.naming.ldap.masterurl to point to the right LDAP address. d - commit and activate the conversation e - do "prepare for cold start" and when prompted, enter the new IP_NAME and follow the rest of the steps for cold start from the "WAS Installation and Customization" book.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 that do a * * "prepare for cold start" to change * * DAEMON_IPNAME. * **************************************************************** * PROBLEM DESCRIPTION: When changing DAEMON_IPNAME by doing * * "PREPARE FOR COLD START", * * RESOLVE_IPNAME is not changed. * **************************************************************** * RECOMMENDATION: * **************************************************************** When doing "prepare for cold start" to change DAEMON_IPNAME, user is never prompted to enter new RESOLVE_IPNAME and com.ibm.ws.naming.ldap.masterurl. As a result, Bootstrap Step 12 fails. The current.env files have old values. There are two workarounds. You can use Option 2 only if you did not do "prepare for cold start" yet. If you did it, ran the bootstrap and failed at some point because of the wrong IP names, you need to now drop LDAP tables with BBOLDTBD job and drop System Management tables with BBOMCRDB (note, BBOMCRDB also recreates the tables) and then follow steps in Option 1 described below. *** Option 1 *** Change RESOLVE_IPNAME AFTER prepare for cold start in the SM EUI a) Modify the current.env files for each server you have defined so they have the correct RESOLVE_IPNAME (BBOSMS, BBOIR, BBONM, BBODMN, and all application servers). b) Modify the following value in current.env file for BBONM server so it has the right address: com.ibm.ws.naming.ldap.masterurl= c) in configuration.xml file located in the following directory: /WebSphere390/CB390/PLEX1/conversations/current/ modify the following entry so it has the new ip name: <environment name="RESOLVE_IPNAME" value="new.ip.name" /> d) in the same configuration.xml file, modify the following: <environment name="com.ibm.ws.naming.ldap.masterurl" value= so it has the new LDAP IP name. e) continue with customization panels and etc. as described in the "WAS Installation and Customization" book (the instructions for doing "cold start") *** Option 2 *** Change RESOLVE_IPNAME BEFORE doing prepare for cold start in th SM EUI: a) Create a new conversation b) at the SYSPLEX level, modify RESOLVE_IPNAME to point to th new Resolve IP name c) modify the following env variable for Naming Server: com.ibm.ws.naming.ldap.masterurlo point to the right LDAP to point to the right LDAP address. d) commit and activate the conversation e) do "prepare for cold start" and when prompted, enter the new IP_NAME and follow the rest of the steps for cold star from the "WAS Installation and Customization" book.Problem conclusion Temporary fix Comments This APAR is being closed UR1 with the concurrence of the reporting customer.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
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 #: PQ67299
IBM Group: Software Group
Modified date: Nov 14, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.