PQ84402: MSGS BBOU0827I BBOU0828I BBOU0829I BBOU0830I DON'T IDENTIFY A SYSTEM NAME SO ITS DIFFICULT TO KNOW WHICH SERVER THE MSG IS FOR | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description customer has a server with 2 instances. Each instance is on a different system. Messages BBOU0827I, BBOU0828I, BBOU0829I, and BBOU0830I note that the server is stopped etc... but does not include an value to identify which system the server stopped on. example: "BBOU0827I SM STOPPING SERVER ABCD2 FOR MAINTENANCE." ABCD2A is on system 1 and ABCD2B is on system 2 Customer cannot tell which system the server stopped on.Local fix HBCProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: Customer has a server with 2 instances, * * each on a different system. * * Automation messages BBOU0827I, * * BBOU0828I, BBOU0829E, and BBOU0830I * * note that the server is being recycled, * * but do not identify the affected * * system. Therefore, the customer's * * automation software cannot tell on * * which system to expect a normal, * * temporary server outage. * **************************************************************** * RECOMMENDATION: * **************************************************************** Messages BBOU0827I, BBOU0828I, BBOU0829E, and BBOU0830I are provided to delineate SM's recycling of J2EE application servers during the activation of new conversations. Automation software monitoring MVS console messages and the current states of active MVS processes can use these messages to help recognize when servers are being intentionally stopped for maintenance, as opposed to when servers stop unexpectedly due to errors. In this latter case, the automation software will typically try to restart the failed server; however, this should not be done when the outage is intentional. Unfortunately, these automation messages do not identify the name of the system on which a server is being recycled, which can cause ambiguities when a server has multiple active server instances on different z/OS systems.Problem conclusion Four new messages have been added: BBOU0832I, BBOU0833I, BBOU0834E, AND BBOU0835I. These messages are identical to messages BBOU0827I, BBOU0828I, BBOU0829E, and BBOU0830I, respectively, except for the addition of a system name field in each new message. For example, message BBOU0832I reads: "SM STOPPING SERVER %s ON SYSTEM %s FOR MAINTENANCE," where the first string substitution is the server name and the second is the system name. The original messages remain for compatibility with existing automation scripts. The new messages will be emitted immediately after their original message counterparts. For example, the following message sequence might appear on the MVS console: BBOU0827I SM STOPPING SERVER BBOASR4 FOR MAINTENANCE. BBOU0832I SM STOPPING SERVER BBOASR4 ON SYSTEM SY1 FOR MAINTENANCE. The following publication was revised as a result of APAR PQ84402: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-07 _______________________________________________________________ This APAR requires changes 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 on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library.html ________________________________________________________________ Chapter 13, pg. 273 (new messages) BBOU0832I SM STOPPING SERVER servername ON SYSTEM systemname FOR MAINTENANCE. Explanation: This message is written to the console before the System Management (SM) process stops the specified server on the specified system during a server recycle operation. When a new conversation is activated, SM recycles active application servers whose configurations have changed in the new conversation. User Response: Do not restart the specified server manually; SM will automatically restart it after performing maintenance. If you have automation tools monitoring application server activity, this message can be used to signal the tools that the specified server is being intentionally stopped. BBOU0833I SM SUCCESSFULLY RESTARTED SERVER servername ON SYSTEM systemname. Explanation: This message is written to the console after the System Management (SM) process successfully restarts the specified server on the specified system during a server recycle operation. When a new conversation is activated, SM recycles active application servers whose configurations have changed in the new conversation. User Response: If you have automation tools monitoring application server activity, this message can be used to signal the tools that the specified server has been successfully restarted. BBOU0834E SM FAILED TO RESTART SERVER servername ON SYSTEM systemname. Explanation: This message is written to the console when the System Management (SM) process fails to restart the specified server on the specified system during a server recycle operation. When a new conversation is activated, SM recycles active application servers whose configurations have changed in the new conversation. This message indicates an error occurred during such a recycle operation. User Response: Check the WebSphere error log for information about errors preceeding this one which could have caused the server restart failure. If you have automation tools monitoring application server activity, this message can be used to signal the tools that the specified server failed to restart. BBOU0835I SM RESTARTING SERVER servername ON SYSTEM systemname AFTER MAINTENANCE. Explanation: This message is written to the console before the System Management (SM) process restarts the specified server on the specified system during a server recycle operation. When a new conversation is activated, SM recycles active application servers whose configurations have changed in the new conversation. User Response: If you have automation tools monitoring application server activity, this message can be used to signal the tools that the specified server is being automatically restarted. APAR PQ84402 is associated with SERVICE LEVEL W401610 of WebSphere Application Server version 4.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: 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 #: PQ84402
IBM Group: Software Group
Modified date: Apr 3, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.