Sun Mainframe Transaction Processing Troubleshooting and Tuning Guide

This chapter describes the tracing and dumping facilities Sun MTP provides. Do not use these facilities unless you are instructed to do so by your authorized service provider. The topics in this chapter include:

• Using the Sun MTP Trace Facility
• Dump Facilities
• Application Dump Facility
• Enabling and Disabling the Dump Facility
• Identifying Where the Transaction Abended

---

Using the Sun MTP Trace Facility

The Sun MTP trace facility enables you to selectively trace low-level routines. Use it only under the direction of a technical support engineer. This internal tracing facility increases the amount of shared memory that Sun MTP allocates. Each of the following processes has a trace table allocated for it in shared memory:

• unikixmain
• unikixprt
• unikixstrt
• unikixept
• unikixrcv
• unikixdsptch
• unikixtran# (each unikixtran will have its own trace table)

The default size of each trace table is 80,000 bytes.

The following formula shows how much shared memory is required for tracing for a Sun MTP region.

(tx-procs + 6) * 80,000 = bytes

Add the number of transaction processors to 6, which is the number of static shared memory processes, and then apply the formula. In the following example, the region has 8 transaction processors, so 14 processes are used to calculate the shared memory requirements.

14 * 80,000 = 1,120,000 bytes

Sun MTP will allocate 1,120,000 bytes of shared memory for internal tracing.

After you calculate the shared memory requirements for the extended trace facility, you must add that number to the shared memory requirements of your application to get the total shared memory requirement. When starting Sun MTP, provide this value with the -S option to unikixmain.

Use the kixetrace utility to display the Trace Administration Utility menu.

  FIGURE 13-1 Trace Administration Utility Menu

An asterisk (*) is displayed next to any option that is selected.

When the trace facility is first run, the menu always shows Production trace on as selected. This does not mean that production trace is turned on; it is the default. The menu does not indicate the options with which Sun MTP is running.

The kixeformat utility is provided to format internal trace dumps. It should only be used under the direction of your authorized service provider. The Sun Mainframe Transaction Processing Software Reference Guide describes the command format for this utility.

Dump Facilities

Sun MTP provides two methods for dumping system information that you can use to help determine the cause of problems:

• The kixsnap utility, described in the Sun Mainframe Transaction Processing Software Reference Guide.
• Application dump facility.

Application Dump Facility

The application dump facility produces a formatted dump file that lists an application's runtime environment under the following circumstances:

• A runtime error occurs
• The application program uses the CICS ABEND command without a HANDLE ABEND command
• Errors such as an out-of-storage condition occur

The application dump file is written to the $KIXSYS directory and the name of the file is printed in the log file with message number KIX6702I. The dump file name is a combination of the transaction name and a sequence number; for example, AC010000.prt.

The formatted dump file includes the following information:

• Date and time of the error
• Runtime error information message
• CICS command trace information, also referred to as a tombstone
• Address of heap, shared memory, maximum core, and threshold memory
• Exec interface block (EIB)
• Common work area (CWA) and terminal user area (TCTUA)
• Communication area (COMMAREA)
• Working storage section for COBOL programs

The application dump facility also writes the following information to unikixmain.err and unikixmain.log:

• Runtime error message, if available
• CICS command trace information, also referred to as a tombstone
• Name of the dump file

Enabling and Disabling the Dump Facility

Although an application dump file is generated by default, you can explicitly enable the dump facility using either of the following options:

• unikixmain -D dy
• kixcontrol -d y

To turn off the dump facility, use either of these options:

• unikixmain -D dn
• kixcontrol -d n

Identifying Where the Transaction Abended

The unikixmain.log file contains information about the transaction failure. It provides the name of the transaction, the name of the program, and the last four CICS commands executed by the transaction. Each CICS command provides the following information:

• Name of the CICS command executed
• CID# references, which stands for CICS command IDentification reference number
• Status of the command executed

The CID# reference helps to locate the CICS command(s) that was executed. This reference number is generated by the kixclt translator. By searching for the CID# reference in the output of the kixclt translator (a *.cbl file for COBOL), you can locate the CICS command that was executed.

unikixmain.err and unikixmain.log Entries

When the application dump facility is enabled, entries are written to unikixmain.err and unikixmain.log that look similar those in the following example.

08/19/2002 13:40:40 unikixtran2 :--------------------------------------------

08/19/2002 13:40:40 unikixtran2 :Transaction AC01  program ACCT01    has abended

08/19/2002 13:40:40 unikixtran2 :Function ENDBR             CID# 00001113 Condition FILENOTFOUND

08/19/2002 13:40:40 unikixtran2 :Transaction was  executing MTP code

08/19/2002 13:40:40 unikixtran2 :Previous functions:

08/19/2002 13:40:40 unikixtran2 :Function READNEXT          CID# 00001100 Condition Successful

08/19/2002 13:40:40 unikixtran2 :Function READNEXT          CID# 00001100 Condition Successful

08/19/2002 13:40:40 unikixtran2 :Function READNEXT          CID# 00001100 Condition Successful

