Runtime Errors -MEMORY_NO_MORE_PAGING

Hello All,

i am getting the following dump in St22, I have provided the info from St22, I would greatly appreciate if someone could kindly let me know if this is memory issue or Z_programing issue causing the memory dump and how to solve it? I can provide any other info as needed..

thank you kindly

----------------

rdisp/PG_MAXFS

Short description(Engl)   Maximum size of SAP paging file

Appl. area                Dispatcher and Task Handler

ParameterTyp              Integer value

Changes allowed           Change permitted

Valid for oper. system    All operating systems

Minimum

Maximum                   262144

DynamicallySwitchable

Same on all servers

Dflt value                32768

ProfileVal                98304

Current value             98304

--------------------------------------------------------------------------------------------------------------------

Short text

    SAP paging overflow when storing data in the ABAP/4 memory.

What happened?

    The current program requested storage space from the SAP paging area,

    but this request could not be fulfilled.

    of this area in the SAP system profile.

What can you do?

    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator

    .

    You can use the ABAP dump analysis transaction ST22 to view and manage

    termination messages, in particular for long term reference.

Error analysis

    The ABAP/4 runtime system and the ABAP/4 compiler use a common

    interface to store different types of data in different parts of

    the SAP paging area. This data includes the

    ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,

    CALL DIALOG and CALL TRANSACTION USING, as well as internally defined

    macros (specified with DEFINE).

    To store further data in the SAP paging area, you attempted to

    allocate a new SAP paging block, but no more blocks were

    available.

    When the SAP paging overflow occurred, the ABAP/4 memory contained

    entries for 2826 of different IDs.

    Please note:

    To facilitate error handling, the ABAP/4 memory was

    deleted.

How to correct the error

    The amount of storage space (in bytes) filled at termination time w

    Roll area...................... 0

    Extended memory (EM)........... 92177184

    Assigned memory (HEAP)......... 0

    Short area..................... " "

    Paging area.................... 24576

    Maximum address space.......... " "

    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',

    you can display an overview of the current roll and paging memory

    levels resulting from active users and their transactions. Try to

    decide from this whether another program requires a lot of memory

    space (perhaps too much).

    The system log contains more detailed information about the

    termination. Check for any unwanted recursion.

    Determine whether the error also occurs with small volumes of

    data. Check the profile (parameter "rdisp/PG_MAXFS", see

    Installation Guidelines).

    Is the disk or the file system that contains the paging file

    full to the extent that it cannot be increased, although it has

    not yet reached the size defined in the profile? Is the

    operating system configured to accommodate files of such a

    size?

    The ABAP processor stores different types of data in the SAP

    paging area. These include:

Line  SourceCde

    1 FUNCTION STATUS_BUFFER_EXPORT_TO_MEMORY.

    2 *"----------------------------------------------------------------------

    3 *"*"Lokale Schnittstelle:

    4 *"       IMPORTING

    5 *"              I_MEMORY_ID DEFAULT 'BSVA_BUFFER'

    6 *"----------------------------------------------------------------------

    7

    8   EXPORT JSTO_BUF JEST_BUF OBJ_DEL TO MEMORY ID I_MEMORY_ID.

    9

>>>>> ENDFUNCTION.

------------------------------