ABENDA03 received after stopping the Daemon
 Technote (FAQ)
 
Problem
ABEND A03 appears after stopping the Daemon. When a stop is issued to the Daemon, the Daemon will issue the stop to all control regions and in turn they issue a stop to all their related server regions. Then the control regions wait for all their server regions to come down. The server regions wait for all work on their threads to complete. Once all work is complete in the server regions, the server regions terminate and notify their control regions they have come down. When the last server region for a control region ends, the control region notifies the Daemon that it is going down. The Daemon waits for all control regions to end. When the last control region is shut down, the Daemon brings itself down.
 
Cause
Missing WebSphere Application Server APAR PQ66328 (service level W401407) and Workload Manager (WLM) APAR OW56785.
 
Solution
The ABENDA03 appears after Daemon termination. The reason for this is when the Daemon comes up, WLM attaches a thread which sits in a loop for the life of the Daemon. This thread remains when the address space terminates and MVS® issues the A03.

Until these APARs are applied, a temporary work around to suppress the A03 from occurring in the Daemon is to add the following to the IEASLPxx member:


SLIP SET,C=A03,ID=XA03,J=BBODMN,A=NODUMP,END

(where BBODMN is the started procedure name for the WebSphere Application Server Daemon)

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1080625
IBM Group: Software Group
Modified date: Nov 29, 2004