08/19/2002 13:40:40 unikixtran2 :---------------------------------------------

08/19/2002 13:40:40 unikixtran2 :Formatted dump requested, file is AC010000.prt

.

.

. (more log not shown)

In this example, CID# 00001113 is the command that failed. In the source program, ACCT01.cbl, a search for 0001113 displays the following code:

* EXEC CICS ENDBR DATASET('ACCTIT') END-EXEC.

	MOVE 'ACCTIT' TO DFHEIV1

	MOVE 0 TO DFHEIV11

	MOVE '&2                    $   #00001113' TO DFHEIV0

	CALL 'kxdfhei1' USING DFHEIV0,

		DFHEIV1,

		DFHEIV11,

		DFHEIV99

	GO TO 9999-DFHEXIT DEPENDING ON DFHEIGDK.

Dump File Output

The dump file generated for a COBOL program looks similar to the example in CODE EXAMPLE 13-1.

When interpreting the information in the dump file, note the following:

• The dump file displays the COMMAREA for the level where the error occurred
• The fields of the EIB return hexadecimal values

CODE EXAMPLE 13-1 Dump File-- COBOL (1 of 3)

08/19/2002 13:40:40.000 unikixtran2 Formatted Dump File     Transaction: AC01 has abended in Program: ACCT01 Failure occurred in Sun MTP code CICS Command Level Trace: Function ENDBR CID# 00001113 Condition FILENOTFOUND Function READNEXT CID# 00001100 Condition Successful Function READNEXT CID# 00001100 Condition Successful Function READNEXT CID# 00001100 Condition Successful   Current address on heap (41dd00) Address of Shared Memory (ee000000) Address of Max Core (ee000000) Address of Threshold Memory (edf80000)   ****************** Exec Interface Block ****************** EIBTIME 0134040c EIBSYNC 00 EIBDATE 0102231c EIBFREE 00 EIBTRNID AC01 EIBRECV 00 EIBTASKN 0000003c EIBSEND 00 EIBTRMID C000 EIBATT 00 DFHEIGDI 0000 EIBEOC 00 EIBCPOSN 0155 EIBFMH 00 EIBCALEN 0000 EIBCOMPL 00 EIBAID 27 EIBSIG 00 EIBFN 0612 EIBCONF 00 EIBRCODE 010000000000 EIBERR 00 EIBDS ACCTIT EIBERRCD 00000000 EIBREQID EIBSYNRB 20 EIBRSRCE ACCTIT EIBNODAT 00 EIBRESP 0000000c EIBRESP2 00000000   ********************************* CWA ******************************** No Common Work Area present   ********************************* TCTUA ****************************** TCTUA LENGTH = 255 ee201ee0 00000000 20202020 20202020 20202020 20202020 * * ee201ef0 00000010 20202020 20202020 20202020 20202020 * * ee201f00 00000020 20202020 20202020 20202020 20202020 * * ee201f10 00000030 20202020 20202020 20202020 20202020 * * ee201f20 00000040 20202020 20202020 20202020 20202020 * * ee201f30 00000050 20202020 20202020 20202020 20202020 * * ee201f40 00000060 20202020 20202020 20202020 20202020 * * ee201f50 00000070 20202020 20202020 20202020 20202020 * * ee201f60 00000080 20202020 20202020 20202020 20202020 * * ee201f70 00000090 20202020 20202020 20202020 20202020 * * ee201f80 000000a0 20202020 20202020 20202020 20202020 * * ee201f90 000000b0 20202020 20202020 20202020 20202020 * * ee201fa0 000000c0 20202020 20202020 20202020 20202020 * * ee201fb0 000000d0 20202020 20202020 20202020 20202020 * * ee201fc0 000000e0 20202020 20202020 20202020 20202020 * * ee201fd0 000000f0 20202020 20202020 20202020 202020 * *   ********************************* COMMAREA *************************** No commarea present   ****************************** WORKING-STORAGE ************************** PROGRAM:ACCT01 3f7b38 00000000 00000000 00000000 0000017F 003F02EF *.............?..* 3f7b48 00000010 2A2A2A2A 2A2A2A2A 2A2A2A2A 41433000 *************AC0.* 3f7b58 00000020 00000000 20202020 00000000 00000000 *.... ........* 3f7b68 00000030 0001000C 0001000C 52202020 20202020 *........R * 3f7b78 00000040 20202047 5245454E 20202020 20202020 * GREEN * 3f7b88 00000050 20202020 20202020 20202020 20202020 * * 3f7b98 00000060 20414343 54303120 20202020 20202020 * ACCT01 * 3f7ba8 00000070 20202000 00000300 06000053 53494820 * ........SSIH * 3f7bb8 00000080 20202020 20202020 31303030 34475245 * 10004GRE* 3f7bc8 00000090 454EFFFF FFFFFFFF FFFFFFFF FFFFFFFF *EN..............* 3f7bd8 000000a0 00000000 00000031 30303033 20202047 *.......10003 G* 3f7be8 000000b0 5245454E 4649454C 44202020 204A4F53 *REENFIELD JOS* 3f7bf8 000000c0 48202020 20204C20 204D5354 52202037 *H L MSTR 7* 3f7c08 000000d0 3031204E 20425241 4E442042 4C564420 *01 N BRAND BLVD * 3f7c18 000000e0 20202020 20202020 204E2020 20202031 * N 1* 3f7c28 000000f0 3030302E 30300000 00000000 00002020 *000.00........ * 3f7c38 00000100 20202020 00002F00 002F0000 20202020 * ../../.. * 3f7c48 00000110 00000000 00000000 20202020 20202000 *........ .* 3f7c58 00000120 002F0000 2F000020 20202000 00000000 *./../.. .....* 3f7c68 00000130 00000000 00000000 20262D30 4859383C *........ &-0HY8<* 3f7c78 00000140 2541314A 2F495228 29003132 33343536 *%A1J/IR().123456* 3f7c88 00000150 377B0000 31008019 852100FF 1A200203 *7...1....!... ..* 3f7c98 00000160 06001C09 01223208 3441979C 0201000F *....."2.4A......* 3f7ca8 00000170 010E0F00 00000000 2D275F7C 3D575868 *........-'..=WXh* 3f7cb8 00000180 22253E2C 31323334 35363738 393A2340 *"%>,123456789:#@* 3f7cc8 00000190 41424344 45464748 495B2E3C 00000000 *ABCDEFGHI..<....* ... ... ...****************************** WORKING-STORAGE ************************** PROGRAM:XXTBMU 7afcd3e0 00000000 00 *. *

