PQ58299: FIX INSTRUCTION ON MIGRATION FROM WAS 4.0 TO 4.0.1 WITHOUT CUSTOMIZATION DIALOG | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Change in doc refers to Installation and Customization manual (GA22-7834), Appendix B, Steps for performing a rolling warm start from WebSphere for z/OS V4.0 to V4.0.1 without the customization dialog. Following the instructions in the manual, the customer didn't receive the BBOU0579I message, "Ready for warmstart." The reason for it was that he had 3 systems defined to system management, but since one of them was not used, he upgraded only 2 of them. There was no information anywhere that would point him to the cause of the BBOU0579I message not coming up. In this particular case, the customer solved the problem by deleting the server instance on the no longer used system. Customer recommended the following modification to the doc: "There should be a sub-section on each of the following two sub-topics: you may not receive the BBOU0579I. Reasons why you may not receive the BBOU0579I. Solutions to resolving a BBOU0579I non-occurance."Local fix Problem summary **************************************************************** * USERS AFFECTED: Users who migrate the system from WebSphere * * Application Server for z/OS and OS/390 V4.0 * * to V4.0.1 * **************************************************************** * PROBLEM DESCRIPTION: "Steps for performing a rolling warm * * start from WebSphere for z/OS V4.0 to * * V4.0.1 without the customization * * dialog" and the customized migration * * instructions (BBOMISTR) need to * * explain why you may not get the * * warm start message BBOU0579I. The * * reason for it was that you may have * * additional systems defined to system * * management, but, since one of them * * is not used, not all are upgraded. * **************************************************************** * RECOMMENDATION: * **************************************************************** Following the instructions in the manual, the customer did not receive the BBOU0579I message, "Ready for warmstart." The reason for it was that the customer had three systems defined to system management, but since one of them was not used, the customer upgraded only two of them. There was no information anywhere that would pointed to the cause of the BBOU0579I message not coming up. In this particular case, the customer solved the problem by deleting the server instance on the system no longer being used. The customer recommended an update to the manual. The same update is required for the customized migration instructions shipped with the customization dialog.Problem conclusion The following tip now appears in the customized instructions (BBOMISTR) from the customization dialog: If you do not receive message BBOU0579I, it may be that you have not restarted all run-time and application instances in the sysplex on the new code. Even though you may not be using all run-time and application server instances, they are defined to system management and system management will not issue the message until all server instances are restarted on the new code. Either restart all run-time and application server instances, or run the Administration application (SM EUI) and delete the run-time and application server instances you no longer use. APAR PQ58299 requires a change to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/ Document Name: WebSphere Application Server V4.0.1 for z/OS and OS/390: Installation and Customization Document Number: GA22-7834-04 The following tip now appears on pages 427 and 431 of Installation and Customization: If you do not receive message BBOU0579I, it may be that you have not restarted all run-time and application instances in the sysplex on the new code. Even though you may not be using all run-time and application server instances, they are defined to system management and system management will not issue the message until all server instances are restarted on the new code. Either restart all run-time and application server instances, or run the Administration application (SM EUI) and delete the run-time and application server instances you no longer use. APAR PQ58299 is associated with SERVICE LEVEL W401069 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ66623 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 #: PQ58299
IBM Group: Software Group
Modified date: Jun 5, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.