IBM Support

How to request a SYSMDUMP under Language Environment

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.

Steps

 


Batch Environment (IMS, Webserver, etc.):

 
Option 1 - CEEOPTS DD & SYSMDUMP DD:
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) Include a SYSMDUMP DD card in the JCL specifying the following (where hlq.mydump is a dump data set name):

//SYSMDUMP DD DSN=hlq.mydump,DISP=(NEW,CATLG),
            UNIT=SYSDA,SPACE=(CYL,(250,250),RLSE),
            DCB=(LRECL=4160,RECFM=FBS,BLKSIZE=4160)


3) Rerun the program.
 

 
Option 2 - CEEOPTS DD including DYNDUMP:
1) Specify the following Language Environment run-time options for the application (ex: via CEEOPTS DD card) and include in the DYNDUMP run-time option (where hlq is is the high level qualifier for the dump data set to be created):

//CEEOPTS DD *
 ABTERMENC(ABEND),TERMTHDACT(UADUMP),TRAP(ON,SPIE),DYNDUMP(hlq,DYNAMIC,TDUMP)
/*


2) Rerun the program.
 

 
Additional notes:

  • ABTERMENC run-time option is not available for a 64-bit environment.
  • Ensure that your IEADMR00 Parmlib member reflects the following SDATA parameters:
    SDATA=(CSA,LPA,LSQA,RGN,SQA,SUM,SWA,TRT,ALLNUC,GRSQ)
  • See "Methods available for specifying runtime options" for other ways to override run-time options.
  • If a SYSMDUMP of only the original exception is desired, use TERMTHDACT(UAIMM) TRAP(ON,NOSPIE) sub-options instead.
     

 



CICS Environment:

 
Option 1 - CLER & CEMT

1) Set the following run-time options under CICS (ex: via CLER transaction)

  CLER                                                            CICS IYCLZCFE
                                                                               
               LANGUAGE ENVIRONMENT REGION LEVEL RUNTIME OPTIONS               
                                                                               
                                                                               
TYPE IN YOUR CHOICES.                                                          
                                                                               
RUNTIME OPTION     CHOICE      
TERMTHDACT    ==>  UADUMP        QUIET,MSG,TRACE,DUMP,UAONLY,UADUMP,UAIMM,UATRACE
TRAP          ==>  ON            ON, OFF         


2) Update the transaction dump table with the CICS-supplied CEMT command (this will produce a CICS system dump): 

CEMT SET TRD(40xx) SYS ADD


You will see CEMT output, for example:

STATUS: RESULTS - OVERTYPE TO MODIFY
Trd(4088)  Sys    Loc Max( 999 )  Cur(0000)


3) Rerun the program.
 

 
Additional Notes:

  • ABTERMENC run-time option is not available for a 64-bit environment.
  • Because Language Environment never sets a SPIE or STAE in this environment, the TRAP(,SPIE|NOSPIE) sub-option is ignored under CICS.
  • Using TERMTHDACT(UADUMP) in CICS can cause significant overhead in a production environment. See "Tuning with Language Environment" for notes on setting TERMTHDACT settings under CICS.
  • If a Language Environment run-time option override (for example, ABTERMENC) is required and CLER does not provide a mechanism to modify it, refer to the CEEUOPT documentation for instructions on linking the override module with a High-Level Language (HLL) application.
  • If a SYSMDUMP of only the original exception is desired, use TERMTHDACT(UAIMM) sub-option instead.
     

 


 

UNIX System Services (OE / Shell Environment):


Option 1 - _CEE_RUNOPTS & _BPXK_MDUMP:
1) Specify the following Language Environment run-time options:

export _CEE_RUNOPTS="ABTERMENC(ABEND),TERMTHDACT(UADUMP),TRAP(ON,SPIE)"


2) Specify where to write the system dump:

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

export _BPXK_MDUMP=hlq.mydump


To write the SYSMDUMP to an HFS file (where mydump.dmp is a fully qualified HFS filename):

export _BPXK_MDUMP=/tmp/mydump.dmp


3) Rerun the program.
 

 
Option 2 - _CEE_RUNOPTS including DYNDUMP:
1) Specify the following Language Environment run-time options (where hlq is is the high level qualifier for the dump data set to be created):

export _CEE_RUNOPTS="ABTERMENC(ABEND),TERMTHDACT(UADUMP),TRAP(ON,SPIE),DYNDUMP(hlq,DYNAMIC,TDUMP)"


2) Rerun the program.
 


Additional notes:

  • ABTERMENC run-time option is not available for a 64-bit environment.
  • Environment variables (ex: _CEE_RUNOPTS and _BPXK_MDUMP) can be set either directly in the shell (for the currently logged-in user's session only), or in that user's $HOME/.profile file (to make the settings persistent for that user across future logins).
  • If a SYSMDUMP of only the original exception is desired, use TERMTHDACT(UAIMM) TRAP(ON,NOSPIE) sub-options instead.
     

 



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

[{"Type":"MASTER","Line of Business":{"code":"LOB56","label":"Z HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG90","label":"z\/OS"},"ARM Category":[{"code":"a8m0z00000009WnAAI","label":"z\/OS-\u003ELanguage Environment \/ Cruntime-\u003EGeneral Debugging \/ Diagnostics \/ SLIPS"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.1.0;2.2.0;2.3.0;2.4.0;2.5.0;3.1.0;3.2.0"}]

Document Information

Modified date:
11 May 2026

UID

ibm17267899