APAR II10573

The method for generating a system dump varies for each of the Language Environment run-time environments. The following procedures describe the recommended steps needed to generate a system dump in a batch, IMS, CICS, and OS/390 UNIX shell run-time environment. Other methods may exist, but these are the recommended steps for generating a system dump.

Generating a System Dump in a Batch Run-Time Environment

To generate a system dump in a batch run-time environment complete the following steps:

1. Specify run-time options TERMTHDACT(UADUMP), and TRAP(ON).
2. Include a SYSMDUMP DD card with the desired dataset name and DCB information: LRECL=4160, BLKSIZE=4160, and RECFM=FBS.
3. Rerun the program.

Generating a System Dump in an IMS Run-Time Environment

To generate a system dump in an IMS run-time environment complete the following steps:

1. Specify run-time options TERMTHDACT(UADUMP), and TRAP(ON).
In an IMS environment you can only use CEEUOPT, CEEDOPT, or CEEROPT to change run-time options. CEEUOPT cannot be used by OS/VS COBOL or non-Language Environment assembler.
2. Include a SYSMDUMP DD card with the desired dataset name and DCB information: LRECL=4160, BLKSIZE=4160, and RECFM=FBS.
3. Rerun the program.

Generating a System Dump in an CICS Run-Time Environment

Under CICS, a system dump provides the most useful information for diagnosing problems. To generate a system dump in a CICS run-time environment complete the following steps:

1. Specify run-time options TERMTHDACT(UADUMP) and TRAP(ON)
2. Update the transaction dump table with the CICS supplied CEMT command,
   

   CEMT SET TRD(40XX) SYS ADD

   
   A sample CEMT output is shown: STATUS: RESULTS - OVERTYPE TO MODIFY Trd(4088) Sys Loc Max( 999 ) Cur(0000)
3. Rerun the program.

If you have a Language Environment U4038 abend, CICS will not generate a system dump. In order to generate diagnostic information you must create a Language Environment U4039 abend by performing the following steps:

1. Specify DUMP=YES in CICS DFHSIT
2. Relink your program by including CEEUOPT. CEEUOPT cannot be used by OS/VS COBOL or non-Language Environment assembler.
3. Take CEECOPT from SCEESAMP and modify the Language Environment run-time options TERMTHDACT(UADUMP), ABTERM(ABEND), and TRAP(ON). By setting these run-time options a Language Environment U4039 abend occurs which generates a system dump.
4. Rerun the program

Generating a System Dump in an OS/390 UNIX Shell

To assist you in generating a system dump from the OS/390 UNIX shell we have provided a downloadable file that will dynamically allocate a SYMSDUMP DD card for you. Once you download the file to your Unix System Services HFS, perform the following steps:

1. Unarchive the file using the following command: pax -rvf sysmdyn.pax
2. Enter the OS/390 UNIX shell by using telnet or the OMVS tso command.



3. Set the following environment variables:

   export _BPX_SHAREAS="yes"
   export _CEE_RUNOPTS="termthdact(UADUMP)"




4. Open the readme file provided with the downloadable file, and follow the instructions to dynamically allocate a SYSMDUMP DD.



5. Run the program. The system dump is written to the dataset name specified.

   If the information is not in the file, OS/390 UNIX was unable to run the program in the same address space and a core dump was produced. The coredump is written to the current working directory (HFS) with the filename, coredump.pid, where pid is the eight-digit process id.

   Note: The parameter, MAXCORESIZE, specifies a default file size of 4MB for the system dump. If the file isn't large enough, you can dynamically increase the size by specifying the command:

   SETOMVS

   or

   SET OMVS

   See UNIX System Services Command Reference for additional information on dynamically increasing MAXCORESIZE