PQ59471: LPA UPDATE WHILE HAVING DAEMON UP CAUSES A TERMINATION OF DAEMONWITHOUT CLEAN UP. RESTARTING DAEMON CAUSES ABEND CC3 RC0A050001

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Doing LPA ADD and DELETE while daemon is up causes the demon to
come down hard without a chance to clean up.  Next time when
attempting to start the daemon, it looks at the flag which
indicates whether the daemon is already up or not, sees that
it's set, and throws CC3 abend with RC 0A050001. The abend/rc
indicates that an attempt was made to start a daemon while one
was already active. There needs to be a better verification
process that would shows whether the daemon is really up or not.
Local fix
Two solutions:
1. Re-IPLing the system.  This will clean up the control blocks
and allow for a clean startup of the daemon.
2. Zapping CSA storage.  We do not have the capability to zap
storage, so you need to have a vendor product to do so.  To zap
storage you need to find the address of the BGVT block (CVT
address is at offset x'10', ECVT ptr is at CVT+8c, BGVT ptr is
at ecvt+234) and zap the first 4 bytes. The purpose of it is to
change the eyecatcher at offset 0 from "BBODBGVT" to something
else.  You will be able to start the daemon at this point.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: ABEND CC3 reason code 0A050001          *
*                      when starting the WebSphere Application *
*                      Server V4.0.1 for z/OS and OS/390       *
*                      Daemon.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the WAS MVS Resource Manager load module BBORRMGR is forcibly
deleted from LPA while the Daemon is still up, when the Daemon
terminates, the Resource Manager will not run and will not turn
off the bit in the BGVT which indicates a Daemon is active.
When a subsequent Daemon instance is started, it fails with
an ABEND CC3 reason code 0A050001 because it thinks another
Daemon is active, and only one Daemon is allowed to be active at
once.
Problem conclusion
Code was added to BGVT creation to validate that, if the
Daemon-is-up bit is set, that there is, in fact, a Daemon
active before abending.

The following publication was revised as a result
of APAR PQ59471:
________________________________________________________________
WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-02
________________________________________________________________
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:


http://www.ibm.com/software/webservers/appserv/

________________________________________________________________
Chapter 15, pg. 518 (new message)
CC3 0A050003
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
________________________________________________________________
Chapter 15, pg. 518 (new message)
CC3 0A050004
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
________________________________________________________________

APAR PQ59471 is associated with SERVICE LEVEL W401040 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ59471
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-26
Closed date 2002-04-04
Last modified date 2002-05-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ64842

Modules/Macros
BBOCASYD BBOCASYH BBOCLSAC BBOCLSCC BBOCLSPC BBOCLSSA
BBOCLSUE BBOCLSUR BBODASRC BBODASRF BBODASRP BBODASRQ
BBODASRS BBODASRU BBODBGVT BBODSDRG BBODSREG BBOIPOOL
BBOMGSCO BBOMSCOX BBOOBIND BBOOBOAM BBOODCTX BBOOEQGQ
BBOOGSCO BBOOOPIP BBOOOPIX BBOOORBP BBOOORBX BBOOOUTP
BBOOPCCR BBOORCTX BBOOSBND BBOOSBOA BBOOSCHD BBOOSMFC
BBOOSMFP BBOOSRAB BBOOSRBF BBOOSRM BBOOSRQA BBOOSRQF
BBOOSRR BBOOSSMF BBOOSSNQ BBOOSSRR BBOOSSTP BBOOSUBD
BBOOSWRK BBOOTMTM BBOOTTIP BBOOTTIX BBOOWORK BBORABND
BBORADMP BBORARM BBORDEQ BBORENQ BBORFRES BBORFRR
BBORGETS BBORLEXT BBORMCDP BBORMCDX BBORPTRC BBORRMC
BBORRMGR BBORSDMP BBORSLOG BBORTDF1 BBORTIME BBORTSRB
BBOSSACE BBOSSCCA BBOSSCLB BBOSSCTX BBOSSDB2 BBOSSEXT
BBOSSINI BBOSSITP BBOSSITU BBOSSMEP BBOSSMET BBOSSRPW
BBOSSRPX BBOSSRVA BBOTETCD BBOTRPCX BBOTTMPC BBOUBINF
BBOUWTO BBOZ0916 BBOZ0917 BBOZ0918 BBOZ0919 BBOZ0920
BBOZ0921 BBOZ0922 BBOZ0923 BBOZ0924 BBOZ0925 BBOZ0926
BBOZ0927 BBOZ0928 BBOZ0929 BBOZ0930 BBOZ0931 BBOZ0932
BBOZ0933 BBO3BEGC BBO3CTXP BBO3CTXX BBO3ENDC BBO3ENQP
BBO3FRES BBO3GETS BBO3PCBA BBO3PCBT BBO3SETS BBO3SRVP
BBO3SSAF BBO3SSFP BBO3SWCH      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ64842    UP02/04/09 P F204

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


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 #: PQ59471
IBM Group: Software Group
Modified date: May 2, 2002