MustGather: ABENDEC3 RC=413000x for 4.0, 5.0 and 5.1 for WebSphere Application Server for z/OS
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with WebSphere® Application Server for z/OS® EC3 timeout problems. Gathering the information before calling IBM® support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem
If you have not contacted IBM click: Mustgather: Read first for WebSphere Application Server for z/OS.

ABENDEC3 RETURN CODE = 0413000x ONLY MustGather specific information:

In WebSphere Application Sever 4.0, the Return Code will be 04130001.
In WebSphere Application Server 5.0, the Return Code will be 0413000x, where x is 2-8 depending on the type of timeout.

IMPORTANT note: WebSphere Application Server issues ABENDEC3 for OTHER reasons, other than timeouts. This information is for TIMEOUT Reason Codes ONLY, RC=0413000x

WebSphere Application Server will attempt to capture an SVC DUMP, when the ABENDEC3 RC=0413000x is issued.

Reasons for the SVC Dump NOT being captured could be the following:

- z/OS DAE (dump suppression) is suppressing the SVC DUMP

- No Dump Datasets Available on the z/OS system

If the SVC Dump is NOT generated automatically, then you may need to set a SLIP Trap on the ABENDEC3, Disable DAE Suppression, or make Dump Datasets available.

  1. SLIP command to set:
    SLIP SET A=SVCD,COMP=EC3,JOBNAME=aaaa*, JOBLIST=aaaa*,
    SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,PSA,RGN,SQA,SUM,SWA,TRT), END
    (Type the SLIP command on one line)
    Where <aaaa*> is the jobname of the WebSphere address space, include the '*' to capture both Control Region and Servant Region
    You can include REASON=0413000x in the SLIP, where 'x' is the reason code you are seeing.
    You can include ADISLST=(C,H,P,S) in the SLIP, to capture any address spaces which may have been Program Controlled, (PC'd) to (for example you may want to include DB2 address space if DB2 is involved with the failure).
  2. Disable DAE
    Using IPCS on the system where the ABENDEC3 is occurring, use IPCS Option 3 (Utility), then option 5 (DAE), find the ABENDEC3 RC=0413000x entry, and mark it 'T' (to take next dump)

Gather the following documentation:
  1. SVC Dump that is generated by WebSphere Application Server
    (May contain several Address Spaces, depending on what the Server was doing).
  2. JobLogs of the Failing WebSphere Server
    This should include the ENTIRE job output, of ALL of the address spaces (Control Region and Servant Region(s) )

    You can use SDSF 'XDC' action character next to the jobname in the SDSF ST Display, to 'Print' the entire job to a dataset.

Refer to Submitting Diagnostic Information to IBM for instructions on how to FTP.

For a listing of all technotes, downloads, and educational materials search the WebSphere Application Server support site

 
Related information
Mustgather: Read first
Steps to Getting Support
Submitting Diagnostic Information to IBM
 
 
 


Document Information


Current web document: swg21195600.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Crash
Operating system(s): z/OS
Software version: 5.1
Software edition:
Reference #: 1195600
IBM Group: Software Group
Modified date: Jan 12, 2005