Download Abap Dumps PDF

TitleAbap Dumps
TagsKernel (Operating System) 64 Bit Computing Variable (Computer Science) File System
File Size1.1 MB
Total Pages37
Document Text Contents
Page 2

ABAP ‘short dump' (German Kurzdump) is a misnomer. There is nothing ‘short' about an ABAP dump.

Should the ABAP AS no longer be able to execute a program - because of an unhandled or unhandleable

exception, a resource or system problem, or an error in coding - it may document the problem with 20 or

more pages of diagnostic information.

Very often, a short dump contains not only the exact diagnosis of the problem that occurred but also the

solution, or at least important pointers toward the solution of the problem. But experience has shown that

developers often don't even read dumps - not even the highly useful Error analysis - much less make use

of the diagnostic resources that short dumps offer.

The lack of attention to short dumps is understandable but regrettable.

Understandable because the report that your program is dumping in a customer system is about the worst

news you can get. It's time to drop everything and switch to emergency mode.

Regrettable, because often developers who don't take a good look at the short dump waste a lot of time

thrashing around in the debugger, trying to understand what went wrong. Taking a good look at the short

dump is usually a better use of your time. And then there are the situations in which the dump is the only

diagnostic resource that you have - when the dump occurred in a production system and is too sensitive to

repeat, when the dump occurred several hours after the background job started, and so on.

In this pair of weblogs, we will take a quick tour through the ABAP short dump as of NetWeaver Release

7.0 EHP1, pointing out important analytic aids that it offers and how to make the best use of them.

In the first weblog, we will just get ready to analyze a dump. The weblog looks at the ABAP dump lists

and how to get the most out of them, as well as at a couple of related sources of information.

Off to the Dump

If you aren't staring at a short dump on the screen in front of you, then the way to see any ABAP short

dumps in your system is by starting transaction ST22. As standard selections, ST22 lets you list dumps

from yesterday and today, but also lets you select dumps by user, date and other parameters.

Adding Information to the List of Selected Runtime Errors

It is natural to want to hurry right to the display of a dump that you need to investigate. But hold on - have

you ever noticed those three useful little options at the bottom of the ST22 start screen? You might want

to take a look at them before you rush off into a list of short dumps.

By default, the options are not set. But:

Page 18

seconds difference that you may see can be important in establishing to chronology of events in
a failure.

Program Variables

For the Chosen variables section, the short dump infrastructure takes a quick run through the collapsing

program context grabbing any program and infrastructure variables it finds that are currently in

scope. The situation is a bit like the belated shopper running through a grocery just at closing time -

there's no guarantee that the shopper will bring home everything that he or she was supposed to

buy. Even though the dump infrastructure may not capture everything, much more often than not you

will find the variables and values that you want to see.

Since SAP_BASIS Release 6.20, the short dump infrastructure has captured a separate set of Chosen

variables for each level in the Active Events/Calls ABAP call stack.

If you are analyzing a data-related problem, then a careful look at the Chosen variables may clarify the

problem. In one recent example, an OSS message reported a short dump because ABAP could not convert

the character value 229812 to an integer (dump ID CONVT_NO_NUMBER). Since this is one of

ABAP's easiest tricks, the dump is at first glance pretty mystifying. A quick look at the character field in

Chosen variables showed, however, that the character field held not ‘229812' but rather ‘229812##믆䀾

##蠤䋒##p###'. The fact that the field was either not correctly initialized or was filled with non-character
data explains the conversion failure, at the very least.

Chosen variables shows the size (here, one record with a length of 3440 bytes) of an internal table, as

well as useful information such as the type of organization of the table (here, a sorted table). The table

Page 36

 Matchcode
A tool for finding specific record. It is made up of search terms. It is used to find possible
entries for an input field.

 Number range
A range of numbers that are laid down per file for the assignment of document numbers.
It can be internal (carried out automatically by the system) or external (carried out
manually by the user).

It is a technique introduced by Microsoft to incorporate objects of one application into

 OSS (Online Service System)
SAP's Online Service System offers fast and effective help for R/3 System problems. It is
also the basic element of communications between customers, partners, and SAP.

 Repair
It contains all the objects that a developer has changed but the originals of the objects
are located in another system.

A way to implement communication between application programs via Abap/4 function

 Semaphores
When a work process locks a resource, it sets a semaphore. Another work process that
also wants to access it must then wait.

 SysID
A set of three letters or number that identify a system. Some sets are not allowed
because they are used by SAP. They are informed when the system is installed.

It is the most widely used transport protocol for open systems. R/3 clients and servers
communicate using TCP/IP.

 Telnet
It provides terminal access to hosts using TCP/IP protocol. It is a well-known command
among Systems Administrators.

 Token Ring
It is a LAN architecture with ring topology. The transmission speed is 4 MBit/s or 16
MBit/s. This involves a 'free token' which circles the loop picking up transmissions. The
receiver station places a confirmation bit into the busy token. As soon as the busy token
reaches the sender station again, it is converted back to a free token and sent on to the
next station.

 Transport
It is a request to transport objects from the software development environment, identified
as the source system, to the specified target system.

 WAN (Wide Area Networks)
They are normally operated either by the telephone company or by private companies
that offer leased lines, switched lines or packet lines.

 Work process
Work processes perform the bulk of the processing carried out by SAP systems. They
perform dialog steps in user transactions and carry out updates, lock management,
printing services, and so on.

 Workbench
The ABAP/4 Workbench, a graphical programming environment, is used to create
application programs. The programming tools are accessed using buttons, dialogs and

Similer Documents