The dump file generated for a C program looks similar to the example in CODE EXAMPLE 13-2.

03/08/1999  15:40:09.000  unikixtran2 Formatted Dump File

Run-Time Error:

C Application ERROR

Transaction: XTBM has abended in Program: XXTBMU  

Failure occured in Application code

CICS Command Level Trace:

      Function GETMAIN          CID# 00000020 Condition Successful

      Function SEND MAP         CID# 00000013 Condition Successful

      Function ADDRESS          CID# 00000045 Condition Successful

      Function ADDRESS          CID# 00000001 Condition Successful

Current address on heap     (400b1000)

Address of Shared Memory    (4086c000)

Address of Max Core         (4086c000)

Address of Threshold Memory (4056c000)

******************  Exec Interface Block   ******************

EIBTIME   0154008c              EIBSYNC   00

EIBDATE   0099067c              EIBFREE   00

EIBTRNID  XTBM                  EIBRECV   00

EIBTASKN  0000002c              EIBSEND   00

EIBTRMID  C003                  EIBATT    00

DFHEIGDI  0000                  EIBEOC    00

EIBCPOSN  0004                  EIBFMH    00

EIBCALEN  000c                  EIBCOMPL  00

EIBAID    27                    EIBSIG    00

EIBFN     0c02                  EIBCONF   00

EIBRCODE  000000000000          EIBERR    00

EIBDS                           EIBERRCD  00000000

EIBREQID                        EIBSYNRB  20

EIBRSRCE                        EIBNODAT  00

EIBRESP   00000000

EIBRESP2  00000000

*********************************   CWA   ***************************

No Common Work Area present

*********************************   TCTUA   *************************

TCTUA LENGTH = 255

c24a0a80 00000000  20202020 20202020 20202020 20202020  *                *

c24a0a90 00000010  20202020 20202020 20202020 20202020  *                *

c24a0aa0 00000020  20202020 20202020 20202020 20202020  *                *

c24a0ab0 00000030  20202020 20202020 20202020 20202020  *                *

c24a0ac0 00000040  20202020 20202020 20202020 20202020  *                *

c24a0ad0 00000050  20202020 20202020 20202020 20202020  *                *

c24a0ae0 00000060  20202020 20202020 20202020 20202020  *                *

c24a0af0 00000070  20202020 20202020 20202020 20202020  *                *

c24a0b00 00000080  20202020 20202020 20202020 20202020  *                *

c24a0b10 00000090  20202020 20202020 20202020 20202020  *                *

c24a0b20 000000a0  20202020 20202020 20202020 20202020  *                *

c24a0b30 000000b0  20202020 20202020 20202020 20202020  *                *

c24a0b40 000000c0  20202020 20202020 20202020 20202020  *                *

c24a0b50 000000d0  20202020 20202020 20202020 20202020  *                *

c24a0b60 000000e0  20202020 20202020 20202020 20202020  *                *

c24a0b70 000000f0  20202020 20202020 20202020 202020    *                *

*********************************   COMMAREA   ***************************

COMMAREA LENGTH: 12

c2335880 00000000  44656C74 61585442 4D540000           *DeltaXTBMT..    *

******************************  WORKING-STORAGE **************************

PROGRAM:XXTBMU  

7afcd3e0 00000000  00                                   *.                *

Sun Mainframe Transaction Processing Troubleshooting and Tuning Guide

816-5333-11

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.