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)
|