How To
Summary
This article describes common ways to set dump-related run-time options and collecting a SYSMDUMP under Language Environment across various environments. A SYSMDUMP provides an unformatted, IPCS‑readable dump of the program’s address space, enabling detailed diagnostic analysis.
Objective
How to request a SYSMDUMP under Language Environment
- Batch Environment (IMS, Webserver, etc.)
- CICS Environment
- UNIX System Services (OE / Shell Environment)
- DB2 Environment
Frequently Asked Questions
- FAQ #1: How can I collect a S0Cx SLIP Dump in Language Environment?
- FAQ #2: How can I collect a U40xx SLIP Dump in Language Environment?
- FAQ #3: How can I collect a U4042 SLIP Dump for user heap damage issues in Language Environment (ex: CEE0802C)?
Steps
Batch Environment (IMS, Webserver, etc.):
|
|
|
CICS Environment:
1) Set the following run-time options under CICS (ex: via CLER transaction)
|
|
UNIX System Services (OE / Shell Environment):
To write the SYSMDUMP to a z/OS data set (where hlq.mydump is a fully qualified dataset specifying LRECL=4160, BLKSIZE=4160, and RECFM=FBS):
|
|
|
DB2 Environment
To override LE Run-Time Options under DB2, see INFO APAR II13232. |
Additional Information
Frequently Asked Questions
FAQ #1: How can I collect a S0Cx SLIP Dump in Language Environment?
1) Specify the following Language Environment run-time options for the application (ex: via CEEOPTS DD card):
//CEEOPTS DD *
ABTERMENC(ABEND),TERMTHDACT(UAIMM),TRAP(ON,NOSPIE)
/*
2) Set the following SLIP trap template to capture a SLIP Dump against the 0Cx ABEND:
SLIP SET,A=SVCD,COMP=0Cx,ID=0Cx,JOBNAME=myjobname,MATCHLIM=3,
SDATA=(CSA,LPA,LSQA,RGN,SQA,SUM,SWA,TRT,ALLNUC,GRSQ),END
Additional notes:
- COMP=0Cx is the specific ABEND to be captured (ex: 0C4), or leave as wildcard 0Cx.
- JOBNAME=myjobname is the name of the failing job to be monitored for the ABEND.
- ABTERMENC run-time option is not available for a 64-bit environment.
- For CICS Environments, SLIP commands on COMP=0Cx will work. To modify run-time options under CICS, see CLER transaction.
FAQ #2: How can I collect a U40xx SLIP Dump in Language Environment?
1) Specify the following Language Environment run-time options for the application (ex: via CEEOPTS DD card):
//CEEOPTS DD *
ABTERMENC(ABEND),TERMTHDACT(UADUMP),TRAP(ON,SPIE)
/*
2) Set the following SLIP trap template to capture a SLIP Dump against the U40xx ABEND:
SLIP SET,A=SVCD,COMP=U40xx,ID=U4xx,JOBNAME=myjobname,MATCHLIM=3,
SDATA=(CSA,LPA,LSQA,RGN,SQA,SUM,SWA,TRT,ALLNUC,GRSQ),END
Additional notes:
- COMP=U40xx is the specific ABEND to be captured (ex: U4039 if using TERMTHDACT(UADUMP)), or leave as wildcard U40xx.
- JOBNAME=myjobname is the name of the failing job to be monitored for the ABEND.
- ABTERMENC run-time option is not available for a 64-bit environment.
- For CICS Environments, SLIP commands on COMP=U40xx will not work.
FAQ #3: How can I collect a U4042 SLIP Dump for user heap damage issues in Language Environment (ex: CEE0802C)?
1) Specify the following Language Environment run-time options for the application (ex: via CEEOPTS DD card):
//CEEOPTS DD *
ABTERMENC(ABEND),TERMTHDACT(UADUMP),TRAP(ON,SPIE),HEAPCHK(ON,1,0,10)
/*
2) When user heap damage is detected by HEAPCHK, LE will immediately issue an ABEND U4042. Set the following SLIP trap template for the U4042:
SLIP SET,A=SVCD,COMP=U4042,JOBNAME=myjobname,MATCHLIM=1,
SDATA=(CSA,LPA,LSQA,RGN,SQA,SUM,SWA,TRT,ALLNUC,GRSQ),END
Additional notes
- COMP=4042 is the specific ABEND that is issued by LE when HEAPCHK is enabled and user heap damage is detected.
- JOBNAME=myjobname is the name of the failing job to be monitored for the ABEND.
- ABTERMENC run-time option is not available for a 64-bit environment.
- HEAPCHK(ON,1,0,10) sub-option indicates that heap checking and/or tracing is activated based on the values of the remaining sub-options.
- HEAPCHK(ON,1,0,10) sub-option indicates that the heap will be checked at each call to a Language Environment heap storage management service. This sub-option has performance implications, but is useful for getting timely dumps of when user heap damage is first detected by Language Environment.
- HEAPCHK(ON,1,0,10) sub-option is useful for detecting culprits of heap overlays or storage leaks. This will cause Language Environment to generate a Heap Storage Diagnostics Report in the dump that includes a series of tracebacks (10 calls each) showing the application's heap allocation ("get heap") call paths.
- HEAPCHK is recommended to be used in a non-production environment if possible.
- HEAPCHK should be turned OFF after a dump is collected.
- For CICS Environments, SLIP commands on COMP=U4042 will not work.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
11 May 2026
UID
ibm17267899