The rsmemory Report


You can use the rsmemory report to define your memory allocation strategy for work processes. You can specify the memory class assigned to a work process, the extent of the class assigned, and the order in which it is allocated. A distinction is made here between dialog work processes and non-dialog work processes (batch, update, spool).

Changes made here only apply to the server on which you are currently logged on and only remain in effect until the SAP instance is stopped again.


You are familiar with the SAP Memory Management concept and have read the section entitled Functions of the SAP Memory Management System.


The following memory classes exist: SAP roll area, SAP Extended Memory, and private memory. These memory classes are assigned the following values, which are also displayed in the initial screen of the rsmemory report.


Memory class


Roll area


Extended Memory (EM)


Private memory (heap)

The initial screen of the report looks like this:

The initial screen of the report comprises three parts:

  • Quota Dialog: The allocation strategy for dialog work processes is defined here. You can specify the steps in which each class is allocated memory, and how much memory is allocated.

 No entry in the memory class field corresponds to class 0 (heap memory).

The entry here does not have to match the defined memory parameters. If you enter a value for the heap memory in the 4th step that is different from the abap/heaparea_dia parameter, the value entered here takes precedence.

In this case, 1 MB of roll area is first allocated by a dialog work process, and then 300 MB of extended memory. Following this, 6.5 MB of roll area are allocated again before 200 MB of heap memory (the process then switches to PRIV mode) are allocated.

  • Quota Batch/VB/Spool: As is the case with the quota dialog, the allocation strategy for non-dialog work processes is defined here (see also Allocating Memory for User Contexts (UNIX)).
  • Other parameters: You can change the following memory parameters here for test purposes (these changes only apply until the next server restart):

Displaying the Memory Areas:

You can display a list of all the users on the application server, with their respective memory requirements, by choosing Goto ® EM/HEAP areas. The used heap memory and extended of the user are displayed first, followed by the EM usage according to internal sessions.

This is followed by a history of users who have used more than the MB limit specified by em/stat_log_size_MB.

The available HEAP and EM memory is displayed at the end of the list.

EG Overview

The buttons EG Overview and EG Dump are used to analyze the Extended Global Memory. This is a part of the extended memory that is available for SAP-internal purposes. The parameter em/global_area_MB sets the size of Extended Global Memory.


In the initial screen of transaction se38, enter the report rsmemory and choose Execute or F8.