sap abap/heap_area_nondia: Heap Memory Limit for Non-Dialog Work Processes

Use

This parameter sets the limit for the heap memory (heap memory) that an R/3 non-dialog work process can allocate. This value refers to spool, update, and background processes. This value ensures that there is enough swap space available in the system.

In IBM AIX systems, specify a value for this parameter smaller than 200 MB, since the shared memory areas under AIX have a limited size. For Siemens-Nixdorf SINIX, 350 MB is the maximum that you can specify. A higher value has no advantages and no effects.

Goal:

Prevent a single non-dialog work process (user context) from filling up the entire heap memory of the application server.

The work processes of an application server can allocate only so much heap memory as specified in parameter abap/heap_area_total. The limit specified in the parameter refers to the combined heap memory usage of all work processes for an application server.

The value should be high enough for the largest possible background processing context in your R/3 System. If the value is too small, the background process is allocated R/3 Extended Memory. This Extended Memory is not available for dialog work processes.

The default value is generously sized and does not usually have to be increased.

Activities

Unit: Bytes

Default value: 40000000 (40 MB)

Recommended value For the following platforms:

• IBM AIX: 190000000 (190 mil. bytes)
• Siemens-Nixdorf SINIX: 350000000 (350 mil. bytes)
• HP-UX: 600000000 (600 mil. bytes)
• Other platforms: 900000000 (900 mil. bytes)

You can find the values from the configuration examples (Contents button). You can find additional restrictions under Data Segment Size (UNIX).

Changes: Customers can make changes.